# Alerting and Monitoring

Each machine runs a Prometheus and Alertmanager instance which monitors the services running on the same machine.

If Prometheus and/or Alertmanager are down, or the entire machine is down/unresponsive then HealthChecks.io is used as a dead-mans-hand alert. Periodic heartbeat pings are sent by a cron script (`~/healthchecks.sh`) every 5 minutes, with a 10 minute grace period.

All services are integrated with PagerDuty for alerts.

{% content-ref url="/pages/ud8BcY3LqFgG7wrR9MNH" %}
[Prometheus](/ethereum-dev/infrastructure/alerting-and-monitoring/prometheus.md)
{% endcontent-ref %}

{% content-ref url="/pages/fOljlY8Mdp94TYLZMrg2" %}
[HealthChecks.io](/ethereum-dev/infrastructure/alerting-and-monitoring/healthchecks.io.md)
{% endcontent-ref %}

{% content-ref url="/pages/tuIrcOP19fAC24doLzOB" %}
[PagerDuty](/ethereum-dev/infrastructure/alerting-and-monitoring/pagerduty.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.eridian.xyz/ethereum-dev/infrastructure/alerting-and-monitoring.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.