Project

General

Profile

Actions

Feature #46499

closed

Feature #45410: cephadm: Support upgrading alertmanager, grafana, prometheus and node_exporter

Requesting a "ceph orch redeploy monitoring" command, as an option, so user does not have to issue four separate commands to update the monitoring stack to the latest versions

Added by Nathan Cutler almost 4 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
cephadm/monitoring
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

It recently came to my attention that the process of updating the monitoring stack to the current latest version will involve issuing a number of commands - at least these four:

ceph orch redeploy prometheus
ceph orch redeploy grafana
ceph orch redeploy node-exporter
ceph orch redeploy alertmanager

(and possibly more to, e.g., restart the running services?)

I am opening this ticket to ask the following question: Would it make sense to implement a single command for this? I'm calling it "ceph orch redeploy monitoring" (working title).

The only reason for having such a command is to make life easier for users. If the user simply wants to be certain they are running the latest version of all the monitoring components, they could issue a single easy-to-remember command instead of a list of commands.


Related issues 2 (0 open2 closed)

Related to Orchestrator - Feature #45864: cephadm: include monitoring components in usual upgrade processResolved

Actions
Related to Orchestrator - Feature #48560: Spec files for each daemon in the monitoring stackClosed

Actions
Actions

Also available in: Atom PDF