You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It would be useful for performance and debugging purposes to record API calls into trace spans produced by decalog (in a similar way to database calls are implemented)
Describe the solution you'd like
WP-Traffic integrated into the tracing component of decalog (ie. user makes request to page, Wordpress has an outgoing API call needed to service that request - request would be logged in the trace span and pushed to jaeger).
Describe alternatives you've considered
Simply analysing the logs in WP-Traffic (this misses other context, like DB calls produced alongside, along with potentially other trace data that is unified with the Decalog data (ie. traces produced by NGINX or other API services) allows us to see the entire request flow (and ideally where slowdowns or issues may occur)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It would be useful for performance and debugging purposes to record API calls into trace spans produced by decalog (in a similar way to database calls are implemented)
Describe the solution you'd like
WP-Traffic integrated into the tracing component of decalog (ie. user makes request to page, Wordpress has an outgoing API call needed to service that request - request would be logged in the trace span and pushed to jaeger).
Describe alternatives you've considered
Simply analysing the logs in WP-Traffic (this misses other context, like DB calls produced alongside, along with potentially other trace data that is unified with the Decalog data (ie. traces produced by NGINX or other API services) allows us to see the entire request flow (and ideally where slowdowns or issues may occur)
The text was updated successfully, but these errors were encountered: