Re: [prometheus-users] Setting up a Prometheus environment with a push mechanism

Regarding the other points: however you judge the differences, they are still significant departures from the rest of the Prometheus ecosystem (including compatible third-party providers). It's ok to build something incompatible, it's just IMO not ok to superficially make it sound everywhere like i

Re: [prometheus-users] Setting up a Prometheus environment with a push mechanism

On Thu, Mar 25, 2021 at 3:15 PM Aliaksandr Valialkin wrote: > > > On Thu, Mar 25, 2021 at 3:54 PM Julius Volz > wrote: > >> What should be noted when bringing up VictoriaMetrics in the Prometheus >> context is that it is deliberately incompatible with Prometheus in multiple >> ways: >> >> - VM's

Re: [prometheus-users] Setting up a Prometheus environment with a push mechanism

On Thu, Mar 25, 2021 at 3:54 PM Julius Volz wrote: > What should be noted when bringing up VictoriaMetrics in the Prometheus > context is that it is deliberately incompatible with Prometheus in multiple > ways: > > - VM's MetricsQL behaves differently from PromQL in a multitude of ways > and is *

Re: [prometheus-users] Setting up a Prometheus environment with a push mechanism

Another option if your security will allow opening one port to Prometheus data, there is the "exporter_exporter" https://github.com/QubitProducts/exporter_exporter On the subject of external labels, you should have those anyway on your Prometheus instances otherwise you can't identify them proper

Re: [prometheus-users] Setting up a Prometheus environment with a push mechanism

Alright, did not know all of that. We are now setting up the Prometheus Proxy and are hoping that it does what we want it to do. VictoriaMetrics would be a last case scenario anyway Op donderdag 25 maart 2021 om 14:54:22 UTC+1 schreef juliu...@promlabs.com: > What should be noted when bringing

Re: [prometheus-users] Setting up a Prometheus environment with a push mechanism

What should be noted when bringing up VictoriaMetrics in the Prometheus context is that it is deliberately incompatible with Prometheus in multiple ways: - VM's MetricsQL behaves differently from PromQL in a multitude of ways and is *not* backwards-compatible with PromQL (see also https://promlabs

Re: [prometheus-users] Setting up a Prometheus environment with a push mechanism

It is correct that Thanos' deduplication works when using just 2 or more Prometheus servers. The thing is, Thanos cannot use existing labels to do deduplication. I want it to deduplicate using the label called exported_instance, but i cannot predefine this label in the external labels for thano

Re: [prometheus-users] Setting up a Prometheus environment with a push mechanism

Probably VictoriaMetrics could help with this setup. It supports data push via various protocols , it supports data deduplication and it is compatible with Prometheus datasource in

Re: [prometheus-users] Setting up a Prometheus environment with a push mechanism

If you're monitoring within a single network, but can't make any connections to your targets, PushProx might be a good idea https://github.com/prometheus-community/PushProx On Thu, Mar 25, 2021 at 2:01 PM robbe vaes wrote: > Okay so, we want to have an environment using Prometheus, where we ca

Re: [prometheus-users] Setting up a Prometheus environment with a push mechanism

Deduplication works fine with Thanos, you need to make sure you setup replica labels in your Prometheus external labels. On Thu, Mar 25, 2021 at 2:20 PM robbe vaes wrote: > The thing is we can implement multiple prometheus instances as well, thats > no issue and will probably happen anyway. The

Re: [prometheus-users] Setting up a Prometheus environment with a push mechanism

The thing is we can implement multiple prometheus instances as well, thats no issue and will probably happen anyway. The thing is, we tried using Thanos to manage multiple prometheus servers and do deduplication, but the deduplication does not work for the collectd exporters. The problem its ha

Re: [prometheus-users] Setting up a Prometheus environment with a push mechanism

The way this is usually solved is by duplicating prometheus - it seems that now you have moved the SPOF from the exporter to prometheus. Regards, On 25 Mar 06:01, robbe vaes wrote: > Okay so, we want to have an environment using Prometheus, where we can > monitor our servers etc with a push meth

Re: [prometheus-users] Setting up a Prometheus environment with a push mechanism

Okay so, we want to have an environment using Prometheus, where we can monitor our servers etc with a push method rather then pull due to network security aspects. As of now, we managed to set up collectd together with collectd exporter for prometheus. This way we can have the clients or server

Re: [prometheus-users] Setting up a Prometheus environment with a push mechanism

Can you describe more about what your network topology is exactly? There are a number of solutions for dealing with distributed monitoring. On Thu, Mar 25, 2021 at 12:45 PM robbe vaes wrote: > Hi, > > I am trying to setup a monitoring environment with Prometheus, but it has > to be using a push

[prometheus-users] Setting up a Prometheus environment with a push mechanism

Hi, I am trying to setup a monitoring environment with Prometheus, but it has to be using a push mechanism instead of the standard pull mechanism Prometheus uses. I was wondering what options there are to create an environment like this. It would also have to perfom data deduplication. The mai