Re: Alertmanager not using custom configuration template

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Thu, 11 Mar 2021 19:40:09 +0100
Marc 'risson' Schmitt <risson@xxxxxxxxxxxx> wrote:
> Cephadm is supposed to include some default Prometheus configuration
> for alerting[1], if this configuration is present in the container. It
> gets the path to this configuration from
> `mgr/cephadm/prometheus_alerts_path`, which is by default
> `/etc/prometheus/ceph/ceph_default_alerts.yml` and is indeed a valid
> Prometheus rules file inside the ceph-mgr container. However it
> doesn't end up in
> `/var/lib/ceph/<uuid>/prometheus/etc/prometheus/alerting/` as they
> should.
> 
> [1]
> https://github.com/ceph/ceph/blob/v15.2.8/src/pybind/mgr/cephadm/services/monitoring.py#L232

I think I found the problem there. The file path in the following lines
of what I linked should be `alerting/ceph_alerts.yml` instead of
`/etc/prometheus/alerting/ceph_alerts.yml`.

Is there any way around that particular problem, apart from
periodically copying the default configuration in
`/var/lib/ceph/<uuid>/prometheus/etc/prometheus/alerting/`?

Thanks,

-- 
Marc 'risson' Schmitt
CRI - EPITA
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux