Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
AND operation of 2 detectors. A different metric can also be provided by passing an input current. The detector will run on this input.
{
"sourcePlanNode": "anomalyDetector"
}
{
"targetProperty": "current",
"sourcePlanNode": "controlDataFetcher",
"sourceProperty": "controlDataOutput"
}
| name | description | default value |
|---|---|---|
component.ignore | If true, anomalies that are not detected by the postProcessor detector will be filtered. | false |
component.valueName | Optional. The name of the metric. Used in the label: "{ValueName} not anomalous according to <TYPE> detector" | Value |
{
"name": "root",
"type": "PostProcessor",
"params": {
"type": "OFFSET_AGGREGATION",
"component.ignore": "true", # filter anomaly in notifications an ui by default,
"component.valueName": "Business KPI", # customize label
"component.offsets": ["P7D", "P14D"], # parameter of the detector
...
"component.aggregation": "MEDIAN" # parameter of the detector
},
"inputs": [
{
"sourcePlanNode": "anomalyDetector"
}
]
}
{
"name": "root",
"type": "PostProcessor",
"params": {
"type": "OFFSET_AGGREGATION",
"component.ignore": "true",
"component.valueName": "GuardRail KPI", # customize label,
"component.timestamp": "ts", # time column of the side input
"component.metric": "sideMetric" # column in the side input to run detector on
"component.offsets": ["P7D", "P14D"], # parameter of the detector
...
"component.aggregation": "MEDIAN" # parameter of the detector
},
"inputs": [
{
"sourcePlanNode": "anomalyDetector"
},
{
"targetProperty": "current",
"sourcePlanNode": "controlDataFetcher",
"sourceProperty": "controlDataOutput"
}
]
}
Was this page helpful?