search

blakelead / couchbase_exporter

Export metrics from Couchbase Server for Prometheus consumption
Other
35 stars 18 forks source link

Node vs Bucket metrics #6

Closed shipmak closed 6 years ago

shipmak commented 6 years ago

I have a 3 node cluster. I'm wondering do I need a separate exporter for each and every node to grab each "NODE's" metrics (for example: cb_node_stats_cmd_get)? If my understanding is correct, each exporter would be calculating the same BUCKET and CLUSTER metrics redundantly.

Is there a way to just have 1 exporter running that points to a single node in the cluster, and then can identify all other nodes in that cluster and provide the *NODE metrics breakdown for each node? (Much like we have for BUCKETs, if we have multiple buckets, we report on each bucket from a single exporter).

blakelead commented 6 years ago

Thanks for your question.

The answer can be found in the "Deployment" paragraph of Prometheus documentation.

For the sake of following good practices, I made node metrics specific to the node that is being scraped hence the need to deploy an exporter instance for each node.

As for redundancy I cannot give you an definite answer right now, but I'll try it as soon as I can.

blakelead commented 6 years ago

I tested it and I have the same cluster metrics for each instance. I also tested some other exporters like Elasticsearch Exporter and same thing happens.

I don't know what to think about that... Anyway, if it is really annoying to use, I could implement a way to have only one instance of the exporter that scrapes all the nodes metrics.

blakelead commented 6 years ago

I will close this issue, but feel free to react if you feel that this issue should be treated.