The latest VictoriaMetrics releases introduce major enhancements across several of its core components, including vmagent, #vmalert, vmctl, and their toolset. New in v1.130.0: ✨ Metric metadata support (#Prometheus-compatible API) #VictoriaMetrics can now scrape and store metadata using vmsingle or vmagent and expose it via /api/v1/metadata. Enable it with -enableMetadata=true across vmsingle, vmagent, and vminsert.
📦 Namespace metadata for #Kubernetes targets vmagent now can attach namespace metadata to discovered pods, services, endpoints, and more, allowing richer filtering and discovery rules. 🎛️ VMUI improvements The #VictoriaMetrics UI is now faster and more intuitive. 🔔 Better alert templating behavior in vmalert Templating errors now surface as annotation values while alerts continue to be generated, aligning with Prometheus behavior.
The VictoriaMetrics ecosystem continues to evolve rapidly, and the latest updates bring meaningful improvements across metrics, logs, and traces. Read the announcement …
VictoriaMetrics
in reply to VictoriaMetrics • • •📦 Namespace metadata for #Kubernetes targets
vmagent now can attach namespace metadata to discovered pods, services, endpoints, and more, allowing richer filtering and discovery rules.
🎛️ VMUI improvements
The #VictoriaMetrics UI is now faster and more intuitive.
🔔 Better alert templating behavior in vmalert
Templating errors now surface as annotation values while alerts continue to be generated, aligning with Prometheus behavior.
Find more information in our blog post 👇
bit.ly/48irBWJ
Our latest updates across the VictoriaMetrics Observability ecosystem
VictoriaMetrics