In this Article

• Overview
• Accessing the Gateway Detail Page
• Gateway Detail Page
  • Overview
  • Alarms
  • Logs
  • Notifications
  • Properties
• Best Practices

Overview

Gateway Monitoring provides visibility into the operational status of a configured gateway and enables administrators to monitor alarms, review logs, and configure alert notifications. The Gateway Detail page provides insights into gateway health and allows users to investigate and resolve operational issues.

Before monitoring a gateway, ensure that the gateway has been installed and configured. For installation instructions, see Gateway Installation.

Accessing the Gateway Detail Page

To access gateway monitoring:

1. Navigate to Account Settings.

2. Select Gateway.

3. From the Stand-alone Gateway list, click the gateway name.

Clicking the gateway name opens the Gateway Detail Page, where monitoring and management options are available.

Gateway Detail Page

The Gateway Detail page provides operational monitoring and management capabilities for the selected gateway.

The page contains four tabs:

• Overview
• Alarms
• Logs
• Notifications

Each tab provides different information about the gateway’s operational health and activity.

Overview Tab

The Overview tab displays a summary of gateway health and system usage.

The following summary metrics are displayed:

Status
Shows whether the gateway is currently running or stopped.

CPU Usage
Displays the percentage of system CPU currently being used.

Memory Usage
Displays the percentage of system memory utilization .

Storage Usage
Displays the percentage of system disk usage for the host.

Data Connections

Data Connections section, which displays connection usage details per data source, including: Allowed connections, Active connections, Available connections, Usage percentage.

Alarms Tab

The Alarms tab displays alerts generated for gateway events or system conditions.

Each alarm record includes:

• Alarm ID
• Alarm Type
• Remarks
• Severity
• Status
• Detected timestamp

Users can filter, sort, and analyze alarms directly from the view.

Governance Views for Alarms

Users can create custom alarm views to organize and monitor alarms based on specific conditions.

To create a governance view:

1. Click All Alarms.

2. Select Create View.

3. Enter a View Name.

4. Define filter conditions.

5. Choose the columns to display.

6. Configure the default sorting order.

Note: Governance views allow teams to focus on specific alarm types, severities, or operational scenarios.
Learn more about Governance views here.

Alarm Trigger Conditions

Gateway alarms are generated when the system detects health or performance issues that may need attention.

These alarms help users identify problems such as:

• Gateway not responding

• High memory usage

• High CPU usage

• High disk usage

• Source issues

• AI workflow issues

Each alarm is assigned a severity level based on the type and seriousness of the issue.

The Severity levels include:

• Critical – A serious issue that may affect gateway availability or performance

• Warning – A condition that should be reviewed before it becomes more serious

In general, alarms are triggered when an issue continues for a period of time instead of appearing only briefly. This helps reduce unnecessary alerts caused by short-term spikes.

Alarms Thresholds

These thresholds are evaluated using historical sampling to ensure that alerts are triggered only when the condition persists rather than during short-term spikes.

Auto-Resolution Behavior

Some alarms are cleared automatically when the issue is no longer happening.

For example:

• Resource usage alarms are cleared once memory, CPU, or disk usage returns to a normal level.

• Gateway down alarms are cleared once the gateway starts responding again.

• Alarms such as source and AI payload errors still need manual resolution.

Reminder Notifications

Reminder notifications for unresolved alarms are configurable per severity level.

By default, reminders are sent every 2 hours for Warnings and every 30 minutes for Critical alarms until the alarm is acknowledged or resolved or ignored.

Updating Alarm Status

Users can update the status of alarms using the Update Status dropdown.

Available actions include:

• Acknowledge
• Resolve
• Ignore

Note: Only alarms in New/Acknowledge status can have their status updated.

Acknowledging an Alarm

Selecting Acknowledge indicates that the alarm has been reviewed and is under investigation.

Reminder alerts still continue until the alarm is resolved.

Once an alarm is acknowledged, it cannot be ignored and must eventually be resolved.

Ignoring an Alarm

Selecting Ignore dismisses the alarm from active monitoring. Once ignored, all reminder notifications for that alarm are suppressed. Ignored alarms are not subject to resolution and will not appear in active alarms. This action is intended for alarms that have been reviewed and determined to require no further action.

Resolving an Alarm

When resolving an alarm, users must select a Reason Code to support root-cause analysis.

Available reason codes include:

• Configurations Updated
• Gateway Restarted
• Other

If Other is selected, a comment becomes mandatory.

Providing clear resolution comments improves traceability and operational auditing.

Manual vs Automatic Resolution

Alarms may be resolved either automatically by the system or manually by a user.

Manual Resolution
Occurs when a user explicitly resolves an alarm from the interface.

Automatic Resolution
Occurs when the system detects that the issue condition has been cleared.

Certain alarm types, such as source connection issues and AI payload errors, cannot be automatically resolved.

For example, if a gateway is intentionally stopped for maintenance, users may choose to acknowledge or ignore alerts rather than resolving them immediately.

Alarm Detail Page

Clicking an Alarm ID opens the alarm detail page.

The alarm detail page displays a status timeline showing the lifecycle of the alarm.

The timeline includes:

Detected
When the alarm was initially detected by the system.

Acknowledged
When the alarm was acknowledged by a user.

Resolved
When the issue was resolved.

If the alarm was resolved automatically, the timeline shows Resolved by System.
If resolved manually, the timeline displays the user name of the person who resolved the alarm.

Users can also update the alarm status directly from this page.

Audit Trail for Alarms

An Activities icon is available in the alarm list view and in the alarm detail page.

Clicking this icon opens the Audit Trail side drawer, which records:

• Alarm status changes
• User actions
• System updates
• Resolution details

For more information about audit tracking, see Audit Trail Logs.

Logs Tab

The Logs tab displays gateway system logs used for operational monitoring and troubleshooting.

Users can:

• Search logs using keywords
• Filter logs by date range
• Review gateway execution activity

These logs help diagnose operational issues and verify gateway activity.

Notifications Tab

The Notifications tab allows administrators to configure alert notifications for gateway alarms.

Notifications can be sent to internal users or external recipients.

For instructions on configuring external recipients see How to Configure External Recipients & Whitelist Domains.

Alert Reminder Intervals

Alert reminders are configured based on severity levels.

By default:

Reminder notifications continue until the alarm is acknowledged or resolved.

Alert Notification Email

When an alarm remains active, recipients receive reminder notification emails containing alarm details and a direct link to view the alarm.

The email includes the following information:

• Alarm ID
• Alarm Type
• Alarm Remarks
• Gateway Name
• Severity Level
• Current Status
• Detection Timestamp

Recipients can click View Alarm to open the alarm detail page in the DvSum application and investigate the issue.

The system continues sending reminder notifications until the alarm is acknowledged or resolved.

Gateway Properties

The Properties tab provides a read-only view of the gateway configuration. It retrieves and displays the current configuration values from the gateway configuration file, allowing administrators to review gateway settings directly from the DvSum UI without accessing the gateway host.

Note: Gateway properties are read-only in the DvSum UI. To modify any property, update the gateway configuration file on the gateway host, then restart or reload the gateway if required for the changes to take effect.

To view gateway properties

1. Navigate to Account Settings > Gateway.
2. Select the required gateway.
3. Open the Properties tab.

The Properties page organizes gateway settings into the following sections:

General

Displays general gateway configuration settings, including:

• API Key – The API key configured for the gateway.
• Log Level – The logging level currently configured.
• Max Connections Allowed – Maximum number of concurrent connections supported by the gateway.
• Sequence Logging – Indicates whether sequence logging is enabled or disabled.

Data Retention

Displays the gateway's data retention configuration, including:

• Retention Policy – Whether data retention is enabled or disabled.
• Retention Period – Number of days gateway data is retained.
• Directories to Clean – Lists the directories that are cleaned during data retention operations.

HTTP Request

Displays the timeout settings used for HTTP requests processed by the gateway.

• GET Timeout
• POST Timeout

App Execution

Displays application execution settings configured for the gateway, including:

• Gateway Port
• Service Port
• Service Connection Limit
• Maximum Request Body Size
• Service Subprocess Timeout
• Service Threads

Thread Pools

The Thread Pools section displays the thread pool configuration used by different gateway services.

The table includes:

Thread pools are displayed for services such as:

• General
• Job Execution
• Scheduler
• Workflow Execution
• Schema Discovery

Note: The thread pools displayed may vary depending on the gateway configuration.

Important Notes

Read-only Configuration

The Properties tab provides a read-only view of the gateway configuration. Gateway properties cannot be modified from the DvSum UI. To change a property, update the gateway configuration file on the gateway host and restart or reload the gateway if required.

Gateway Availability

Gateway properties are available only when the gateway is online. If the gateway is unavailable, DvSum displays a warning banner, and property information cannot be retrieved until the gateway becomes available.

Supported Gateway Version

The Properties tab is available only for supported gateway versions of 3.4.4 or later. If the connected gateway is running an earlier version that does not support this feature, DvSum displays a message indicating that the gateway must be upgraded before the Properties tab becomes available.

Best Practices

• Regularly review gateway alarms to identify operational issues early. 

• Use the Properties tab to verify gateway configuration when troubleshooting or validating gateway settings. 

• Acknowledge alarms once investigation begins. 

• Use governance views to monitor critical alerts more efficiently. 

• Review gateway logs during troubleshooting. 

• Ensure notification recipients are configured to receive alerts promptly.