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

Graph: timeshift per query #22942

Open
szerwi opened this issue Mar 21, 2020 · 11 comments
Open

Graph: timeshift per query #22942

szerwi opened this issue Mar 21, 2020 · 11 comments

Comments

@szerwi
Copy link
Contributor

szerwi commented Mar 21, 2020

What would you like to be added:
It would be nice to display different timeranges on single graph panel.
Currently it is available only on 2 separate panels like this:
image
To make it on one graph panel, timeshift needs to be set differently for each query.

Why is this needed:
Ability to make comparisons between different timeranges on single graph.

@cpmoore
Copy link

cpmoore commented Sep 1, 2020

+1 for this

We currently display the current value and the previous week's value on the same graph, this makes it easier for a quick comparison of trends for people not familiar with the normal values.
We have some data in prometheus and for this we just use the offset keyword, however we are in the process of converting some data to other databases which do not support this.

@davidnewhall
Copy link

Paid enterprise customer here. We could use this too! @cpmoore describes our use case. Except we used to use timeShift() in graphite and we're now in cloudwatch metrics. Thanks!

@cpmoore
Copy link

cpmoore commented Jul 29, 2021

@davidnewhall
In case it helps you, I was able to use this plugin as a workaround for now https://github.com/AutohomeCorp/autohome-compareQueries-datasource

@davidnewhall
Copy link

davidnewhall commented Jul 29, 2021

I found that and am dropping it into dev now. Thanks!
EDIT: I don't think it works with cloudwatch
Screen Shot 2021-07-28 at 5 45 23 PM

@matejanajdanov
Copy link

Any updates on this?

1 similar comment
@nereus-east
Copy link

Any updates on this?

Copy link
Contributor

This issue has been automatically marked as stale because it has not had activity in the last year. It will be closed in 30 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant. Thank you for your contributions!

Copy link
Contributor

This issue has been automatically closed because it has not had any further activity in the last 30 days. Thank you for your contributions!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 21, 2024
@drewhammond
Copy link

@gabor Can this be reopened based on your comment here?

This is a very valuable feature

@gabor
Copy link
Contributor

gabor commented Mar 11, 2024

this is still actual, reopening.

(thanks for the pointer @drewhammond )

@gabor gabor reopened this Mar 11, 2024
@gabor
Copy link
Contributor

gabor commented Mar 11, 2024

(i assigned this to the dashboard-squad, but not sure if that's the right home for the issue. feel free to reassign it. thanks!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 📝 Backlog
Development

No branches or pull requests

10 participants