You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2017/03/10 02:56:37 UTC

[jira] [Commented] (AMBARI-20391) Ambari Metrics Grafana Datasource plugin does not work when configured with a reverse proxy with subpath

    [ https://issues.apache.org/jira/browse/AMBARI-20391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904306#comment-15904306 ] 

Yusaku Sako commented on AMBARI-20391:
--------------------------------------

https://github.com/grafana/grafana/blob/v2.6.0/public/app/core/services/backend_srv.js#L68-L70 was adding extra subpath even though the URL already contains it.  The fix was to use the backendSrv.datasourceRequest, and not use backendSrv.get directly.

> Ambari Metrics Grafana Datasource plugin does not work when configured with a reverse proxy with subpath
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-20391
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20391
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 2.2.2
>            Reporter: Yusaku Sako
>            Assignee: Yusaku Sako
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-20391.patch, duplicate-grafana-grafana.png
>
>
> When Grafana is set up with a reverse proxy with sub path (http://docs.grafana.org/installation/behind_proxy/), Ambari Metrics datasource plugin does not work.
> With the subpath "/grafana", Grafana is making calls with incorrect URLs to the Metrics Collector.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)