Hi:
Our prometheus database contains around 5k+ unique type of metrics. With time,
we have defined alerting rules to detect deviations.
However, given the number of growing metrics, it is becoming difficult to
expand the alerting rules.
Generally we are interested in increase/decrease of
It is not possible as target.json param only override the first entry and will
not allow dots.
Prometheus 2.43 enables scrape_config_file so you can split your scrape
configs into multiple files. Maybe that can be helpful.
On 23 Mar 14:17, Christian Oelsner wrote:
> Hello all,
>
> I am trying
Hello all,
I am trying to use file_sd with params.
I currently have a scrape job that looks similar to this.
- job_name: 'confluent-cloud'
scrape_interval: 1m
scrape_timeout: 20s
static_configs:
- targets:
- api.telemetry.confluent.cloud
scheme: https
(foo==1)[24h:1m]
creates a range vector, which you then need to process further. If you run
a function over it to count the values in the range you will get an instant
vector, which as I showed in my original post makes this:
*count_over_time((foo==1)[24h:1m])*
That is valid (I've tested it with
4 matches
Mail list logo