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

Missing metrics #19

Closed
dsw9742 opened this issue Feb 5, 2018 · 3 comments
Closed

Missing metrics #19

dsw9742 opened this issue Feb 5, 2018 · 3 comments

Comments

@dsw9742
Copy link

dsw9742 commented Feb 5, 2018

Hi, it seems like there might be a few metrics missing from this plugin.

I'm sure this is not an exhaustive list, but some of the metrics I've personally been unable to find:

  • batch_index_created_buffers
  • batch_index_destroyed_buffers
  • batch_index_unused_buffers
  • batch_index_huge_buffers
  • fabric_bulk_send_rate
  • fabric_bulk_recv_rate
  • fabric_ctrl_send_rate
  • fabric_ctrl_recv_rate
  • fabric_meta_send_rate
  • fabric_meta_recv_rate
  • fabric_rw_send_rate
  • fabric_rw_recv_rate
  • heap_active_kbytes
  • heap_mapped_kbytes
  • heap_allocated_kbytes
  • heap_efficiency_pct
  • heartbeat_received_foreign
  • heartbeat_received_self
  • uptime

I'm unsure if these are missing from asgraphite but figure that could be a contributing factor. Seems like this project has not been updated in quite a long time.

Any chance of getting an updated version that exposes current set of metrics?

@whyrg
Copy link
Contributor

whyrg commented Feb 5, 2018

What is your Aerospike Server version and asgraphite version?

asgraphite does discovery of metrics through our info protocol. Any metrics that the server responds with gets parsed for formatting only. Any unrecognized lines are printed into the log. Asgraphite itself doesn't keep a list of what is or isn't a metric.

@dsw9742
Copy link
Author

dsw9742 commented Feb 5, 2018

@whyrg Hi Richard, thanks for the quick response.

Aerospike Server version is 3.15.0.2.

As for the asgraphite version ... I'm not sure. I'm using the (Aerospike Prometheus Exporter)[https://github.com/alicebob/asprom], which indicates it "follows the logic from asgraphite." I had assumed it was wrapping the asgraphite library, but now I'm not so sure. Maybe it reimplements the asgraphite logic instead. Any chance you have a good idea how to go about validating that theory ... ?

@whyrg
Copy link
Contributor

whyrg commented Feb 5, 2018

The Prometheus plugin keeps a small mapping of the initial service metrics, as they need to differentiate counters and gauges.

From my limited understanding of GoLang, it seems they only parse the metrics in this mapping, instead of applying said mapping to all discovered metrics.

Closing as this is a 3rd party issue.

@whyrg whyrg closed this as completed Feb 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants