Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.extractor.live/llms.txt

Use this file to discover all available pages before exploring further.

Behavior Detector sends GET/POST requests and expects response within specified timeout. Use cases
  • API Uptime Monitoring: A DeFi platform uses the Network Monitor to periodically send HTTP GET requests to its critical public API endpoint. If the API doesn’t respond within the specified timeout (indicating downtime or a crash), the monitor triggers an alert to the ops team. This helps the team react quickly to restore service and minimize disruption for users relying on that API.
  • Third-Party Service Health Check: An exchange sets up the Network Monitor to watch a third-party price feed service via regular HTTP requests. If the price feed fails to respond or returns an error (for example, due to a provider outage), the monitor detects it and notifies the system to switch to a backup feed. The team is also alerted, so they can contact the provider or investigate issues before it affects trading operations.

​
Configuration

1

Name

Enter a descriptive name for your monitor, for example: “Network Monitor”.
2

Cron

Enter a cron expression to define the schedule.
3

URL

The endpoint URL to monitor.
4

Request type

HTTP method to use (GET or POST).
5

Request Body

Optional request body for POST requests.
6

Authorization header

Optional authorization header value.
7

Response pattern

Expected pattern in the response body.
8

Latency (msec)

Maximum acceptable response time in milliseconds.
Alert example