![]() Or you can use a VMPodScrape or a VMServiceScrape (with a headless service). ![]() So, for example, if you’re using a VMNodeScrape, that port must be exposed on the node’s IP address. You still need to ensure that the metrics port is accessible to the agent. The Prometheus Node Exporter can expose metrics that Prometheus can scrape, including a wide. The VictoriaMetrics scrapers define discovery: VMNodeScrape enumerates nodes, VMPodScrapeĮnumerates pods, and so on. Machine-metric exporter for the Prometheus monitoring system. It took me a little while to figure it out and I initially tried this with a VMNodeScrape object, but it didn’t work. Note: The default port for the nodeexporter is actually :9100 but that is the same port as the Couchbase Index Admin Port and cannot be used. 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. A Node Exporter is needed on all servers or virtual machines to collect data on all nodes Node Exporter exposes metrics on '/metrics' sub-path on port 9100. 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 |