All work

Select view

Select search mode

 

Parameter values are being sent for the wrong parameters in flow datasource queries

Unresolved

Description

Attempting to work around https://opennms.atlassian.net/browse/HELM-422 I found that the queries in the table panels aren’t working after conversion because some query parameter values are being sent with the wrong parameter name.

When I attempt to query the top 10 applications on a specific exporter node and specific ifIndex with asTableSummary, no data is returned. If I remove the exporterNode and ifIndex filters, it works. With the filters present, the URL sent to to the back end includes the correct ifIndex parameter name and value. It also includes includeOther with an integer value, but no exporterNode query parameter is present at all. If I also add includeOther to the query, then exporterNode is added as a query parameter with a value of true. It seems like exporterNode and includeOther have their wires crossed somewhere.

Environment

Meridian 2023 Grafana 9.5 Elasticsearch 7.19.9 w/ Drift 2.0.5 Grafana Plugin 9.0.3

Details

Assignee

Reporter

Fix versions

Affects versions

Sprint

HB Grooming Date

HB Backlog Status

Components

Priority

PagerDuty

Created May 17, 2023 at 4:05 PM
Updated June 27, 2023 at 12:36 AM

Activity

Scott ThelemanJune 20, 2023 at 7:47 PM

Marking as Resolved, will reopen if needed.

Scott ThelemanJune 20, 2023 at 7:46 PM

this appears to be fixed in version 9.0.5. In my testing with this version, the correct query parameters and parameter values are being sent in the URL. Please retry and let us know if the newer version has fixed these issues. Thanks!

David SchlenkMay 17, 2023 at 4:32 PM

Also FWIW the query generated when asTableSummary is not applied does seem to include the correct parameter names / values.

David SchlenkMay 17, 2023 at 4:13 PM

Query URL generated with only topN (returns data, despite presence of erroneous includeOther): api/datasources/proxy/uid/e16a261a-0a44-4d69-bd5a-511b74239678/rest/flows/applications?N=10&start=1684253337020&end=1684339737020&includeOther=53731

Query URL generated with exporterNode and ifIndex and dscp (all) added (doesn't return data, missing exporterNode): api/datasources/proxy/uid/e16a261a-0a44-4d69-bd5a-511b74239678/rest/flows/applications?N=10&start=1684252568522&end=1684338968522&ifIndex=3&dscp=1&includeOther=53731

Query URL generated with exporterNode and ifIndex and dscp (all) and includeOther added (doesn't return data, missing exporterNode set to true): api/datasources/proxy/uid/e16a261a-0a44-4d69-bd5a-511b74239678/rest/flows/applications?N=10&start=1684253520336&end=1684339920336&exporterNode=true&ifIndex=3&dscp=1&includeOther=53731

Manually changing the values of exporterNode and includeOther appropriately and issuing the request with curl does work as expected.