Project

General

Profile

Bug #42927

Feature #48314: mgr/dashboard: reverse proxy support

mgr/dashboard: alerts page's generatorURL is made of a hostname vs. FQDN

Added by Ernesto Puerta over 4 years ago. Updated almost 3 years ago.

Status:
New
Priority:
Normal
Category:
Monitoring
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

As a result of Prometheus composing the generatorURL with the hostname retrieved from os.Hostname, it would be unreachable from users outside the local network. Hence a FQDN is needed instead. This is a Prometheus issue already fixed by https://github.com/prometheus/prometheus/pull/717. This means Prometheus config option web.hostname needs to be set to the specific FQDN of the node.

This issue can't be fixed in the dashboard, but I opened it just to leave track of where its resolution should lie in. This should be fixed from within the deployment configuration.


Related issues

Blocks Dashboard - Feature #48315: mgr/dashboard: check Prometheus/Alertmanager support behind a reverse proxy New

History

#1 Updated by Ernesto Puerta about 3 years ago

  • Status changed from Won't Fix to New
  • Parent task set to #48314

#2 Updated by Ernesto Puerta about 3 years ago

  • Blocks Feature #48315: mgr/dashboard: check Prometheus/Alertmanager support behind a reverse proxy added

#3 Updated by Ernesto Puerta almost 3 years ago

  • Project changed from mgr to Dashboard
  • Category changed from 148 to Monitoring

Also available in: Atom PDF