---
title: "Platform | Visualizing Historical Alarms | N3uron KB V1.22"
slug: "platform-visualizing-historical-alarms"
description: "N3uron is an Industrial Edge Platform for DataOps that enables seamless integration between the industrial plant floor and business applications,"
updated: 2025-12-22T11:16:41Z
published: 2025-12-22T11:16:41Z
canonical: "docs.n3uron.com/platform-visualizing-historical-alarms"
---

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

# Visualizing Historical Alarms

Historical Alarms can be monitored from [WebUI](/v122/docs/platform-web-user-interface)and [Web Vision](/v122/docs/web-vision-introduction). WebUI provides a historical alarm table, which displays the alarm system history. To access the interface, go to **Alarms—>Historical** in the **Navigation**panel.

Before the historical alarm table can retrieve alarm data, a local [Historian](/v122/docs/historian)instance must first be configured. Once the Historian instance has been created, go to the **Navigation panel** and select **Config**under the **System**menu. Next, head to the **Explorer**panel and click on **This node**, as shown in the image below.

In order to store alarm data in a MongoDB database, users will need to enable**Alarm & Events History** and then enter the name of the Historian instance used for storing data in the **Local Historian name** field. Remember to hit the **Save** button.

![Figure 8- Historical Alarm & Events Configuration](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%208-%20Historical%20Alarm%20&%20Events%20Configuration.png)

## **Tag Groups**

On the left-hand side of the window, we can find the **Tag Groups** browser, which is set up in an interactive tree structure that can be expanded or collapsed to view more tags. By selecting the different levels in the tree, we can filter which historical information will be displayed in the **Alarms** panel.

## **Alarms**

The **Alarms** panel is located on the right-hand side and is the panel where the selected historical Alarm Events are displayed. Below the header, we can find the **Sublevels** checkbox, which, if checked, will display all the alarms below the selected level in the **Tag Groups** tree. Users can also filter the alarms displayed in the panel by entering a [](https://regexr.com/)[](https://regexr.com/)[Regular Expression](https://regexr.com/)[](https://regexr.com/) in the corresponding text field. Most features of regular expressions are supported.

The historical alarm table can be configured to show active, unacknowledged, cleared, and acknowledged alarms. By default, all non-cleared/non-acknowledged alarms will be shown. It's also possible to filter alarms depending on their priority level, as shown in the image below.

Users can adjust the date range by modifying the**Start**and **End** date and time fields provided for this alarm. All Alarm Events with timestamps that match the selected range will appear in the table.

Users can also enable auto-reload for this table using the corresponding check box and the numeric field that specifies how often the historical data reload will occur.

![Figure 9- Visualization Historical Alarms](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%209-%20Visualization%20Historical%20Alarms.png)

The columns shown in the **Alarms** panel****are as follows:

- **Timestamp:** The timestamp corresponding to the alarm event.
- **Path:** Full path of the tag linked to the alarm.
- **Value:** The tag value.
- **Description:** Provides a description of the alarm.
- **Priority:** Priority level for the alarm.
- **Status:**Combination of the alarm's Active and Acknowledged conditions.
- **Acked by:** User that acknowledged the alarm.
- **Ack comment:** Message entered when the alarm was acknowledged, if any.

Finally, **N3uron**allows users to export everything that is being displayed in the **Alarms**panel to a CSV file by clicking on the button located in the upper-right corner of the panel. Next to this button, there is also an alarm counter, which shows the total number of displayed Alarm Events.

![Figure 10- Exporting Historical Alarms](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2010-%20Exporting%20Historical%20Alarms.png)

## **Historical Alarms via Links**

It is possible to read historical alarms from other nodes through the links. To do this, go to **Node**, select the Link and the historical alarms corresponding to the selected node will automatically appear.

![1(1)](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/1(1).png)

![2(2)](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/2(2).png)

![3(1)](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/3(1).png)

[Embedded content](https://www.youtube.com/embed/qmx2cZos80s?&t=13s&wmode=opaque&rel=0)