docs/CaseStudies.md: typ fix: vmgent -> vmagent

This is a follow-up for f5c46b8176
This commit is contained in:
Aliaksandr Valialkin 2023-10-16 13:32:55 +02:00
parent d6f585ec0f
commit 64b503ba1c
No known key found for this signature in database
GPG Key ID: A72BEC6CD3D0DED1

View File

@ -87,7 +87,7 @@ We ended up with the following configuration:
We learned that remote write protocol generated too much traffic and connections so after 8 months we started looking for alternatives. We learned that remote write protocol generated too much traffic and connections so after 8 months we started looking for alternatives.
Around the same time, VictoriaMetrics released [vmagent](https://docs.victoriametrics.com/vmagent.html). Around the same time, VictoriaMetrics released [vmagent](https://docs.victoriametrics.com/vmagent.html).
We tried to scrape all the metrics via a single instance of vmagent but it that didn't work because vmgent wasn't able to catch up with writes We tried to scrape all the metrics via a single instance of vmagent but it that didn't work because vmagent wasn't able to catch up with writes
into VictoriaMetrics. We tested different options and end up with the following scheme: into VictoriaMetrics. We tested different options and end up with the following scheme:
- We removed Prometheus from our setup. - We removed Prometheus from our setup.