I’m seeing one of my telemetry sensor graphs seeming to stop showing data once it gets up to 1 million height.
SELECT mean("npu_util_stats.packets.rate") AS "mean_npu_util_stats.packets.rate" FROM "juniper"."four_weeks"."juniperNetworks.jnpr_npu_utilization_ext" WHERE time > now() - 24h AND "_seq"='1' AND "device"='sv-a-960:10.101.128.7' GROUP BY time(:interval:) FILL(null)
When I monitor that string, the Chronograf picture shows a nice graph as I would expect…. Climbs during peak usage time from 200k…400k…600k…800k…1m , BUT, once it gets to 1 million, the graph shows bad gaps as if the graph slope rapidly drops off to nothing.
Is there a limitation in the default settings to only allow some graphs to go up to 1 million, and then that’s it ? If so, how do I allow it to go higher and display graphed data for 1 million and beyond ?
I’m seeing one of my telemetry sensor graphs seeming to stop showing data once it gets up to 1 million height.
SELECT mean("npu_util_stats.packets.rate") AS "mean_npu_util_stats.packets.rate" FROM "juniper"."four_weeks"."juniperNetworks.jnpr_npu_utilization_ext" WHERE time > now() - 24h AND "_seq"='1' AND "device"='sv-a-960:10.101.128.7' GROUP BY time(:interval:) FILL(null)
When I monitor that string, the Chronograf picture shows a nice graph as I would expect…. Climbs during peak usage time from 200k…400k…600k…800k…1m , BUT, once it gets to 1 million, the graph shows bad gaps as if the graph slope rapidly drops off to nothing.
Is there a limitation in the default settings to only allow some graphs to go up to 1 million, and then that’s it ? If so, how do I allow it to go higher and display graphed data for 1 million and beyond ?
-Aaron