Monitor management · Customizing monitors
Configure request parameters, headers, and authentication
Set the HTTP method, expected response code, custom headers, and authentication details a monitor uses for checks. The guide follows the same monitor workflow used in the dashboard, so you can create, pause, remove, and troubleshoot monitors with confidence.
HTTP method and expected status
Advance Check Settings controls how Statixoup sends the request and decides whether the response is healthy.
- Choose GET, POST, PUT, DELETE, PATCH, or HEAD.
- Set Expected Status Code to the response code that means healthy for the endpoint.
- Use the real success code for the monitored workflow instead of assuming every healthy endpoint returns 200.
Custom headers
Use Custom Headers when the endpoint requires additional request metadata.
- Authorization or bearer token headers.
- Content-Type or Accept headers.
- Tenant, version, region, or routing headers.
- Any required app-specific header key and value.
HTTP authentication
If the monitored endpoint requires basic authentication, enter the username and password when Statixoup asks for credentials. For token-based authentication, add the token as a custom header such as Authorization.
Keep credentials scoped
Use monitoring-specific credentials or tokens with the least access needed to run the check.