-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[receiver/aerospikereceiver] Add query metrics. #13295
[receiver/aerospikereceiver] Add query metrics. #13295
Conversation
…rt lifecycle test skip
…telemetry-collector-contrib into aerospikereceiver-perf
"timeUnixNano": "1660328843530626000" | ||
}, | ||
{ | ||
"asInt": "0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like the integration test environment produced 0 for basically all the new metrics. Do you think it's worth updating the scraper test to cover at least some of them, to ensure a given response results in non-zero data points?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes I agree. In order to populate those metrics I'll have to set something up that makes requests to the test container. I can make an issue ticket for that and make it my next PR.
Co-authored-by: Daniel Jaglowski <[email protected]>
…r-contrib into aerospikereceiver-metrics
Description: Add query_count and query_json metrics. Useful for tracking query transactions.
Link to tracking Issue: 13255
Testing: Integration test adjusted for new metrics. Unit tests passed. local testing with Aerospike cluster.
Documentation: Automated changes made to documentation.md by mdatagen reflecting new metrics.