# Uptime Monitoring

Knowing your agent is deployed is not the same as knowing it is reachable. Monitoring tracks whether your agents are online and responding, surfaces daily and historical uptime, and alerts the right people when something breaks. Open **Observatory > Monitoring** to see the status of every agent at a glance.

{% hint style="warning" %}
Monitoring is enabled by default for agents created with legacy templates. For agents based on the modern template, activation is available upon request. [Contact support](/resources/support.md#contact-us) to get started.
{% endhint %}

<div data-with-frame="true"><figure><img src="/files/Q2OOkgdaGAGQPa85tz36" alt=""><figcaption></figcaption></figure></div>

### How Monitoring Works

Monitoring tracks whether your agents are online and responsive, giving you a week-by-week view of uptime. Over time, this builds a history you can use to spot reliability issues, verify that deployments went smoothly, and hold your production agents to an availability standard.

The platform sends test requests to each monitored agent multiple times throughout the day. If the agent responds correctly, the check passes and the agent is marked as healthy. If it fails to respond or returns an error, the agent is marked as down, meaning it was not reachable or unable to answer during that check.

<table data-column-title-hidden data-view="cards"><thead><tr><th>Title</th><th>Description</th></tr></thead><tbody><tr><td><h4><i class="fa-heart-pulse">:heart-pulse:</i></h4><h4>Automated Health Checks</h4></td><td>The platform tests each agent multiple times a day, verifying it is reachable and able to respond</td></tr><tr><td><h4><i class="fa-chart-line">:chart-line:</i></h4><h4>Uptime History</h4></td><td>Daily health status and uptime trends across four time windows: 24 hours, 7 days, 30 days, and 90 days</td></tr><tr><td><h4><i class="fa-bell">:bell:</i></h4><h4>Email Alerts</h4></td><td>Configure per-agent notifications so the right team members are alerted the moment an agent goes down</td></tr></tbody></table>

{% hint style="success" %}
Helvia also publishes platform-wide availability at its [service status page](https://service-status.helvia.ai/), which tracks the health of the platform itself rather than individual agents.
{% endhint %}

### Enabling Monitoring for an Agent

Agents that support monitoring appear in the table with their toggle off by default. To start tracking an agent:

{% stepper %}
{% step %}

#### Locate the Agent

Find the agent you want to monitor in the table. Use the **Agents** filter or sort by **Agent Name** to narrow down the list.
{% endstep %}

{% step %}

#### Enable Monitoring

Toggle **Enable Agent Monitoring** on the far right of the agent's row.

<div data-with-frame="true"><figure><img src="/files/m1ejab2l9ZVgE2UzO8tE" alt="" width="181"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Add Notification Recipients

Select the dropdown arrow next to the toggle to open the Email notification panel. Search and select the console users who should receive email alerts when this agent's status changes. Confirm with **OK**.

<div data-with-frame="true"><figure><img src="/files/ESiwTRjEsXSiQEFZGVA6" alt="" width="294"><figcaption></figcaption></figure></div>

{% endstep %}
{% endstepper %}

Notifications are configured per agent, so different team members can be responsible for different agents.

### Checking Agent Uptime

Monitoring shares the same filtering controls found across Observatory, with one difference: instead of selecting a custom date range, the date picker works week by week. Select any day on the calendar and the table updates to show the full Sunday-to-Saturday week that contains it.&#x20;

{% columns %}
{% column %}

#### <i class="fa-calendar">:calendar:</i> Date Range

<div data-with-frame="true"><figure><img src="/files/UujZWXFsl3rwJfkLd5zR" alt=""><figcaption></figcaption></figure></div>

Select any day on the calendar to define the Sunday-to-Saturday week you want to monitor
{% endcolumn %}

{% column %}

#### <i class="fa-robot">:robot:</i> Agents

<div data-with-frame="true"><figure><img src="/files/nBKAaeoDhIXnJ9kXrU9A" alt=""><figcaption></figcaption></figure></div>

Filter by agent or narrow it down to a specific deployment

{% endcolumn %}
{% endcolumns %}

The uptime table contains uptime information about the status for each agent and for each day of the selected week. A green checkmark means the agent was healthy that day; a dash means no data was collected. The **Current Status** tells you whether the agent was responsive in the last check. Hover over any day cell to see the exact uptime percentage for that day.&#x20;

<div data-with-frame="true"><figure><img src="/files/dVgHzXICSME39jDqMoBO" alt=""><figcaption></figcaption></figure></div>

#### Overall Uptime

Select the expand icon on any agent row to reveal its overall uptime across four time windows: last 24 hours, 7 days, 30 days, and 90 days. If monitoring has not collected enough data yet, the charts show "No data."

Use these trends to catch gradual degradation before it becomes an outage. A steady 99% that drops to 92% over 30 days is worth investigating even if today's status looks healthy.

### Best Practices

* **Monitor production agents only:** Focus on agents serving real users to keep the table clean and alerts meaningful
* **Assign recipients per agent:** Route alerts to the people responsible for each agent so notifications reach the right inbox
* **Watch the 30-day trend:** A slow decline in uptime is easier to catch in the 30-day chart than in daily checkmarks

{% hint style="success" %}
You can now track agent availability, spot uptime trends over time, and configure email alerts to catch issues early.
{% endhint %}


---

# 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.helvia.ai/observatory/uptime-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.