Replies: 1 comment 3 replies
-
Usually one would configure different |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello 👋
I'm using this library to export metrics of DB connection pool on Google Cloud.
I found the following error in otel-collector processes (Cloud Run instances) and want to fix this problem:
According to https://stackoverflow.com/a/61108971, it means that otel-collector received DB connection pool metrics from two or more instances, and timestamp of metrics from them are mixed so they seems invalid for the collector.
So I want to try to change resource type of these metrics from
generic_node
tocloud_run_revision
, or add the instance ID to attribute (or label?) of metrics.I expected that setting
Attributes
would realize it, however, I found no public API handlingAttributes
inio.opentelemetry.instrumentation.hikaricp.v3_0
package.I've also checked #6209 (comment) but I think
Baggage
API is not suitable because DB connection pool metrics are not related to trace/span.Please help me to find solutions to export HikariCP metrics from multiple instances.
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions