Prometheus as a remote writer only.

[Oscar Prieto]

Hi all!

With old prometheus 1.7 i was able to disable the local storage completely but it does not seem to be doable with current iterations.

I'm currently playing with this arguments to launck kubenetes and figuring what are their minimum bondaries.

'--storage.tsdb.retention.time=6h'
'--storage.tsdb.min-block-duration=2h'
'--storage.tsdb.max-block-duration=2h'

While it seems the TSDB cannot be disrabled entirely how can it be tuned to minimize his usage as possible?

Thanks!

[Brian Candler]

You might want to look at vmagent instead (part of VictoriaMetrics).  It does exactly what you want: scraping and remote writing only.

You can't disable local writing with prometheus because it depends on having at least *some* timeseries history for alerting rules, recording rules, federation etc - and indeed the WAL is used for buffering remote writes.

[Oscar Prieto]

Many thanks Brian, i'll be definitely giving it a try!

On Thu, Oct 29, 2020 at 11:53 AM Brian Candler <b.ca...@pobox.com> wrote:

You might want to look at vmagent instead (part of VictoriaMetrics).  It does exactly what you want: scraping and remote writing only.

You can't disable local writing with prometheus because it depends on having at least *some* timeseries history for alerting rules, recording rules, federation etc - and indeed the WAL is used for buffering remote writes.

--
You received this message because you are subscribed to a topic in the Google Groups "Prometheus Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/prometheus-users/gj-iRPopFg8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to prometheus-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/ff24fd73-ac13-4236-a6dd-24a27f13d11fo%40googlegroups.com.