Embedded Widget Missing Line Segments - Bad Rendering

###Insights Question Template

  • There are many ways to achieve a goal in Insights, tell us a bit about your end goal. What insights are you hoping to gain?

The line graphs on my embedded widgets are not rendering correctly.

  • Please include the URL to the Insights dashboard that needs addressing:

See “Avg Number Pending” on https://insights.newrelic.com/accounts/1032275/dashboards/874841


@jacob.dalton - This is being displayed in this way because we have slightly changed how we present NULL data visually in our charts. For MIN , MAX and AVERAGE. If data matching the query’s conditions is not found, or there are no numeric values returned by the query, it will return a value of NULL. The documentation has been updated to reflect this change :

https://docs.newrelic.com/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions

So where there is no data when we used to include a visual connection to present as a solid line when we received null, it would simply present as 0 , which isn’t a true representation of data.

1 Like

This makes dozens if not hundreds of embedded widgets I built with the previous behavior sort of useless. This might be a more a “true representation of the data” but you broke what I had deployed and replaced it with something worse. I don’t see an obvious way get this back to the previous behavior. It seems like timeseries line graphs are broken by design for sparse data.

I would much prefer that you had added a new parameter to the average function to get this new behavior than breaking the existing behavior with no way to get it back.

In the absence of a backwards compatible solution, I feel like the average function should accept a default value so that one can actually get line graphs when asking for line graphs rather than a mix of points and line segments.

I recognize the ambiguity of no events, but the point of a line graph is to identify trends. The previous behavior was useful for this and it was reasonably easy to work with the NULL is 0 behavior.

This solution here is like the kid who takes his ball and goes home when the group can’t decide on the rules for the game or whether someone is safe or out. If I wanted more “truth” I should at least have been able to opt in to it.

Thank you for that info @jacob.dalton - I understand this update isn’t perfect for everyone’s use cases! And we appreciate the feedback on it. I’ll get this passed over to the right team in here for you.