Skip to main content
This guide walks the complete product path once. By the end you will have sent a real alert, watched an incident open, been notified, and acknowledged it.
Estimated time: 10 minutes. You need: an aciona.me account and a terminal with curl. No monitoring tool is required for this test.

Create your organization

When you create your account, aciona.me asks for an organization name. It is your company’s isolated space — everything you create from here belongs to it.If you were invited to an existing organization, skip this step.Details

Make sure you are an active member

For this first test you will be the on-call person yourself. As the creator of the organization you are already an owner, with every permission.Inviting the rest of the team can wait.Details

Create a team

Under Teams, create a team — say Platform — and add yourself as a member.The team is the unit of responsibility: it links services to on-call schedules.Details

Create a service

Under Services, create a service — say payments-api — and set the team you just created as responsible.Write down the exact name: you will use it in the test alert so routing finds this service.Details

Set up an on-call schedule

Under Schedules, create a schedule for the team with yourself as the only participant.For the test, use 24x7 rotation and your team’s timezone (for example America/Sao_Paulo). That way you are on call right now, whatever the hour.
Without an active schedule holding a valid participant, the incident is still created but has no owner — and falls back to a notification to the organization owners.
Details

Create an alert source

Under Alert sources, create a source of type Generic named Test.On save, aciona.me shows the webhook URL and the token.
The token is shown only once. Copy and store it now; afterwards it can only be rotated.
Details

Send a test alert

Replace <alertSourceId> and <sourceToken> with the values you just copied, and set service to your service’s exact name:
Test alert
The expected response is 202 Accepted. Any other code means a configuration problem — see Webhook returned an error.

Confirm the incident

Open Incidents in the dashboard. Within seconds a critical incident should appear with the title you sent, linked to the service, the team and you as the responder.Open it and read the timeline: alert received, incident created, responder notified.

Acknowledge the incident

Click Acknowledge (ACK). This records that someone is looking, moves the status to acknowledged and stops automatic escalation.Then resolve the incident to close the loop.

​
Done. What now?

Connect your real tool

Grafana, Prometheus, Datadog, CloudWatch, Zabbix or New Relic.

Invite your team

Roles, invites and permissions.

Build the real schedule

Weekly rotation, timezones and overrides.

Set up notifications

Mobile push, Slack and Microsoft Teams.

​
Checklist

  • Organization created
  • Team created with at least one member
  • Service created and linked to the team
  • Active schedule with a participant
  • Alert source created and token stored
  • Test alert returned 202
  • Incident appeared in the dashboard
  • Incident acknowledged