Resource field hard-coding node ID
Description
Activity
Show:
Scott Theleman May 17, 2023 at 6:02 PM
Updating so that when node is changed (either by user in the dropdown or via a dashboard template variable being changed), we re-query to get proper resources for that node. This results in all resource references being updated to have the new node, plus also gets the proper set of resources available for that node. In cases where node does not have those resources, user will need to select; though if user then selects a node with the original set of resources and attribute, those will be retained.
Unresolved
Details
Details
Assignee
Scott Theleman
Scott ThelemanReporter
Mark Mahacek
Mark MahacekFix versions
Affects versions
Sprint
None
HB Grooming Date
May 08, 2023
HB Backlog Status
Refined Backlog
Story Points
5
Components
Priority
High
PagerDuty
PagerDuty Incident
PagerDuty
PagerDuty Incident
Created May 8, 2023 at 7:34 PM
Updated June 13, 2023 at 2:36 PM
When selecting the Node-Level Performance Data in the query editor of a Performance Data source, from the resource drop down, it appears to be hard-coding the
node[id].resource[id] combo. After selecting the resource and then changing the node, the panel will still display the data from the original node. This is especially a problem when using a dashboard variable. Manually enteringnodeSnmp[]in the resource filed avoids this issue, but this should be the default when selecting “Node-Level Performance Data”