Fixed
Details
Assignee
Christian PapeChristian PapeReporter
Mark MahacekMark MahacekHB Grooming Date
Apr 25, 2022HB Backlog Status
BacklogDoc Backlog Status
NBStory Points
8Components
Sprint
NoneFix versions
Priority
Minor
Details
Details
Assignee
Christian Pape
Christian PapeReporter
Mark Mahacek
Mark MahacekHB Grooming Date
Apr 25, 2022
HB Backlog Status
Backlog
Doc Backlog Status
NB
Story Points
8
Components
Sprint
None
Fix versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created March 16, 2022 at 10:21 PM
Updated May 24, 2022 at 7:45 AM
Resolved May 24, 2022 at 7:45 AM
When collecting some values, especially from REST APIs via an XML Collector, the provided data comes back as a string value. Sometimes this string value represents a state that we can't currently persist over time. If we were able to send the value through an enumeration, the value could be persisted as an integer to track over time.
such as:
If there was an enumeration such as:
these numbers could easily be persisted with our current JRB/RRD models.
My initial though would be for this to be an extension of resource types, where enumerations could be defined like:
and then collected as following, assuming the "status" xpath refers to a field that is a string in the source:
Or I guess as a "ReverseEnumLookupPropertyExtender"