Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Grafana step size is ignored when InfluxDB or Cortex is used

Description

When you use Cortex or InfluxDB and you collect performance metrics with a higher resolution of 5 minutes (300s), it is not possible to query metrics in a higher resolution. In the Grafana data source, I've configured a Min time interval of 15s.

In Grafana the request is made with a step size of 15000ms but in the response shows a step size of 300000ms and the min time interval is ignored.

To rule this out, I've configured on the OpenNMS side

org.opennms.newts.query.minimum_step=15000

even it has nothing to do with Newts, but it doesn't solve the problem. I've tried Cortex and the Influx 2.0 data source with the same effects.

Acceptance / Success Criteria

None

Attachments

4
  • 11 Sep 2020, 03:55 PM
  • 10 Sep 2020, 03:54 PM
  • 10 Sep 2020, 03:54 PM
  • 10 Sep 2020, 03:53 PM

Lucidchart Diagrams

Activity

Show:

Ronny Trommer September 11, 2020 at 5:26 PM

Can confirm this solved the problem. Fixed Thanks

Patrick Schweizer September 11, 2020 at 4:57 PM

Ronny Trommer September 11, 2020 at 3:56 PM
Edited

Digging a little bit deeper, it seems we have this problem while reading the data. I made two panels one querying our own Helm data source with 15s minimal interval and the second using a native Flux query against InfluxDB shows the data is persisted with the correct resolution. The Helm data source just shows 5 min resolution whereas the InfluxDB panel shows the full collected data resolution.

Configuration

Details

Assignee

Reporter

Labels

Sprint

Affects versions

Priority

PagerDuty

Created September 10, 2020 at 3:55 PM
Updated September 11, 2020 at 5:26 PM
Resolved September 11, 2020 at 5:26 PM