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
Describe the bug
When metrics expire, opentelemetry-collector crashes.
Steps to reproduce
Start otel collector with provided config below.
Start HotROD example: docker run --rm --network="host" --env JAEGER_AGENT_HOST=localhost --env JAEGER_AGENT_PORT=6835 -p8080-8083:8080-8083 jaegertracing/example-hotrod:latest all
This will emit spans to otel collector on port 6835.
Click on a button on HotROD example to send a trace.
Check that the latency_bucket metrics are correct for the first minute of data, and make a note of which bucket has count > 0. For example, where the metric has label le = "250".
Example query: latency_bucket{service_name = "driver", le="250"}
What did you expect to see?
After a minute (on metric expiry), the metric with le = "250" (example query latency_bucket{service_name = "driver", le="250"}) should no longer be query-able (a null value).
What did you see instead?
After a minute (on metric expiry), the opentelemetry-collector crashes with the following logs:
Relates to #6935
Describe the bug
When metrics expire, opentelemetry-collector crashes.
Steps to reproduce
docker run --rm --network="host" --env JAEGER_AGENT_HOST=localhost --env JAEGER_AGENT_PORT=6835 -p8080-8083:8080-8083 jaegertracing/example-hotrod:latest all
6835
.latency_bucket
metrics are correct for the first minute of data, and make a note of which bucket hascount > 0
. For example, where the metric has labelle = "250"
.latency_bucket{service_name = "driver", le="250"}
What did you expect to see?
After a minute (on metric expiry), the metric with
le = "250"
(example querylatency_bucket{service_name = "driver", le="250"}
) should no longer be query-able (a null value).What did you see instead?
After a minute (on metric expiry), the opentelemetry-collector crashes with the following logs:
What version did you use?
Version:
main
branchWhat config did you use?
Config:
Environment
OS: "Ubuntu 20.04"
Compiler(if manually compiled): "go 1.17.5")
cc @Aneurysm9
The text was updated successfully, but these errors were encountered: