Notifications
Notifications in Serversinc let you stay informed about important events happening on your servers and applications.
Notifications are sent to external services (like Slack, Discord, or any webhook) through Notification Channels.
Notification Channels
Section titled “Notification Channels”A Notification Channel is where Serversinc delivers events.
Each channel requires an URL:
- Slack webhook URL
- Discord webhook URL
- Any generic webhook URL
You can add multiple channels and customize which events each channel should listen for.
Selecting Events
Section titled “Selecting Events”When setting up a Notification Channel, you can select which events it should listen for.
- Only the selected events will be sent to that channel.
- Events are delivered as JSON payloads containing details about the object (server, application, deployment, etc.) that triggered the event.
Available Events
Section titled “Available Events”Events are grouped into categories:
Server Events
Section titled “Server Events”server.created– A new server was added.server.provisioning– Provisioning process started.server.provisioned– Server provisioned successfully.server.provisioning.failed– Provisioning failed.server.setup.started– Setup process started.server.setup.failed– Setup process failed.server.updated– Server configuration updated.server.deleted– Server removed.server.offline– Server became unreachable.server.online– Server came back online.
Application Events
Section titled “Application Events”application.created– A new application was created.application.updated– Application settings were updated.application.deleted– Application was deleted.application.offline– Application went offline.application.online– Application came back online.application.status.changed– Generic status change event.
Deployment Events
Section titled “Deployment Events”deployment.created– A new deployment was created.deployment.started– Deployment process started.deployment.deleted– Deployment was deleted.deployment.failed– Deployment failed.deployment.succeeded– Deployment completed successfully.
Command Events
Section titled “Command Events”command.pending– Command created and waiting to run.command.execution.started– Command started running.command.execution.succeeded– Command finished successfully.command.execution.failed– Command failed.
Build Events
Section titled “Build Events”build.started– Build process started.build.completed– Build finished successfully.build.failed– Build failed.
Example Use Cases
Section titled “Example Use Cases”- Slack/Discord alerts when a deployment fails.
- Webhook integration with monitoring tools (PagerDuty, Opsgenie, custom dashboards).
- Server offline alerts to respond quickly to downtime.
- Application online alerts to confirm successful recovery.