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

Add support for graphing multiple unrelated timeseries (metrics) in one graph #39

Open
juliusv opened this Issue Jan 22, 2013 · 15 comments

Comments

Projects
None yet
@juliusv
Copy link
Member

juliusv commented Jan 22, 2013

It should be possible to correlate multiple metrics in the same graph. The graphing UI should show (dynamically) multiple expression input fields to enable that.

@ghost ghost assigned juliusv Jan 22, 2013

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Dec 26, 2014

The console templates graph library supports this, we'd have to hook it into /graph though.

@syepes

This comment has been minimized.

Copy link

syepes commented Sep 7, 2016

+1

3 similar comments
@smalot

This comment has been minimized.

Copy link

smalot commented Sep 21, 2016

+1

@fmmr

This comment has been minimized.

Copy link

fmmr commented Oct 27, 2016

+1

@prasadus92

This comment has been minimized.

Copy link

prasadus92 commented Jan 5, 2017

+1

@alexellis

This comment has been minimized.

Copy link

alexellis commented Jan 28, 2017

~3 years on are we any closer to this happening? @brian-brazil

@juliusv

This comment has been minimized.

Copy link
Member Author

juliusv commented Jan 28, 2017

@alexellis No, nobody has spent time on this yet as far as I know.

@mindfulmonk

This comment has been minimized.

Copy link

mindfulmonk commented May 31, 2017

What about this query? It seems to work.

{__name__=~"node_filefd_allocated|node_filefd_maximum"}

@juliusv

This comment has been minimized.

Copy link
Member Author

juliusv commented May 31, 2017

@mindfulmonk That works, but has the downside of giving you back all data in one expression, and especially if you apply any transformation that will drop the metric name (rate, increase, sum, avg, etc.), then you won't know anymore what is what.

@tomwilkie

This comment has been minimized.

Copy link
Member

tomwilkie commented May 31, 2017

@juliusv

This comment has been minimized.

Copy link
Member Author

juliusv commented May 31, 2017

That really seems hacky to me (and could theoretically even conflict with future language changes). If we decide to do this in Prometheus itself at all, I'd prefer a full UI solution to this that allows you to add multiple input fields - either underneath each other or tabbed (like in OpenTSDB).

@G-Harmon

This comment has been minimized.

Copy link

G-Harmon commented Dec 28, 2018

+1 to this request

@davkal

This comment has been minimized.

Copy link
Contributor

davkal commented Jan 31, 2019

This is supported by Grafana's Explore, which is now available in grafana/grafana:latest as part of the Beta for the upcoming 6.0 release (and no longer behind a feature flag).

@codesome

This comment has been minimized.

Copy link
Member

codesome commented Feb 18, 2019

I was digging through issues for possible GSoC projects, so are we still keen on adding this into Prometheus?
/cc @juliusv

@juliusv

This comment has been minimized.

Copy link
Member Author

juliusv commented Feb 18, 2019

I think yes, but it's probably not large enough for a GSoC project. Maybe a day or so...

dmitsh pushed a commit to dmitsh/prometheus that referenced this issue Apr 17, 2019

Merge pull request prometheus#39 from draios/fix-urls-2
Fix backend URLs to use https instead of http
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.