We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
target allocator
The metric "opentelemetry_allocator_targets" is not accurate
Deploy the target allocator within a k8s cluster in which there are otel-collectors and service monitors.
The metric "opentelemetry_allocator_targets" should reflect the accurate number of targets
Seems the metrics value is not equal to number of targets.
For example, in this cluster there is only one target, grafana-operator, but the metric value is 700+
As a contrast, according to metric opentelemetry_allocator_targets_per_collector, the total targets number is 1
opentelemetry_allocator_targets_per_collector
1.30.0
v0.103.0
v0.98.0
No response
The text was updated successfully, but these errors were encountered:
This metric measures the number of targets discovered by the service discovery mechanism, before relabelling. Would that account for the discrepancy?
Sorry, something went wrong.
Let me double check for that
No branches or pull requests
Component(s)
target allocator
What happened?
Description
The metric "opentelemetry_allocator_targets" is not accurate
Steps to Reproduce
Deploy the target allocator within a k8s cluster in which there are otel-collectors and service monitors.
Expected Result
The metric "opentelemetry_allocator_targets" should reflect the accurate number of targets
Actual Result
Seems the metrics value is not equal to number of targets.
For example, in this cluster there is only one target, grafana-operator, but the metric value is 700+
As a contrast, according to metric
opentelemetry_allocator_targets_per_collector
, the total targets number is 1Kubernetes Version
1.30.0
Operator version
v0.103.0
Collector version
v0.98.0
Environment information
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: