Repository navigation
Tracing: Simplify webhook traceability #1139
Description
Is your feature request related to a problem?
Currently, tracing the flow from glific to kaapi, then to the provider, back to kaapi, and finally to the webhook and back to glific is cumbersome. It requires correlating data across the database, Cloudwatch logs, Sentry, and Glific logs, which is time-consuming and inefficient.
Describe the solution you'd like
- Add a shared key per webhook request for easier traceability.
- Simplify the process of determining if Kaapi successfully dispatched the response.
Why is this enhancement needed?
This enhancement will improve efficiency, reducing the time spent on manual correlation and improving maintainability and usability of the tracing process.
Original issue
Describe the current behavior
To streamline traceability of whole glific--> kaapi---> provider--->kaapi---> webhook --> glific, we will add a shared key per webhook request to easily decipher whether Kaapi has successfully dispatched response in the webhook or not. Currently this requires a bit of grunt work correlating across database, Cloudwatch logs, Sentry and Glfic logs.
Describe the enhancement you'd like
A clear and concise description of the improvement you want to see.
Why is this enhancement needed?
Explain the benefits (e.g., performance, usability, maintainability, scalability).
Additional context
Add any other context, metrics, screenshots, or examples about the enhancement here.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
[-]LLM Call: Streamline Traceability[/-][+]Tracing: Simplify webhook traceability[/+]Prajna1999 commentedon Oct 5, 2026
Glific sends a hash key with request_metadata to correlate. Not required at the moment.