The menu "Probes" lists the probes of the tenant with their kind, component, interval and last result: ![The list "Probes" with the kind, component, interval and last result of each probe.](20261106-status-probes.png) The kinds and the rules are explained in [[Invantive Cloud Status/Concepts/Probes and Automatic Incidents|Probes and Automatic Incidents]]. "New probe" asks for the kind and opens its form. An HTTP(S) probe has the following fields: ![The form "New Probe" for an HTTP(S) probe with address, method, expected status and interval.](20261106-status-probe-http.png) - Name and Component: the name of the probe and the component it measures. - Address: the address requested. It must lie on a verified host name of the tenant or a known public service. - Method and Headers: the HTTP method and extra headers as a JSON object. A header value `{{secret}}` takes the secret. - Expected Status and Body Contains: the status code and an optional text the answer must contain. - Certificate: the number of days the certificate must still be valid; fewer fails the probe. - Secret: an optional secret, stored encrypted and never shown again. - Interval: the seconds between two polls, which count against the polls per hour of the tenant. - Time-Out: the milliseconds after which a poll fails. - Down After: the number of failures in a row after which the state changes. - State on Failure: the state the component gets. - Open an incident automatically and Enabled. A TDS probe asks for the server, database, user, password and the read-only query: ![The form "New Probe" for a TDS probe with server, database, user and query.](20261106-status-probe-tds.png) A probe of kind status page asks for the address of the other status page, its type and the component there to follow: ![The form "New Probe" for a probe that reads another status page.](20261106-status-probe-status-page.png) A push probe shows after saving the address that the component calls, and asks for "Silence Allowed" instead of an interval.