Hi,
Our Prometheus configs are also automated via Ansible, based on template.
But in the end, all the lines are inserted to prometheus.yml file after
'scrape_configs'.We have a lot of AWS instances and each project using
multiple exporter/services that's why the file is too long.
Yeah, I know abo
On Tue, 16 Jun 2020 at 11:06, Ben Kochie wrote:
> There are other advantages to moving targets from static_configs to
> file_sd_configs.
>
> With targets in file_sd_configs, Prometheus knows how to reload these
> files without reloading all targets. This improves the scheduling of
> scrapes,
>
There are other advantages to moving targets from static_configs to
file_sd_configs.
With targets in file_sd_configs, Prometheus knows how to reload these files
without reloading all targets. This improves the scheduling of scrapes, as
when you reload Prometheus, all in-flight scrapes are canceled
Hi Christian,
Our Prometheus configs are also automated via Ansible, based on template.
But in the end, all the lines are inserted to prometheus.yml file after
'scrape_configs'.We have a lot of AWS instances and each project using
multiple exporter/services that's why the file is too long.
Yea
Hi,
On 6/16/20 9:35 AM, pratyush ranjan wrote:
> I am using Prometheus for our monitoring and I have a lot of configs
> (our prometheus.yml main config file is 8000+ lines long).
>
> I would like to divide this out into logical groupings so that it
> becomes much readable. I came to know that Pro
I am using Prometheus for our monitoring and I have a lot of configs (our
prometheus.yml main config file is 8000+ lines long).
I would like to divide this out into logical groupings so that it becomes
much readable. I came to know that Prometheus doesn't support this and we
can use configura
6 matches
Mail list logo
