The Remote HTTP detector allows the anomaly detection to be performed by a remote HTTP service. The user can configure the alert to point to a REST endpoint. This endpoint must be able to accept the ThirdEye detection payload and respond back with a specific response API. Upon successful exchange, the response is shared back with downstream operators thereby completing the detection workflow.
Here is a sample request payload that is sent to the remote http service.
Copy
Ask AI
{ "startMillis": 1553468646555, "endMillis": 1653468646555, "spec": { "help": "This is the anomaly detector spec object which is sent as is to the remote service", ... }, "dataframe": { "seriesMap": { "timestamp": [1, 2, 3], "current": ["v1", "v2", "v3"] } }}
Here’s a sample response payload. The endpoint must return a json that follows this schema for ThirdEye to execute successfully.In this case, the expectation is to receive a dataframe in a format defined below with a predefined set of columns.
current: The value of the metric at different timestamps
timestamp: The timestamps associated with the observed values of the metric
value: baseline/predicted values of the metric
lower_bound: The allowed lower bound of the metric
upper_bound: The allowed upper bound of the metric