- This topic has 1 reply, 2 voices, and was last updated 3 months, 2 weeks ago by
.
-
Posts
-
Hi,
Is there a method/query I can run to gain some more information on what resources the MFLib system itself is using?Ie: Let’s say I have a slice with 4 nodes that I measure using MFLib, instrumentizing prometheus. I am interested in figuring out how much resources this measurement uses, and I am therefore wondering if there is anything built into MFLib that lets me peek at that.
The measurement framework sets up its own network to get data from the experimental nodes, therefore experimental networks are mostly unaffected. You could use the metrics, node_network_receive_packets_total and node_network_transmit_packets_total, to see data going in/out of the network interface used for the measurement network to get an idea of the network use.
Most of the Prometheus/Grafana & ELK monitoring processes take place on the measurement node, therefore they have little effect on the experiment nodes.
What is running on the experiment nodes are the node_exporters & file beats.
The node exporter is a binary that only uses resources when it is asked for metrics. see https://github.com/prometheus/node_exporter for information about the resources it uses. You can see what it is doing via top/htop. The node exporter is written in GO and exports some go metrics about its own resource usage. Use the Explore page to search for{ __name__=~”go_.*”, job=”node”}ELK beats are similar but may use more resources since they monitor logs and periodically ship out data. You may also see filebeat, metricbeat and packet beat resource usage using top/htop. I am not sure of the current status of self monitoring of ELK beats.
- You must be logged in to reply to this topic.