Skip to content
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

Mixed "timeserie" and "table" metrics on the same Graph or Table throws an error #83

Closed
famzah opened this issue Nov 25, 2017 · 3 comments

Comments

@famzah
Copy link

famzah commented Nov 25, 2017

Hello,

The "Metrics" configuration tab lets us to add both "timeserie" and "table" targets for the Query. What is the purpose of this? Shouldn't Graphs allow only "timeserie" and Tables only "table" metrics? How should these be visualized even if the JSON datasource returns a proper response to such a query?

The other thing is that I can't find a proper way to return the results for such a mixed query. If I had a Graph, and if I request the first row to be "timeserie" and the second row to be "table", the first row is graphed. However, if I request (and return) data in the opposite order (first a "table" metric and then a "timeserie" one), this confuses Grafana and nothing is visualized.

Thank you for your time, and excuse me for being a total novice with Grafana and the Simple JSON Datasource plugin.

@andig
Copy link
Contributor

andig commented Aug 7, 2018

I've noticed a similar issue. The timeserie (btw. there is no such thing in English imho- should be timeseries?) allows returning results for multiple targets. table doesn't do so.

What would a proper response for mixed timeserie/table responses result in? Or shouldn't this be prevented as requested above?

@wernerdaehn
Copy link

Same question here. The response is clear, I think. It would be an array of objects and one object is a timeseries response, the other a table response.

But how is that used then??? Which element can render a table plus timeseries without a transformation?

@gwdawson
Copy link
Member

The Simple JSON Datasource is now deprecated, and as a result, we are closing all open issues in this repository.
Our development focus has shifted, and we are no longer actively maintaining this plugin.

This deprecation means that this plugin won’t receive any feature updates or bug fixes except critical security fixes.
After 6 months of the deprecation date (End of June 2024), no updates will be provided at all.

We recommend migrating to the Infinity datasource. Here are the migration steps you can follow.
Thank you for your understanding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants