Proposal
Extend the existing Splunk Observability scaler's queryAggregator metadata to support sum, count, and latest in addition to avg, max, and min.
The current implementation rejects these values as invalid. The proposed behavior is:
sum: return the sum of the datapoint values received during the query window.count: return the number of datapoints received during the query window.latest: return the most recently received datapoint value.
Existing aggregator behavior and validation remain unchanged.
Use-Case
SignalFlow queries can return multiple datapoints or series. Depending on the metric, scaling may need the total value, the number of datapoints, or the most recently received value rather than only the minimum, maximum, or average.
Is this a feature you are interested in implementing yourself?
Yes. The implementation is in #8098.
Anything else?
This extends an existing metadata field and does not add a new scaler, schema field, or deployment manifest.
Proposal
Extend the existing Splunk Observability scaler's
queryAggregatormetadata to supportsum,count, andlatestin addition toavg,max, andmin.The current implementation rejects these values as invalid. The proposed behavior is:
sum: return the sum of the datapoint values received during the query window.count: return the number of datapoints received during the query window.latest: return the most recently received datapoint value.Existing aggregator behavior and validation remain unchanged.
Use-Case
SignalFlow queries can return multiple datapoints or series. Depending on the metric, scaling may need the total value, the number of datapoints, or the most recently received value rather than only the minimum, maximum, or average.
Is this a feature you are interested in implementing yourself?
Yes. The implementation is in #8098.
Anything else?
This extends an existing metadata field and does not add a new scaler, schema field, or deployment manifest.