Skip to content
New issue

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

Issue in calls_total metric of spanmetric connector #34126

Closed
namkattor123 opened this issue Jul 17, 2024 · 14 comments
Closed

Issue in calls_total metric of spanmetric connector #34126

namkattor123 opened this issue Jul 17, 2024 · 14 comments

Comments

@namkattor123
Copy link

Component(s)

connector/spanmetrics

Describe the issue you're reporting

I installed opentelemetry java agent and using [opentelemetry-collector-contrib] to expose metrics which displayed SPM on JaegerUI. But metric calls_total doesn't increase, it increase and decreas over time.Screenshot 2024-07-17 at 08 47 38

@namkattor123 namkattor123 added the needs triage New item requiring triage label Jul 17, 2024
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@namkattor123
Copy link
Author

My metric graph
Screenshot 2024-07-17 at 08 49 53

@namkattor123
Copy link
Author

My SPM monitor on Jaeger
Screenshot 2024-07-17 at 08 51 33

@crobert-1
Copy link
Member

Hello @namkattor123, from what I can tell, the metric is the current batch's total, rather than the total count of all spans seen ever. I believe this is on purpose.

I'll defer to code owners though in case there's something I'm missing.

@crobert-1 crobert-1 added question Further information is requested and removed needs triage New item requiring triage labels Jul 17, 2024
@namkattor123
Copy link
Author

Thank @crobert-1 , This photo is my value of call_totals metric. As documents of spanmetric connector, it's counter type. I don't understand why it can decrease

@namkattor123
Copy link
Author

Screenshot 2024-07-18 at 10 25 47
This is my pipeline config

@namkattor123
Copy link
Author

Screenshot 2024-07-18 at 10 25 28
This is my data value of metric

@Frapschen
Copy link
Contributor

@namkattor123 Please check your spanmetrics connector aggregation_temporality config, if the value is AGGREGATION_TEMPORALITY_DELTA, the call_totals will be gauge metrics.

@Frapschen
Copy link
Contributor

more like this: open-telemetry/opentelemetry.io#4368

@namkattor123
Copy link
Author

namkattor123 commented Aug 5, 2024

I config spanmetric with default, it means that aggregation_temporality config must be AGGREGATION_TEMPORALITY_CUMULATIVE, why it's setten to AGGREGATION_TEMPORALITY_DELTA . Can you explain for me @Frapschen

@Frapschen
Copy link
Contributor

@namkattor123 have you add resource_metrics_key_attributes to your spanmetrics connector? please see #21101 (comment)

@Frapschen
Copy link
Contributor

@namkattor123 have you add resource_metrics_key_attributes to your spanmetrics connector? please see #21101 (comment)

@namkattor123 if the above solution does not work for you, you can use the UUID() function in the transform processor to add a unique UUID to metrics attributes in each collector. I have tested this method, it works for me.

Copy link
Contributor

github-actions bot commented Oct 7, 2024

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Oct 7, 2024
Copy link
Contributor

github-actions bot commented Dec 6, 2024

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants