https://tracker.ceph.com/https://tracker.ceph.com/favicon.ico2020-11-26T19:00:38ZCeph Dashboard - Cleanup #48384: mgr/dashboard: remove GRAFANA_API_URL and validation through back-endhttps://tracker.ceph.com/issues/48384?journal_id=1801772020-11-26T19:00:38ZErnesto Puerta
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/180177/diff?detail_id=186147">diff</a>)</li></ul> Dashboard - Cleanup #48384: mgr/dashboard: remove GRAFANA_API_URL and validation through back-endhttps://tracker.ceph.com/issues/48384?journal_id=1801892020-11-27T11:59:07ZPatrick Seidensal
<ul></ul><p>The two points you've listed are valid and describe what the options are additionally used for, but its main purpose is to be able to configure the URL to be used for the ceph dashboard frontend to Grafana. There's no way I can think of in which we can remove this setting and being able to configure a URL that the frontend then uses to show Grafana graphs (except for implementing a reverse proxy for Grafana into Ceph Dashboard, but this issue doesn't seem to be about that).</p>
<p>But removing the check of the ceph dashboard backend would work.</p>
Would it make sense to change the scope of this issue to just
<ol>
<li>remove the test of the CD backend to Grafana and </li>
<li>implement something similar in the frontend?</li>
</ol> Dashboard - Cleanup #48384: mgr/dashboard: remove GRAFANA_API_URL and validation through back-endhttps://tracker.ceph.com/issues/48384?journal_id=1801902020-11-27T12:15:13ZErnesto Puerta
<ul></ul><p>Patrick Seidensal wrote:</p>
<blockquote>
<p>The two points you've listed are valid and describe what the options are additionally used for, but its main purpose is to be able to configure the URL to be used for the ceph dashboard frontend to Grafana. There's no way I can think of in which we can remove this setting and being able to configure a URL that the frontend then uses to show Grafana graphs (except for implementing a reverse proxy for Grafana into Ceph Dashboard, but this issue doesn't seem to be about that).</p>
</blockquote>
<blockquote>
<p>But removing the check of the ceph dashboard backend would work.</p>
Would it make sense to change the scope of this issue to just
<ol>
<li>remove the test of the CD backend to Grafana and </li>
<li>implement something similar in the frontend?</li>
</ol>
</blockquote>
<p>Yeah, my intention was to decide whether we want to keep the one you added (for front-end only purpose) and discard this other older one. In fact, we can simply keep the former name <code>GRAFANA_API_URL</code> and remove the validation back-end-grafana functionality. What do you think?</p> Dashboard - Cleanup #48384: mgr/dashboard: remove GRAFANA_API_URL and validation through back-endhttps://tracker.ceph.com/issues/48384?journal_id=1905542021-04-15T16:54:26ZErnesto Puerta
<ul><li><strong>Project</strong> changed from <i>mgr</i> to <i>Dashboard</i></li><li><strong>Category</strong> changed from <i>148</i> to <i>Monitoring</i></li></ul>