> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aciona.me/llms.txt
> Use this file to discover all available pages before exploring further.

# The alert never reached aciona.me

> No record from the monitoring tool shows up in the dashboard.

If nothing shows up in aciona.me, the problem is **before** ingestion: either the tool did not send, or the request never arrived.

## 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    |

<Note>
  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.
</Note>

## 2. Test connectivity directly

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

```bash theme={null}
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](/en/troubleshooting/webhook-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.

<AccordionGroup>
  <Accordion title="Corporate firewall or proxy" icon="shield">
    Environments with restricted egress need `ingress.aciona.me` explicitly allowed. Ask your network team to permit outbound HTTPS to that host.
  </Accordion>

  <Accordion title="Lambda inside a VPC" icon="cloud">
    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".
  </Accordion>

  <Accordion title="On-premises Zabbix or Grafana" icon="server">
    Internal servers frequently egress through a proxy. Configure the proxy in the tool or open a direct route.
  </Accordion>

  <Accordion title="DNS and TLS" icon="globe">
    From the tool's host, confirm that `ingress.aciona.me` resolves and that TLS negotiates.
  </Accordion>
</AccordionGroup>

## 4. Confirm you are looking at the right organization

If you belong to more than one organization, the dashboard only shows the active one. Switch and check.

## 5. Check that the source is active

A deactivated source rejects everything with `403`. Check the status under **Alert sources**.