On 22/03/2021 23:30, chuanjia xing wrote:
I have one more question for node_exporter: say if I want to get ec2
instance cpu metrics for _/lots/_ of clusters, do I need to run
node_exporter on every node in all clusters? From the doc of
node_exporter, it looks like one exporter will only collect metrics
for the node it's running on, which means in my case I do need to
install node_exporter on every nodes for all clusters.
If that is the case, then node_exporter might not work for my case --
I can't run a node_exporter on every node. Then cloudwatch exporter
can do this since I only need one exporter instance to collect all ec2
instance cpu metrics in one region, but it's just slow.
Yes you would install the node exporter on each EC2 instance. A common
way to do that is to build it into the AMIs you are using or to use
cloud-init to add it on startup. In addition to CPU you get a lot more
metrics that Cloudwatch isn't able to supply - full details about
networking, memory, disk, systemd, etc.
Cloudwatch is known to be slow, not just the actual API calls but also
the time it takes for metrics to be available (a value returned by the
API might be comparatively old rather than being real-time). Using the
Node exporter is also likely to be cheaper as the only costs are network
bandwidth rather than the various API calls.
--
Stuart Clark
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to prometheus-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-users/f92e5959-a61d-5ace-66f0-978cfd693754%40Jahingo.com.
