Monitoring configuration

Settings

Platform defaults apply to new monitors. Live websites keep their own schedule, timeout, and retry policy.

General monitoring defaults

Used when a monitor is created. The scheduler keeps its own cadence after that.

Schedule
Every 900 seconds
HTTP concurrency
10
Request timeout
15000 ms
Retry count
2
Failure confirmation
2 cycles
Recovery confirmation
1 cycle
Edit monitors

Scheduler

The internal scheduler queues due monitors on its own. It does not require this dashboard to stay open and it does not use Jenkins.

Default interval
Every 900 seconds

Changing a live interval is done on that monitor. This page does not rewrite running schedules.

HTTP monitoring configuration

Availability checks run for every eligible discovered URL.

HTTP availability checks

Status, redirects, and response time

On

Redirect policy

Each monitor stores its own redirect limit and trailing-slash policy. Redirects that leave the allowed domains are rejected.

Expected status policy

2xx responses are healthy. A monitor can also treat selected 4xx or 5xx codes as healthy. Other 4xx and 5xx responses fail after the confirmation cycles.

Security and retention

Closed incidents and old check results are removed. Open incidents stay.

Keep integration secrets server-side

The Teams webhook stays in the server environment and is not returned by the API

On
Teams notification defaults

Retention is still the environment default.

System health

Taken from the API readiness check for PostgreSQL and Redis.

Service
Service healthy

PostgreSQL and Redis are reachable.