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

Include graph showing 30, 60 day (or more) history for each? #39

Closed
vynjo opened this issue Dec 11, 2019 · 4 comments
Closed

Include graph showing 30, 60 day (or more) history for each? #39

vynjo opened this issue Dec 11, 2019 · 4 comments
Labels
triage/duplicate Indicates an issue is a duplicate of other open issue.

Comments

@vynjo
Copy link

vynjo commented Dec 11, 2019

When I worked at Circonus I designed executive dashboards which showed year over year, quarter over quarter, etc., graphs to show devops teams 'how are we doing today' kinds of answers. It would be (IMHO) really interesting to show that same thing for each of our 4 key metrics (ALT, Deploy, MRT, CFR).

If interested I'd be happy to contribute, or give more specifics.

@etsauer
Copy link
Collaborator

etsauer commented Dec 12, 2019

@vynjo yes, thats definitely something that we're working on. The first step in this is to come up with a long term storage strategy for our prometheus data.

#23

@vynjo
Copy link
Author

vynjo commented Dec 12, 2019

When I worked at Circonus (now at Red Hat, btw - cmadsen@redhat.com) we always ran into customer dealing with long term Prometheus issues - we came up with IronDB (https://www.circonus.com/solutions/time-series-database/) and a grafana plugin (supporting histograms), and alerting. Pretty cool.

@vynjo
Copy link
Author

vynjo commented Dec 13, 2019

FWIW, a graphana plug/datasource in is https://github.com/circonus-labs/circonus-irondb-datasource. @kamelkev is incredibly knowledgeable (used to work with him)

@prakritikoller prakritikoller added this to To do in Pelorus Roadmap via automation Apr 27, 2020
@etsauer etsauer added the triage/duplicate Indicates an issue is a duplicate of other open issue. label Jun 11, 2020
@etsauer
Copy link
Collaborator

etsauer commented Jun 11, 2020

resolved by #77

@etsauer etsauer closed this as completed Jun 11, 2020
Pelorus Roadmap automation moved this from To do to Done Jun 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/duplicate Indicates an issue is a duplicate of other open issue.
Projects
No open projects
Development

No branches or pull requests

2 participants