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

Lead Time for Change doesn't show the graph under long interval #1044

Open
1 task done
apetryla opened this issue Aug 8, 2023 · 0 comments
Open
1 task done

Lead Time for Change doesn't show the graph under long interval #1044

apetryla opened this issue Aug 8, 2023 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@apetryla
Copy link

apetryla commented Aug 8, 2023

OpenShift version

Not related to OpenShift

Problem description

When I specify a longer interval in Grafana dashboard, in the Lead Time for Change graph I see N/A.

For example, we have a service, which deploys weekly. When I selected 4 days interval (aka Last 4 days), I didn't see any Curent interval value in the Lead Time for Change.

image

Playing around with Grafana options, I noticed that when the Interval is left as 1h , then the Current Interval value is N/A, however, when I increase Max data points by some amount so that Interval drops down to 30m, then I do see the expected current interval value:

image

Also, the corresponding graph under 1 week is:

image

When selecting more days, the graph itself also get's N/A

image

While increasing the Max data points seems to partially solve this:

image

and increasing even more solves completely for the last 7 days interval

image

Maybe there's a possibility to set parameters automatically depending on the interval (Last back) specified so that the graph and the Current interval get represented correctly? It might be autogenerating Max data points value? Or maybe making the deployment event duration longer? Or maybe somehow else? This may need some testing to find out the best solution. As for now, the only thing I can think of doing on my side is to choosing Max data points as big as the maximum interval (Last days) I want to support.

Also might be useful noting that Deployment frequency is working under all intervals which I tested.

Steps to reproduce

I was testing a service, which got deployed daily. I start seeing misrepresentations starting from Last 4 days.

Current behavior

Current interval of the Lead Time for Change graph isn't being calculated and the graph itself isn't represented under larger intervals (for example, Last 4 days).

Expected behavior

Graphs and values to be seen under all intervals which users could choose under normal conditions (there's data in prometheus etc.)

Code of Conduct

  • I agree to follow Pelorus's Code of Conduct
@apetryla apetryla added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

1 participant