Metrics forwarder?

[Ramanathan Muthaiah]

Hello All,

I have been scratching on this for a while now. Would appreciate your suggestions.

We have a bunch of VMs at customer sites running telegraf exporter.  These are configured to send metrics to specific urls setup in cloudflare.

My question is this:

How can I use aws managed prometheus to store the incoming metrics from VMs? I prefer the managed service as it provides relief (per aws doc) from storage/scaling/reliability.

I looked at Prometheus docs (run as agent, like for example, grafa agent or push gateway) and several others too but could not find the best way forward.

/R

[Ben Kochie]

Both Prometheus in agent mode and Grafana Agent would be good solutions.

It really depends on how you want to configure everything.

--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/CAGBd0epbojo79kRnmVcAidbtZKKat_4L07L2-rsZjr81i7yyBQ%40mail.gmail.com.

[Brian Candler]

On Tuesday, 1 February 2022 at 19:45:51 UTC Ram wrote:

How can I use aws managed prometheus to store the incoming metrics from VMs? I prefer the managed service as it provides relief (per aws doc) from storage/scaling/reliability.

That depends.  If aws managed prometheus supports "remote write", which was only made a supported feature a few days ago, then you could use that.  However the documentation warns:

"Prometheus can be configured as a receiver for the Prometheus remote write protocol. This is not considered an efficient way of ingesting samples. Use it with caution for specific low-volume use cases. It is not suitable for replacing the ingestion via scraping and turning Prometheus into a push-based metrics collection system."

In other words, if you want to use prometheus, you should get prometheus to do active scraping (making scrapes to say node_exporter running on the customer sites).  If you can't do that, then prometheus is probably not a good fit for your use case.

[Ben Kochie]

Prometheus has supported receiving remote write for several releases. It's just now promoted to stable.

What this person is asking about is _sending_ remote write, which has been supported for a very long time.

--

You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/aa25cdeb-8c1c-47c9-93d4-9f09c72f1229n%40googlegroups.com.

[Brian Candler]

On Tuesday, 1 February 2022 at 20:34:15 UTC sup...@gmail.com wrote:

Prometheus has supported receiving remote write for several releases. It's just now promoted to stable.

Indeed. It's unclear though whether the aws managed version of prometheus (which the OP said they wanted to use) lets you turn this on, when it was hidden behind a feature flag until a few days ago.

 

What this person is asking about is _sending_ remote write, which has been supported for a very long time.

I'm not sure - I read it as saying that the data was originating from telegraf, not prometheus.

What do you think of the comment that "[remote-write] is not suitable for replacing the ingestion via scraping" ?  If the scraping were done using a local prometheus agent, and then relayed via remote-write to another prometheus, would that be acceptable?  Or is really remote-write primarily intended for a destination other than prometheus?