Docs / Observability and data
Uptime Kuma
Connect your own Uptime Kuma instance and let the agent list, create and manage its monitors.
Connect an existing Uptime Kuma instance to see its monitors in Pangea and let the agent manage them. Pangea keeps the credentials on its servers. The agent works through Pangea's monitor endpoints and never sees them.
Connect
As a team Administrator, open Connectors → Connect → Uptime Kuma and fill in:
| Field | Notes |
|---|---|
| Label | A friendly name, for example Production Uptime Kuma |
| Base URL | The public URL of your Uptime Kuma dashboard, for example https://status.example.com |
| Auth Token | Use this when the instance has 2FA enabled. Leave it empty to sign in with username and password |
| Username / Password | The instance login, if you don't use an auth token |
Pangea verifies the credentials against your instance before it saves the connection, then stores the secret encrypted. Enter secrets in this form, never in a conversation.
Your server must be reachable from Pangea over the internet. The URL must use port 80, 443 or 3001. Pangea refuses localhost, .local and .svc hosts, and any URL that resolves to a private, loopback or reserved IP address.
Verify
Open the instance's Monitors page, or select the connection in a conversation and ask for a list of existing monitors. Check their targets and status. Don't create a monitor just to test access.
Monitor changes
The agent can create, update, pause, resume and delete monitors. Give it the exact URL, monitor type, interval and the notifications you expect.
A monitor that exists does not prove that its alerts reach the right person. Check the notification setup separately.
Uptime Kuma has its own pages in Pangea. It does not feed the Monitoring overview.
Permissions
Team Administrators connect and remove this connection. They can limit who uses it with a member allow-list. Individual actions follow Auto Mode and Full Access.
Troubleshoot and disconnect
If reads fail, check the URL, the instance's health and the credentials. Don't open a private monitoring server to everyone just to make it reachable. Put it behind a public URL with authentication.
To retire access, remove the connection in Pangea and revoke the credential on the instance. Disconnecting does not stop any monitors. Pause or delete the ones you want to stop.