Vector: Add VictoriaMetrics metrics sink
It would be great if Vector could route metrics data to VictoriaMetrics via any supported ingestion methods - see https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/README.md#how-to-import-time-series-data .
valyala
All 3 comments
I was just about to ask for this myself!
jogster
on 10 Dec 2019
Both the Influx line protocol and Graphite text protocol are sinks we plan to support before too long.
lukesteensen
on 11 Dec 2019
Having just setup a statsd (source) -> prometheus (sink) -> prometheus (pull) (5s) -> prometheus(write) (5s) -> victoria-metrics
The above pipe-line results in metics being pulled every 5 seconds and pushed every 5 seconds + 1 second approx. 11 seconds delay
Would be great to just have:
statsd(source) -> prometheus_write (sink) -> victoria-metrics
In this pipe-line at the most it should be 1 second (pushed by app into statsd source)
Additionally the current prometheus mapping work 'out-of-the-box' translating those to graphite/influx and back will result in a mapping headache.
jogster
on 12 Dec 2019
Related issues
binarylogic
路
3Comments
Hoverbear
路
3Comments
a-rodin
路
3Comments
LucioFranco
路
3Comments
lewisthompson
路
3Comments
Most helpful comment
Having just setup a statsd (source) -> prometheus (sink) -> prometheus (pull) (5s) -> prometheus(write) (5s) -> victoria-metrics
The above pipe-line results in metics being pulled every 5 seconds and pushed every 5 seconds + 1 second approx. 11 seconds delay
Would be great to just have:
statsd(source) -> prometheus_write (sink) -> victoria-metrics
In this pipe-line at the most it should be 1 second (pushed by app into statsd source)
Additionally the current prometheus mapping work 'out-of-the-box' translating those to graphite/influx and back will result in a mapping headache.