grafana-gnocchi-datasource icon indicating copy to clipboard operation
grafana-gnocchi-datasource copied to clipboard

Gnocchi datasource for Grafana 3 and 4

Results 23 grafana-gnocchi-datasource issues
Sort by recently updated
recently updated
newest added

I've been using grafana-gnocchi-datasource token based authentication with a small hacky service that runs regularly and updates the token in the database. https://gitlab.com/Baggypants/grafana-gnocchi-openstack-token-renewer. It would be helpful if there was...

I'm not able to use the Keystone Auth Mode. Even if the services are using the same URL, they don't share the same port. As a result, I can't use...

Project name may contain special characters so it's better to use project id when doing authentication

https://github.com/gnocchixyz/grafana-gnocchi-datasource/blob/ee3fbebf47d099402b692f3086bb99e1c8441db7/src/datasource.ts#L901

When selecting a single instance, the query passed to gnocchi seems to be incorrect. ``` params: {filter: "instance_id in cb5f8625-155c-4528-a51e- "Invalid input: expected a list for dictionary value @ data['in']['instance_id']”...

Some response jsons will include “Infinity”, which JSON.parse can’t handle. E.g. "{"measures": {"aggregated": [["2018-10-10T13:10:00+00:00", 300.0, Infinity]]}}" The plugin could probably replace those occurrences with 1e+99999, avoiding such parsing errors.

Using *Auth Mode keystone*, with all settings OK (URL endpoint http://controller:5000, domain, project, user and password) and CORS enabled. Grafana gets the Keystone token and the Gnocchi endpoint, and goes...

question

Hello, we are using the Gnocchi Grafana datasource v1.6.2 and are trying to query the metrics of an OpenStack cluster. We noticed that the dynamic aggregate for the instance metric...

Hello, we are using the current **stable** Gnocchi Grafana Datasource plugin in to query the metrics of an OpenStack cluster. At the moment, I am trying to use the **dynamic...

When crafting queries in the Grafana UI, it would be helpful if the names of available metrics were discoverable from within the "metric regex" field, rather than requiring an out-of-band...