Monitor Configuration
Configure how your monitors behave and how failures are detected.
Upstat provides several settings when configuring a monitor. These settings help reduce false positives, refine failure criteria, and match the monitor to your service behavior.
Failure Thresholds
Control how many consecutive failures are required before the monitor status changes:
- Failure Threshold: Number of failed checks before marking the monitor as failed
- Recovery Threshold: Number of successful checks before marking it healthy again
For example:
If your threshold is 3 and your check interval is 30 seconds, the monitor must fail for 90 seconds before an event is triggered.
Response Time Thresholds
You can set upper bounds on how long a request can take before it’s considered a failure.
- Maximum Response Time (in ms): If exceeded, the check is marked as failed
- This is particularly useful for HTTP/HTTPS monitors
- Helps you catch degraded performance, not just hard failures
Expected Status Codes (HTTP)
Define which HTTP status codes count as a success:
- Defaults to any 2xx status (e.g., 200–299)
- You can override this with any valid ranges (e.g., include 3xx for redirect-allowed cases)
Keyword Match (Optional)
You can define a string or keyword that must appear in the response body for a check to succeed.
- Case-sensitive by default
- Useful for verifying specific page content or API messages
- If the keyword is missing, the check fails—even if the status code is successful
Custom Headers
Send custom HTTP headers with your requests:
- Useful for authentication (e.g., API keys, bearer tokens)
- Also useful for simulating client behavior (e.g., custom User-Agent)
- Header data is stored securely and not shown in plaintext after save
Authentication (Basic Auth)
If your monitored endpoint requires basic authentication, you can enter credentials directly:
- Username and password will be encoded in the request
- Only used for HTTP/HTTPS monitors
- Credentials are securely stored
Summary
Monitor settings allow you to:
- Define failure sensitivity
- Monitor for both uptime and latency
- Validate responses beyond status codes
- Add authentication or headers when needed
These settings help you match the monitor’s behavior to your system’s real-world needs.
Learn more