1
Create an account
Sign in with a Server Alerts account. This account is used for the portal and mobile apps, not for direct monitoring platform 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 server setup is enabled after approval.
3
Install the connector
Create a connector enrolment, then run the generated install command on the monitoring server. The connector makes outbound-only broker calls.
4
Verify your site
Return to the app or portal, refresh the pending setup, and enter monitoring credentials. Access is granted only after local verification.
Monitoring server requirements
- A supported monitoring platform: Nagios, Icinga, Checkmk, or Sensu.
- Local API or status access reachable by the connector from the monitoring server.
- Outbound HTTPS access from the monitoring server to the Server Alerts broker.
- Command/write access where the selected platform supports actions such as downtime, acknowledgement, or notification control.
What gets installed
- A local connector service running on the monitoring server.
- A local config file containing the broker token and platform connection details.
- A named systemd connector instance for each connected site when multi-instance install is used.
- A service that sends snapshots, polls queued commands, and forwards supported notifications to mobile devices.
- No inbound firewall rule is required for the monitoring server.
Sites
Not refreshedSite health alerts
Per siteServer Alerts monitoring dashboards
Per siteCreate a read-only monitoring dashboard for a single site. The full dashboard link is only shown when enabling or rotating the token.
Team invites
Not refreshedOperators can invite users and run site actions such as downtime, acknowledgements, and notification changes. Viewers can see site status and alerts only.
Audit trail
Not refreshedOperators can view site changes and actions for the sites they manage.
New monitoring server
Self-servicePending enrolments
Support
PilotSupport contacts, setup documentation, and diagnostic exports will be added here as the pilot moves closer to production.
How Server Alerts works
1
Create an account
Sign in with a Server Alerts account. This account is used for the portal and mobile apps, not for direct monitoring platform access.
2
Request a trial
Open Licence, request a pilot trial, and wait for LCW Labs approval. New server setup is enabled after approval.
3
Install the connector
Create a connector enrolment, then run the generated install command on the monitoring 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 monitoring credentials. Access is granted only after local verification.
Security reference
Traffic and connector design
- The connector makes outbound HTTPS requests to the Server Alerts broker. No inbound firewall rule is required for the monitoring server.
- In production, the connector's broker URL must use `https://`. Plain HTTP is accepted only when the broker is running on localhost for development.
- The local monitoring/statusjson URL can remain local to the connector, such as `http://127.0.0.1/nagios`, where the traffic never leaves the monitoring server.
- The broker queues supported monitoring actions for the connector to poll. The connector translates those requests into known monitoring commands locally.
- Connector bearer tokens are stored hashed by the broker and can be rotated from the LCW Labs admin portal.
Accounts and access
- Server Alerts accounts are separate from monitoring credentials. Monitoring credentials are used only to prove site access.
- Credential verification happens through the local connector, and completed verification payloads have passwords scrubbed server-side.
- Operators can invite users, change roles, update site health alerts, and queue site actions. Viewers can inspect site status and alerts only.
- Audit events record invites, role changes, alert settings, enrolments, licence overrides, connector token rotations, and site actions.