Issues
Node metadata not always returned
Unresolved
Description
is caused by
Details
Assignee
UnassignedUnassignedReporter
Mark MahacekMark MahacekLabels
Fix versions
HB Grooming Date
Jun 06, 2023HB Backlog Status
Refined BacklogPriority
Medium
Details
Details
Assignee
Unassigned
UnassignedReporter
Mark Mahacek
Mark MahacekLabels
Fix versions
HB Grooming Date
Jun 06, 2023
HB Backlog Status
Refined Backlog
Priority
PagerDuty
PagerDuty
PagerDuty
Created May 31, 2023 at 2:22 AM
Updated August 7, 2023 at 7:23 PM
Activity
Show:
Scott ThelemanJuly 7, 2023 at 2:37 PM
Fix being done in:
Scott ThelemanJuly 6, 2023 at 8:59 PM
Can confirm that the Measurements API does not send back node metadata for items that it could not find resources for. Looking into a server-side fix that would return node metadata for any requested resources.
Scott ThelemanJuly 5, 2023 at 9:31 PM
could you send me an example response which has response metadata for some nodes but not others? Trying to determine whether this is a server-side or client-side issue, or if the client-side can have a fallback if server does not include the label info in the metadata.
When generating a single panel based on a multi-value variable for a Performance DS, the
nodeToLabel()
formatter only applies to some of the returned nodes so that some nodes have anodelabel
and others have aFID:FID
. Looking at the query inspector, the response metadata for nodes is missing instances for theFIS:FID
nodes. It appears that these nodes do not have SNMP attributes collected, though the expectation is that the node label from inventory should still be returned.Tested against Horizon 31. Replicated on both Helm 8.0.4 and Plugin v9.0.4, though there was a difference in which nodes did and did not return metadata.