Skip to main content
Enterprise only
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.

Inputs

"targetProperty": "current": The data on which to perform detection. It should contain the historical data to use for training.

Parameters

Payloads format

Request payload

Here is a sample request payload that is sent to the remote http service.

Response Payload

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
  • anomaly: boolean if this is or isn’t an anomaly.

Example

Full alert