Chronograf: Support for multiple graphs for each value of a tag in dashboard

Created on 2 Mar 2017  路  9Comments  路  Source: influxdata/chronograf

Now:
screen shot 2017-03-02 at 16 41 27

Hope so: (DATA EXPLORE) or (CPU0 Usage, CPU1 Usage ...etc)
screen shot 2017-03-02 at 17 02 33

stale

Most helpful comment

@lin-credible Ah, I see what you are saying. Thanks for the examples of what you are looking for. We could probably build something that generate a graph per provided tag, that sounds like it might be a pretty nice feature. I'm going to rename this ticket and push it later in the 1.2.x timeline.

All 9 comments

Could I change the default layout of 'CPU Usage' and add a 'groupbys' ?

cpu_disk_groupby

I changed the 'cpu.json': 馃槀
screen shot 2017-03-02 at 18 19 12

@lin-credible This looks like it might be an improvement, do you want to submit a PR?

@nhaugo

screen shot 2017-03-03 at 18 29 50
As the picture above, I think we need a better method to handle this...
Is there a better way to show so many cpu's graph?
Here is the graph of netdata:

netdatas

@lin-credible Ah, I see what you are saying. Thanks for the examples of what you are looking for. We could probably build something that generate a graph per provided tag, that sounds like it might be a pretty nice feature. I'm going to rename this ticket and push it later in the 1.2.x timeline.

I have a bad idea:
screen shot 2017-03-04 at 14 55 06

*.json file:
screen shot 2017-03-04 at 15 22 28

I got this:
screen shot 2017-03-04 at 15 05 21

馃敂 As we all know, the number of CPUs per server is different, so we can't solve it by my stupid solution. 馃槀


I'm new to TICK, so I need to learn it's framework and some details of the architecture more. I'm curious about the TICK, thanks so ... much for your amazing job.

this will be solved once we complete #2962

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

This issue has been automatically closed because it has not had recent activity. Feel free to reopen if this issue is still important to you. Thank you for your contributions.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

mkarlesky picture mkarlesky  路  3Comments

goller picture goller  路  3Comments

jackzampolin picture jackzampolin  路  6Comments

krysjoseoctanio picture krysjoseoctanio  路  4Comments

karel-rehor picture karel-rehor  路  5Comments