Hi Mircea!
Did you find a solution to your problem? I'm looking into a somewhat
similar scenario.
/Rufus
Mircea Ulinic schrieb am Freitag, 21. Februar 2020 um 23:46:38 UTC+1:
> Thanks for your answers both! To clarify, I am looking on the
> Prometheus client side. The metrics are not counters
Thanks for your answers both! To clarify, I am looking on the
Prometheus client side. The metrics are not counters or anything that
can be exported straight away, rather based on some "events" (e.g., a
file has been changed, etc. -- even in an example like that, I would
need the app, after restart,
Why are you trying to persist your metrics? If it's to preserve counters,
this is unnecessary. PromQL functions that operate on counters (such as
rate) will gracefully handle cases where the counter restarts.
On Friday, February 21, 2020 at 9:21:47 AM UTC-8, Stuart Clark wrote:
>
> Your metrics
Your metrics are being stored in Prometheus so this shouldn't be necessary.
On 21 February 2020 17:15:18 GMT, Mircea wrote:
>
>
>Hello,
>
>
>This might be a silly question, but here I am: I would need to enable
>persistence for some metrics (looks like the push gateway might be a
>no-go
>for n
Hello,
This might be a silly question, but here I am: I would need to enable
persistence for some metrics (looks like the push gateway might be a no-go
for now) and I was thinking to have my app dump the metrics, say into a
file (e.g., using the write_to_textfile function) - then when the ap
5 matches
Mail list logo
