Project

General

Profile

Feature #45996

adopted prometheus instance uses port 9095, regardless of original port number

Added by Tim Serong 12 months ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
cephadm/monitoring
Target version:
-
% Done:

0%

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

Description

When adopting prometheus (cephadm adopt --style legacy --name prometheus.HOSTNAME), the new prometheus daemon starts listening on port 9095, regardless of what port the original daemon was running on. This is a problem for upgrades, as if you have an existing grafana instance it will still be looking at the old prometheus port number.


Related issues

Related to Orchestrator - Feature #45652: cephadm: Allow user to select monitoring stack ports Duplicate
Related to Orchestrator - Bug #46561: cephadm: monitoring services adoption doesn't honor the container image New
Blocked by Orchestrator - Feature #48822: Add proper port management to mgr/cephadm Closed

History

#1 Updated by Sebastian Wagner 7 months ago

  • Tracker changed from Bug to Feature

#2 Updated by Sebastian Wagner 7 months ago

  • Related to Feature #45652: cephadm: Allow user to select monitoring stack ports added

#3 Updated by Sebastian Wagner 4 months ago

  • Blocked by Feature #48822: Add proper port management to mgr/cephadm added

#4 Updated by Sebastian Wagner about 1 month ago

  • Category changed from cephadm to cephadm/monitoring

#5 Updated by Sebastian Wagner about 1 month ago

  • Related to Bug #46561: cephadm: monitoring services adoption doesn't honor the container image added

Also available in: Atom PDF