[ceph-users] Re: setting unique labels in cephadm installed (pacific) prometheus.yml

2022-10-25 Thread Redouane Kachach Elhichou
Currently the generated template is the same for all the hosts and there's
no way to have a dedicated template for a specific host AFAIK.

On Tue, Oct 25, 2022 at 12:45 PM Lasse Aagren  wrote:

> The context provided, when parsing the template:
>
>
> https://github.com/ceph/ceph/blob/v16.2.10/src/pybind/mgr/cephadm/services/monitoring.py#L319-L331
>
> doesn't seem to provide any per host uniqueness
>
> On Tue, Oct 25, 2022 at 12:35 PM Lasse Aagren  wrote:
>
> > Hello,
> >
> > In our cephadm installed cluster (pacific) we are running two instances
> of
> > prometheus.
> >
> > Through altering the prometheus.yml.j2 template (ceph config-key set
> > mgr/cephadm/services/prometheus/prometheus.yml ...) we set the
> prometheus'
> > to remote write to a corporate setup for long time retention of metrics)
> >
> > As we have two prometheus instances we need a way to create a unique
> label
> > to not have clashing data in the upstream setup.
> >
> > So far we haven't been able to do that in this template:
> >
> >
> >
> https://github.com/ceph/ceph/blob/v16.2.10/src/pybind/mgr/cephadm/templates/services/prometheus/prometheus.yml.j2
> >
> > other than something like:
> >
> > 
> >   - target_label: prometheus_replica
> > replacement: 'prometheus-{{ range(1, 51) | random }}'
> > 
> >
> > And keeping fingers crossed that "random" won't be the same two times in
> a
> > row.
> >
> > Do anyone have a better idea on how to do this?
> >
> > Best regards,
> > Lasse Aagren
> >
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io


[ceph-users] Re: setting unique labels in cephadm installed (pacific) prometheus.yml

2022-10-25 Thread Lasse Aagren
The context provided, when parsing the template:

https://github.com/ceph/ceph/blob/v16.2.10/src/pybind/mgr/cephadm/services/monitoring.py#L319-L331

doesn't seem to provide any per host uniqueness

On Tue, Oct 25, 2022 at 12:35 PM Lasse Aagren  wrote:

> Hello,
>
> In our cephadm installed cluster (pacific) we are running two instances of
> prometheus.
>
> Through altering the prometheus.yml.j2 template (ceph config-key set
> mgr/cephadm/services/prometheus/prometheus.yml ...) we set the prometheus'
> to remote write to a corporate setup for long time retention of metrics)
>
> As we have two prometheus instances we need a way to create a unique label
> to not have clashing data in the upstream setup.
>
> So far we haven't been able to do that in this template:
>
>
> https://github.com/ceph/ceph/blob/v16.2.10/src/pybind/mgr/cephadm/templates/services/prometheus/prometheus.yml.j2
>
> other than something like:
>
> 
>   - target_label: prometheus_replica
> replacement: 'prometheus-{{ range(1, 51) | random }}'
> 
>
> And keeping fingers crossed that "random" won't be the same two times in a
> row.
>
> Do anyone have a better idea on how to do this?
>
> Best regards,
> Lasse Aagren
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io