Lead Time for Change doesn't show the graph under long interval #1044
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.
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 anyCurent interval
value in theLead Time for Change
.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:Also, the corresponding graph under 1 week is:
When selecting more days, the graph itself also get's
N/A
While increasing the
Max data points
seems to partially solve this:and increasing even more solves completely for the last 7 days interval
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 autogeneratingMax 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 choosingMax 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 theLead 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
The text was updated successfully, but these errors were encountered: