-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing 'measurement' in template configuration causes invalid queries to be generated #25
Comments
Probably DB data was reset while saved index was used based on previously existing data. Will need to see:
to take this further. |
OS Ubuntu 16.04 graphite-api.yaml :
http://localhost:8000/metrics/find?query=*.cpu.cpu-total.{usage_user,usage_system} is OK. The influxgraph log file is never created. |
Will need to create the log directory if it does not exist. Obvious question, is there an influxdb running at See also #24 - there are outstanding blockers with influx |
The log directory is created. |
The log file entries are not intended correctly, should be:
In any case, have been able to reproduce, the queries look like the below from the docker container:
Measurement is Weirdly, running it locally outside docker works fine. Will have to do some debugging on the running instance, something might have changed with queries on the grafana side. Have not been able to reproduce by running the query manually in python interpreter inside the docker container which is even weirder. |
Is an issue with template configuration, it should be:
Not host.measurements The example config at the wiki is correct. The config should not be accepted without a valid measurement so have updated the title accordingly. |
Well ... That did it. Thanks :-) |
I believe you, no really I do 😃 |
Restarting docker container today, wanted to render : http://localhost:8000/render?from=-1h&target=*.cpu.cpu-total.{usage_user,usage_system}&format=svg
This was working before. But today I'm replied :
What can be this ?
The text was updated successfully, but these errors were encountered: