In this guide, you will: Start up a Node Exporter on localhost. Or you can use a VMPodScrape or a VMServiceScrape (with a headless service). The Prometheus Node Exporter exposes a wide variety of hardware- and kernel-related metrics. This is just an example: there are other ways to configure prometheus scrape targets and label rewrite rules. Note that this requires one to add an appropriate and unique instance label to each nodeexporter target. So, for example, if you’re using a VMNodeScrape, that port must be exposed on the node’s IP address. This example shows a single node configuration running ceph-mgr and nodeexporter on a server called senta04. You still need to ensure that the metrics port is accessible to the agent. The VictoriaMetrics scrapers define discovery: VMNodeScrape enumerates nodes, VMPodScrapeĮnumerates pods, and so on. It took me a little while to figure it out and I initially tried this with a VMNodeScrape object, but it didn’t work. Once that’s running, you need to decide how to export the metrics so that VictoriaMetrics can find them. ![]() The page I linked above has a few extras: it ignores various mount points and networking interfaces. ApiVersion : apps/v1 kind : DaemonSet metadata : labels : /name : node-exporter name : node-exporter namespace : monitoring-system spec : selector : matchLabels : /name : node-exporter template : metadata : labels : /name : node-exporter spec : containers : - name : node-exporter image : prom/node-exporter args : -path.sysfs=/host/sys -path.rootfs=/host/root ports : - containerPort : 9100 name : prometheus protocol : TCP volumeMounts : - name : sys mountPath : /host/sys mountPropagation : HostToContainer readOnly : true - name : root mountPath : /host/root mountPropagation : HostToContainer readOnly : true volumes : - name : sys hostPath : path : /sys - name : root hostPath : path : /
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |