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
Users are asking why their metrics and spans do not match the external telemetry they get from their load balancers.
We need to make telemetry the first layer that is called after Axum.
Currently we have a bunch of stuff in random layers that have been added before plugins get a look in. This means that their timing and errors are not captured in spans or metrics.
We've sort of hacked around this by putting some telemetry stuff earlier, but it a mess and can be cleaned up if we make the random layers be part of the regular request lifecycle and thus telemetry plugin can happen first.
The text was updated successfully, but these errors were encountered:
BrynCooke
changed the title
Make telemetry the first layer that is called. * Discuss with team
Make telemetry the first layer that is called.
Oct 23, 2023
BrynCooke
changed the title
Make telemetry the first layer that is called.
Make telemetry the first layer that is called
Oct 23, 2023
BrynCooke
changed the title
Make telemetry the first layer that is called
Metrics and spans missing
Dec 6, 2023
Users are asking why their metrics and spans do not match the external telemetry they get from their load balancers.
We need to make telemetry the first layer that is called after Axum.
Currently we have a bunch of stuff in random layers that have been added before plugins get a look in. This means that their timing and errors are not captured in spans or metrics.
We've sort of hacked around this by putting some telemetry stuff earlier, but it a mess and can be cleaned up if we make the random layers be part of the regular request lifecycle and thus telemetry plugin can happen first.
The text was updated successfully, but these errors were encountered: