---
title: Managing installations
slug: how-tos/hkne-managing-installations
createdAt: 2025-09-26T11:06:30.122Z
---

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

The **Installations** page in the Historian Client Portal provides a structured overview of all Historian environments and their components.

Navigate to: [https://portal.factry.cloud/installations](https://portal.factry.cloud/installations)

It is the central place to monitor installations, organizations, and collectors.

## Installations Page Structure

The page follows a fixed hierarchy:

**Installation → Organization → Collector**

- All **installations** are listed at the top level.
- Clicking an installation reveals its **organizations**.
- Clicking an organization reveals its **collectors**.

This structure allows you to quickly move from a system-wide overview to a specific collector.

## Installations Overview

Each row (installation, organization, or collector) shows:

- Name
- Status
- Total alerts
- Heartbeat
- Version
- Type (Historian / Organization / Collector)
- Client

The **eye icon (**:inlineImage[]{src="https://api.archbee.com/api/optimize/SMPo4IS9FkillUAMsur2c/dloBwDnIbsCAN8MfF7xjL_image.png" alt caption width="512" height="512"}**)** opens the detailed view.

The **Heartbeat** indicates when the component last communicated with the portal and is often the first sign of connectivity issues.

## Detailed Views

Each level has its own detail page, accessible via the **eye icon (**:inlineImage[]{src="https://api.archbee.com/api/optimize/SMPo4IS9FkillUAMsur2c/dloBwDnIbsCAN8MfF7xjL_image.png" alt caption width="512" height="512"}**)**.

### Comparison by Level

| Section            | Installation                                                   | Organization                                       | Collector                                                         |
| ------------------ | -------------------------------------------------------------- | -------------------------------------------------- | ----------------------------------------------------------------- |
| **Status**         | Aggregated health of its collectors<br />Heartbeat (last seen) | Aggregated health of its collectors<br />Heartbeat | Status (e.g. Active)<br />Health (e.g. Collecting)<br />Heartbeat |
| **Scope**          | Entire Historian environment                                   | One organization within the installation           | Single collector                                                  |
| **Collectors**     | Total collectors in the installation                           | Collectors within that organization                | Not applicable                                                    |
| **Measurements**   | Total measurements in the installation                         | Measurements within that organization              | Measurements handled by that collector                            |
| **Product**        | Historian                                                      | Organization                                       | Collector                                                         |
| **Product Type**   | Not applicable                                                 | Not applicable                                     | Collector type (e.g. OPC-UA, MQTT, CSV, etc.)                     |
| **Version**        | Historian version<br />PostgreSQL version                      | Historian version                                  | Collector version                                                 |
| **System Info**    | Operating system                                               | Not applicable                                     | Operating system<br />Architecture                                |
| **Contact Person** | If configured                                                  | If configured                                      | If configured                                                     |
| **Location**       | If configured                                                  | If configured                                      | If configured                                                     |

## Overview Tab (Alerts & License info)

Within the detailed page, alerts and license information are grouped under the **Overview** tab.

### Alerts Section

Displays all alerts within the scope of the selected level:

- **Installation** → All alerts in that environment
- **Organization** → Alerts for that organization
- **Collector** → Alerts for that collector

From here you can review active alerts and navigate to configurations.

### Licenses Section

License information is available at:

- Installation level
- Organization level

Collectors do not contain license information.

The license section shows license state, issue date, expiry date, enabled features, and linked scope.

:::hint{type="info"}
A consolidated license overview is also available in the [Settings](docId\:GnRkmaECWHmPv7Vqg5jat) page.
:::

## Alert Configurations Tab

Each detailed page also contains an **Alert configurations** tab.

This tab shows:

- All alert configurations for that scope
- Silence rules (planned maintenance or temporary suppression)

From here, alerts can be managed, modified, or silenced.

:::hint{type="info"}
For detailed guidance on configuring alerts and notification channels, see:
[Managing alerts & notifications](docId\:XOCaCmXp7iiYvOYpTG32D)
:::

## Statistics Tab

Each detailed page contains a **Statistics** tab, but the information shown depends on the level.

### Installation

Shows statistics of the **server where the Historian is running**, including:

- CPU usage
- Memory usage
- Disk usage and free space
- I/O activity
- Uptime and system information

Use this when diagnosing infrastructure or performance issues affecting the entire Historian environment.

### Organization

Shows the status of the **InfluxDB instances** running within that organization.

### Collector

Shows statistics of the **server where the collector is running**, including system-level metrics similar to the installation view.

Use this when diagnosing collector-specific performance or infrastructure issues.

## Best Practice

- Regularly review the **Heartbeat** to detect communication failures early.
- Act on active alerts promptly.
- Use the **Statistics** tab when investigating performance or resource issues.
- Keep all components on supported versions.