You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently the Aerospike receiver scrapes a subset of the key monitoring metrics. This should be expanded to include a metric set similar to the Aerospike Prometheus exporter.
Describe the solution you'd like
Add new metrics until the scraped set is similar to the Aerospike Prometheus exporter. I'm planning to add these in slices by PR. Something like, query metrics, latency metrics, job metrics, misc metrics, etc.
Describe alternatives you've considered
I don't see any alternative solutions. Just add the new metrics. We could stick to a small subset of metrics but I think matching the Prometheus metrics exporter Aerospike already has makes sense.
The text was updated successfully, but these errors were encountered:
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.
Is your feature request related to a problem? Please describe.
Currently the Aerospike receiver scrapes a subset of the key monitoring metrics. This should be expanded to include a metric set similar to the Aerospike Prometheus exporter.
Describe the solution you'd like
Add new metrics until the scraped set is similar to the Aerospike Prometheus exporter. I'm planning to add these in slices by PR. Something like, query metrics, latency metrics, job metrics, misc metrics, etc.
Describe alternatives you've considered
I don't see any alternative solutions. Just add the new metrics. We could stick to a small subset of metrics but I think matching the Prometheus metrics exporter Aerospike already has makes sense.
The text was updated successfully, but these errors were encountered: