Validate the plugin with Grafana 3.1.0

[FlorianLautenschlager]

Use Grafana 3.1.0 for development.

• Check on Windows
• Check on Linux

[sciffer]

Does not work for me, it does seems that grafana is adding 3 tailing 000 to the timestamps in the query which fails the whole query (and the datasource test as well I guess).

[FlorianLautenschlager]

Thanks, i will investigate on this later.

[sciffer]

BTW, It might be the result of using Logstash chronix output plugin.

On Jul 25, 2016 12:54 AM, "Florian Lautenschlager" notifications@github.com
wrote:

Thanks, i will investigate on this later.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#13 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF7u5Mbd4NXiS7GchAJR1KiyAwIsUoHtks5qZEGfgaJpZM4JLKZc
.

[FlorianLautenschlager]

So what i did (worked on windows):

1. Downloaded Grafana 3.1, Chronix-Server 0.3, and Chronix-Grafana
2. Copied the Chronix-Grafana directory to Grafana
3. Created a datasource for Chronix.
   
4. Created a dashboard
   

To your point with the tailing three zeros. Grafana returns unix time (seconds since 1970) while Chronix wants milliseconds since 1970 i simply multiplied it with 1000.

Note: What i not tested is the pipeline with Chronix-Logstash. And that one have to enter "metric:" is definitely an issue. Thanks @sciffer
Otherwise one will see this error:

[FlorianLautenschlager]

Created an issue for the "no field name specified in query..." see #14

[FlorianLautenschlager]

Chronix-Grafana and Grafana 3.1 also works on Linux.
Closing this issue.