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

Service hint in the alert

Each source type takes the hint from a different place. It matches an existing service of the organization by slug or name (case-insensitive):
2

Auto-registration (explicit field only)

If an explicit field points at a service that does not exist yet, aciona.me registers it automatically so the alert is not lost — even when the source has a default service. Derived hints (job, host, metric…) never create a service.
3

Default service on the alert source

With no hint, or a derived hint that did not match, the fixed service configured on the source is used. Handy when an entire tool monitors a single service.
Auto-registered services are born in the default team of the alert source that created them. If the source has no default team, they start with no responsible team: review them under Configuration → Services and link them to the right team.

​
Service team

The team decides who gets paged. Owners and admins set it in two places:
  • under Configuration → Services, in the Team column (including No team). The page warns how many services have no team;
  • on the team page, under Services → Link service. If the service already belongs to another team, aciona.me asks for confirmation before moving it. Unlink leaves the service without a team.
When the alert has no service, or its service has no team, the incident goes to the alert source default team, without changing the service. With no default team, it goes to the organization owners.
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