1
Create an account
Sign in with a Server Alerts account. This account is used for the portal and mobile apps, not for direct Nagios access.
Verified sites
0
Sites available to this account
Pending setup
0
Connector enrolments
Critical sites
0
Sites needing attention
Plan
Checking
Licence status
How Server Alerts works
Start here2
Request a trial
Open Licence, request a pilot trial, and wait for LCW Labs approval. New Nagios server setup is enabled after approval.
3
Install the connector
Create a connector enrolment, then run the generated install command on the Nagios Core server. The connector makes outbound-only broker calls.
4
Verify your site
Return to the app or portal, refresh the pending setup, and enter your Nagios credentials. Access is granted only after local verification.
Nagios server requirements
- Nagios Core 4.x with `statusjson.cgi` enabled and reachable locally by the connector.
- A Nagios account that can read hosts/services and submit external commands for actions such as downtime.
- Outbound HTTPS access from the Nagios server to the Server Alerts broker.
- Write access for the connector service to the Nagios command file, usually `/usr/local/nagios/var/rw/nagios.cmd`.
What gets installed
- A local connector service running on the Nagios server.
- A local config file at `/etc/nagios-mobile/connector.json` containing the broker token and Nagios connection details.
- A systemd service that sends snapshots, polls queued commands, and forwards Nagios notifications to mobile devices.
- No inbound firewall rule is required for the Nagios server.
Sites
Not refreshedNew Nagios server
Self-servicePending enrolments
Licence
Not checkedRequest a Server Alerts pilot trial for this account.
Account security
Not checkedUse an authenticator app to protect portal sign-ins.
Support
PilotSupport contacts, setup documentation, and diagnostic exports will be added here as the pilot moves closer to production.