OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|1 month ago|
|examples||1 year ago|
|img||2 years ago|
|partials||1 year ago|
|.gitreview||1 month ago|
|LICENSE||2 years ago|
|README.rst||11 months ago|
|datasource.js||1 year ago|
|module.js||2 years ago|
|package.json||1 year ago|
|plugin.json||1 year ago|
|query_ctrl.js||2 years ago|
For more information on Monasca see the Monasca documentation
The Monasca Horizon plugin offers Horizon integration for Monasca. Among other things this plugin proxies the Monasca metrics API, using the Horizon session for authentication (as opposed to a Keystone token). This proxied API can be used to let this plugin access the Monasca API with the privileges of the user logged in to Horizon.
Note that this is entirely separate from Grafana’s user management.
Setting this up requires the following steps:
monasca-uiHorizon plugin. Specifically you will need to set
GRAFANA_LINKSto your dashboards which can either be JSON dashboards you point to or in-database dashboards. In the former case set the links’
pathattribute to the dashboard’s path or full URL. In the latter case, set the links’
False(or omit it entirely) and set their
pathattributes to the database dashboards’ names.
mod_proxy_http in Apache:
a2enmod proxy proxy_http
Configure the VHost hosting your Horizon instance with a proxy path that points at your Grafana instance (the example assumes you are running Horizon on Apache - adapt as required for other web servers):
ProxyPass "/grafana" "http://my.grafana.server:3000" ProxyPassReverse "/grafana" "http://my.grafana.server:3000"
[server/root_url] setting to point at your dashboard node’s
[server] root_url = %(protocol)s://%(domain)s/grafana
http://my.dashboard.server/monitoring/proxy(substitute your dashboard’s actual host name for
Steps (2) and (3) are neccessary to ensure both Grafana and Horizon are on the same Host/Port from the browser’s perspective. Otherwise the browser’s XSS protection mechanisms will omit the Horizon session cookie from any requests triggered by the
When combined with Grafana Keystone authentication this datasource supports using login credentials to authenticate queries.
Without the Grafana Keystone auth, this datasource can be used by inserting a keystone token into the datasource. To get a keystone token download the python-openstackclient, source credentials and run
openstack token issue.