The alert never reached aciona.me

1. Confirm the tool actually fired

Before looking at aciona.me, check in the tool itself whether the alert fired and the notification was sent:

Tool	Where to look
Grafana	Alert history and contact point delivery log
Alertmanager	The Alertmanager UI, or its command-line query tool
Datadog	Monitor history and webhook log
New Relic	Workflow history and destination status
Zabbix	Action report and server log
CloudWatch	Alarm history and Lambda logs in CloudWatch Logs

If the tool never recorded the send, the problem is its configuration — alert condition, notification policy, workflow filter, filtered action. aciona.me is not involved.

2. Test connectivity directly

Isolate the problem with a manual request to the ingestion endpoint:

curl -i -X POST "https://ingress.aciona.me/webhooks/<alertSourceId>" \
  -H "Content-Type: application/json" \
  -H "X-Aciona-Token: <sourceToken>" \
  -d '{"externalId":"connectivity-test","title":"Test","severity":"info","status":"firing"}'

Returned 202 — URL and token are fine. The problem is in the tool’s configuration.

Returned another code — see Webhook returned an error.

No response at all — a network problem. Continue below.

3. Check outbound networking

The monitoring tool must be able to reach ingress.aciona.me on port 443.

Corporate firewall or proxy

Environments with restricted egress need ingress.aciona.me explicitly allowed. Ask your network team to permit outbound HTTPS to that host.

Lambda inside a VPC

A Lambda in a private subnet with no NAT Gateway has no internet access. This is the most common cause of “the Lambda runs without a visible error, but nothing arrives”.

On-premises Zabbix or Grafana

Internal servers frequently egress through a proxy. Configure the proxy in the tool or open a direct route.

DNS and TLS

From the tool’s host, confirm that ingress.aciona.me resolves and that TLS negotiates.

Introduction

Getting started

Organizations

Teams

Services

On-call

Incidents

Notifications

Troubleshooting

The alert never reached aciona.me

1. Confirm the tool actually fired

2. Test connectivity directly

3. Check outbound networking

4. Confirm you are looking at the right organization

5. Check that the source is active

​1. Confirm the tool actually fired

​2. Test connectivity directly

​3. Check outbound networking

​4. Confirm you are looking at the right organization

​5. Check that the source is active

1. Confirm the tool actually fired

2. Test connectivity directly

3. Check outbound networking

4. Confirm you are looking at the right organization

5. Check that the source is active