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
DB semconv: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/semantic_conventions/database-metrics.md
The text was updated successfully, but these errors were encountered:
hey can you assign this to me.
Sorry, something went wrong.
hey @srikanthccv I have some doubts related to semantic convention of db i am posting here feel free comment
db.client.connections.usage
pymemcache.pool.ObjectPool
what do you mean by db.client.connections.idle.max is it the maximum_pool value that is passed during pool intialization?
db.client.connections.idle.max
db.client.connections.pending_requests can you please explain this pending request scenario?
db.client.connections.pending_requests
Is db.client.connections.usage for metric tells how many connection are currenlty in state of used or idle which can be set in upDownCounter ?
Yes
Requests that are yet to be assigned with connection from the pool
rahulmukherjee68
No branches or pull requests
DB semconv: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/semantic_conventions/database-metrics.md
The text was updated successfully, but these errors were encountered: