Skip to main content
A service represents something that is monitored and has an owner: payments-api, checkout, auth, erp-integration, messaging-platform. It exists for one practical reason: to turn a technical alert into human responsibility.

​
Create a service

Under Services, owners and admins define:

​
How an alert finds its service

aciona.me resolves the service in this order:
1

Default service on the alert source

If the source has a fixed service configured, it is used. Handy when an entire tool monitors a single service.
2

Service hint in the alert

Each source type takes the hint from a different place:
3

Auto-registration

If the hint points at a service that does not exist yet, aciona.me can register it automatically so the alert is not lost.
Auto-registered services start with no responsible team. Review them regularly and link them to the right team — until then, their incidents have nobody on call.
Auto-registered services are not blocked by plan limits. That is deliberate: aciona.me never fails to create an incident because of a resource limit.

​
Service severity

The service’s default severity is the criticality context used when an alert arrives without a severity aciona.me recognizes. When the alert carries its own severity, that wins. The possible severities are critical, high, warning and info. See how each tool’s values are mapped in Severities.

​
Deleting a service

A service with open incidents cannot be deleted. Resolve or close those incidents first.

Teams

Alert sources