Bug #44577
Feature #43705: cephadm: on config change, restart appropriate daemons
cephadm: reconfigure Prometheus on MGR failover
Status:
Closed
Priority:
High
Assignee:
-
Category:
cephadm/monitoring
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:
Description
we have to make sure, Prometheus knows the new prometheus exporter endpoint:
- Generate a new prometheus config pointing to the now-active MGR endpoint
- Deploy configs to proemtheus instances
Related issues
History
#1 Updated by Sebastian Wagner 8 months ago
- Category changed from cephadm to cephadm/monitoring
#2 Updated by Sebastian Wagner 7 months ago
- Tracker changed from Feature to Bug
- Subject changed from cephadm: restart Prometheus, if new MGR is deployed to cephadm: reconfigure Prometheus on MGR failover
- Description updated (diff)
- Priority changed from Normal to High
- Regression set to No
- Severity set to 3 - minor
#3 Updated by Sebastian Wagner 7 months ago
- Related to Feature #43687: cephadm: haproxy (or lb) added
#4 Updated by Sebastian Wagner 7 months ago
How can we make sure, we're not missing any MgrMap updates, as we have to deal with a mgr/cephadm failover simultaneously.
#5 Updated by Sebastian Wagner 7 months ago
- Status changed from New to Closed
no need. prometheus already knows all instances.