An inbound integration lets the alerts of a monitoring tool set the state of components. Grafana, Elastic APM and a generic JSON format are recognised. The menu "Integrations" lists the integrations of the tenant:  An integration has the following fields: - Code and Name: the code and name of the integration. - Mapping: per alert name the component and the state it gets while the alert fires, as JSON. A resolved alert returns the component to operational. - Require an HMAC-SHA256 signature of the body: refuse alerts without a valid signature. ```json { "exact_nl_invoice_timeouts": { "component": "exact-online-netherlands", "stateWhenFiring": "partial_outage" } , "cloud_api_5xx_rate": { "component": "invantive-cloud-api", "stateWhenFiring": "degraded_performance" } } ``` After "Create", the address of the alerts and the secret are shown once. The monitoring tool posts its alerts to `/api/v1/integrations/<key id>/alerts` with the secret in the header `X-Status-Secret`, and the HMAC-SHA256 of the body in `X-Status-Signature` when a signature is required. The list "Mapping" shows per alert the component and state. "Delete" removes an integration. "Rotate secret" issues a new secret. The previous secret stays valid for the chosen number of hours, 24 by default and at most 168, so the monitoring tool can be changed without losing alerts.