v1.107.0238.2 MB
Apache-2.0
strict
core18
vmagent is a tiny agent which helps you collect metrics from various sources, relabel and filter the collected metrics and store
- Can be used as a drop-in replacement for Prometheus for discovering and scraping targets such as node_exporter. Note that single-node VictoriaMetrics can also discover and scrape Prometheus-compatible targets in the same way as vmagent does.
- Can add, remove and modify labels (aka tags) via Prometheus relabeling.
- Can filter data before sending it to remote storage.
- Can accept data via all the ingestion protocols supported by VictoriaMetrics.
- Can aggregate incoming samples by time and by labels before sending them to remote storage.
- Can replicate collected metrics simultaneously to multiple Prometheus-compatible remote storage systems.
- Can save egress network bandwidth usage costs when VictoriaMetrics remote write protocol is used for sending the data to VictoriaMetrics.
- Works smoothly in environments with unstable connections to remote storage. If the remote storage is unavailable, the collected metrics are buffered at
-remoteWrite.tmpDataPath. The buffered metrics are sent to remote storage as soon as the connection to the remote storage is repaired. The maximum disk usage for the buffer can be limited with-remoteWrite.maxDiskUsagePerURL. - Uses lower amounts of RAM, CPU, disk IO and network bandwidth than Prometheus.
- Scrape targets can be spread among multiple vmagent instances when big number of targets must be scraped.
- Can load scrape configs from multiple files.
- Can efficiently scrape targets that expose millions of time series such as
/federateendpoint in Prometheus. - Can deal with high cardinality and high churn rate issues by limiting the number of unique time series at scrape time and before sending them to remote storage systems.
- Can write collected metrics to multiple tenants.
Update History
v1.107.0 (23)13 Dec 2025, 09:47 UTC
3 Jun 2023, 16:12 UTC
9 Dec 2024, 15:49 UTC
13 Dec 2025, 09:47 UTC