---
title: Managing alerts & notifications
slug: how-tos/XOCa-managing-alerts
docTags: vg8QkSZx_1TOzYPB3tXmx,n5hUNKFejaPplyvTaPYRJ
createdAt: 2025-09-09T15:10:52.101Z
---

::embed[]{url="https://www.youtube.com/watch?v=DrtzhSmtn8I"}

The **Factry Portal** provides automatic alerting to monitor the health, performance, and licensing status of your Historian installations and collectors.

Alerts help detect connectivity issues, system overload, storage problems, and license risks before they cause downtime.

## Managing Alerts

Alerts are managed per installation via:[https://portal.factry.cloud/installations](https://portal.factry.cloud/installations)

### Viewing Alerts

1. Go to **Factry Portal**.
2. Navigate to **Installations**.
3. Click the **eye icon** next to your Historian server.
4. Open **Alert configurations**.

![](https://api.archbee.com/api/optimize/SMPo4IS9FkillUAMsur2c/5NQPynDJwhYiHczzaQYnk-20250926-111500.png)

You can filter alerts by installation, severity, or status.

### Creating Custom Alerts

**Installations** → **Eye icon **→ **Alert configurations** → **+ Add alert**

![](https://api.archbee.com/api/optimize/SMPo4IS9FkillUAMsur2c/hWFc4XR0lUCJ5id3Aqg81-20250926-112723.png)

Complete the following fields:

- **Name** – Clear and descriptive name
- **Activation delay** – Duration the condition must remain active before triggering
- **Template** – Select a message template
- **Frequency** – Interval for repeated notifications if still active
- **Escalate to Factry after** – Duration after which Factry is notified if the alert remains High

Custom alerts can be edited, disabled, deleted, or silenced.

### Editing Alerts

For each alert in the configuration list, you can:

- Edit the alert
- Configure notification channels (e.g. Email, Webhook)
- Enable or disable the alert
- Delete the alert
- Silence the alert

![](https://api.archbee.com/api/optimize/SMPo4IS9FkillUAMsur2c/Qm0zHBKZZ_FOQn2axv8of-20250926-112531.png)

## Acknowledging Alerts

When an alert fires:

- Use the **Ack** button to mute notifications until the issue is resolved.
- Alerts that are **not acknowledged** will trigger reminder notifications based on the configured frequency.

Acknowledging suppresses notifications but does not resolve the underlying issue.

## Silences (Planned Maintenance)

Silences temporarily suppress notifications (maximum 7 days).

### Silence all alerts for an installation

**Installations** → **Eye icon** → **Alert configurations** → **+Add silence rule**

### Silence a single alert

**Installations** → **Eye icon** → **Alert configurations** → **Silence alert (**:inlineImage[]{src="https://api.archbee.com/api/optimize/SMPo4IS9FkillUAMsur2c/pjwrNcE3V8kde7XNQpDVW_image.png" alt caption size="10" width="512" height="512"}**)**

Silencing does not disable the alert, it only suppresses notifications during the selected period.

## Auto-Created Alerts

The Factry Portal automatically creates alerts for all new instances.

They are created when:

- A Historian first connects to the Portal
- A new collector is onboarded

Auto-created alerts:

- Cannot be modified
- Cannot be deleted
- Can be linked to notification channels

### Auto-Created Alerts for Historians

- No monitoring data received for > 5 minutes
- Issue writing data to the time-series database
- CPU or memory usage > 80%
- Disk usage > 85%
- Free disk space \< 5000 MB
- License expiry in less than 30 days

### Auto-Created Alerts for Collectors

- No heartbeat for > 5 minutes
- Bad health
- No data collection (while health = Collecting)
- More points with bad quality than with Good quality
- CPU or memory usage > 80%
- Disk usage > 85%
- Free disk space \< 5000 MB

## Managing Notification Channels

:::hint{type="info"}
To add or modify notification channels, go to **Settings → Notification channels**
or visit: [https://portal.factry.cloud/notification-channels](https://portal.factry.cloud/notification-channels)

For full details on configuring and linking notification channels, see the [Settings](docId\:GnRkmaECWHmPv7Vqg5jat) page.
:::

## Best Practice

- Link alerts to at least one notification channel
- Use silences during planned maintenance
- Review auto-created alerts when onboarding new instances