Intended integration methods

The Qisutu integration configured in the interface uses the event interface of the separate Qisutu add-on. The connection is configured under Notifications with its event address and key. Events are transmitted as JSON over HTTPS; the access key is used as a bearer token. The connection test calls the selected connection’s test address and does not create a ticket.

Distributed data collectors have their own HTTPS interface to the central server. They are created under Settings → Distributed collectors and then assigned to a device under Configure → Collector. Use the data collector setup for this; an agent password does not replace their access key.

Interface	Purpose	Authentication
GET /api/health on the monitoring server	Simple reachability test of the web service; the response contains service: netzmonitor. This does not indicate the state of every monitored device.	No sign-in required.
GET /collector/v1/config/{ID}	Retrieve the assigned check configuration for the data collector.	Bearer key of this active data collector; HTTPS required.
POST /collector/v1/results/{ID}	Transmit measurement results from the data collector.	Bearer key of this active data collector; HTTPS required.
Qisutu event address from the add-on	Send problems and recovery notifications from monitoring to Qisutu.	Bearer key of the Qisutu connection.

The remaining /api/ routes serve the signed-in monitoring interface. They use a session; changes also require its corresponding CSRF token. They are not authorized through the Qisutu connection key. In this version, the monitoring interface has no configurable general webhook address for other ticket systems and no form for accepting arbitrary external monitoring events.