Actions
Feature #45652
closedcephadm: Allow user to select monitoring stack ports
Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
cephadm/monitoring
Target version:
-
% Done:
0%
Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
User must be able to change the ports settings for the monitoring stack
We can continue using as default:
port_map = {
"prometheus": [9095], # Avoid default 9090, due to conflict with cockpit UI
"node-exporter": [9100],
"grafana": [3000],
"alertmanager": [9093, 9094],
}
Updated by Sebastian Wagner almost 4 years ago
- Description updated (diff)
- Category changed from cephadm to cephadm/monitoring
Updated by Sebastian Wagner almost 4 years ago
- Related to Feature #45876: cephadm: handle port conflicts gracefully added
Updated by Sebastian Wagner over 3 years ago
- Related to Feature #45996: adopted prometheus instance uses port 9095, regardless of original port number added
Updated by Sebastian Wagner about 3 years ago
- Related to Feature #48822: Add proper port management to mgr/cephadm added
Updated by Sebastian Wagner almost 3 years ago
- Is duplicate of Bug #50359: Configure the IP address for the monitoring stack components added
Updated by Sebastian Wagner almost 3 years ago
- Status changed from New to Duplicate
Actions