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
Hi, I'm from the Kibana team, and I'm working on APM RUM agent integration into Kibana.
In the Kibana use case, when a user opens a dashboard page, Kibana might render several visualizations. Each visualization triggers an async sequence of steps that ends up in a network request to fetch data.
We found out the APM RUM agent doesn't support context propagation when multiple async operations are executed in parallel. So we have to work around this limitation by implementing a custom solution for manual context propagation.
It would be awesome if the APM RUM agent provides API for manual Context management.
// in dashboard codeconstcontext=apm.createContext({ type, id });// just for a demo purposesawaitinitDataLoading({ context });// in http serviceapm.startTransaction(...);apm.bind(context);awaitfetch(...)// automatically propagates context via headers
The text was updated successfully, but these errors were encountered:
In the interests of transparency, we’ve discussed this in refinement and we won’t be able to work on this or plan it in right now, whilst the team are focusing on Synthetics.
Hi, I'm from the Kibana team, and I'm working on APM RUM agent integration into Kibana.
In the Kibana use case, when a user opens a dashboard page, Kibana might render several visualizations. Each visualization triggers an async sequence of steps that ends up in a network request to fetch data.
We found out the APM RUM agent doesn't support context propagation when multiple async operations are executed in parallel. So we have to work around this limitation by implementing a custom solution for manual context propagation.
It would be awesome if the APM RUM agent provides API for manual Context management.
The text was updated successfully, but these errors were encountered: