You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Metrics that have no data run for a certain time period will have 0 data point even though no data was actually run. Likely some where in the front-end code NULLS are being graphed as 0s instead of just skipping the data point. See how this affects an Average Age chart below that has only had new rows written to the table twice in the last two weeks:
Describe the solution you’d like
Either by default or as an option, I'd like the data points that are NULLS to not be plotted on the graph at all and just connect the line to the next NON-NULL data point, this would make the current graph look more like the blue line below.
Describe the alternative you’ve considered or used
Have not really found a work around for this. This also causes a lot of false anomalies when no data is run for a day, I've worked around this issue with the anomalies by essentially turning them off by setting the Threshold to be very high.
The text was updated successfully, but these errors were encountered:
Tell us about the problem you're trying to solve
Metrics that have no data run for a certain time period will have 0 data point even though no data was actually run. Likely some where in the front-end code NULLS are being graphed as 0s instead of just skipping the data point. See how this affects an Average Age chart below that has only had new rows written to the table twice in the last two weeks:
Describe the solution you’d like
Either by default or as an option, I'd like the data points that are NULLS to not be plotted on the graph at all and just connect the line to the next NON-NULL data point, this would make the current graph look more like the blue line below.
Describe the alternative you’ve considered or used
Have not really found a work around for this. This also causes a lot of false anomalies when no data is run for a day, I've worked around this issue with the anomalies by essentially turning them off by setting the Threshold to be very high.
The text was updated successfully, but these errors were encountered: