Overview

The Monitoring menu provides a real-time overview of OneDB system resource usage.

Administrators can use this menu to monitor the current condition of the OneDB host environment, including CPU usage, memory usage, disk usage, and network throughput. This helps administrators quickly identify resource pressure that may affect OneDB performance or availability.

Main Functions

Administrators can use the Monitoring menu to:

• View current CPU usage
• View current memory usage
• View disk usage and available storage
• View network throughput
• Review resource usage trends using charts
• Identify abnormal resource consumption
• Support troubleshooting and capacity planning

Monitoring Dashboard

The Monitoring page displays several resource indicators.

Indicator	Description
CPU	Shows current CPU usage percentage.
Memory	Shows current memory usage percentage.
Disk	Shows used and total disk capacity.
Network	Shows current network throughput.

Example display:

Resource	Example Value
CPU	0%
Memory	98%
Disk	440GB / 460GB
Network	142 MBPS

Resource Usage Charts

The Monitoring page also provides visual charts to help administrators understand resource usage trends.

Chart	Description
CPU Usage	Displays CPU usage trend over time.
Memory Usage	Displays memory usage trend over time.
Disk Usage	Displays disk utilization, including used and free space.
Network Throughput	Displays network traffic trend over time.

These charts help administrators observe whether resource usage is stable, increasing, or reaching a critical level.

CPU Usage

The CPU Usage section shows how much processor capacity is currently being used by the OneDB host.

High CPU usage may indicate heavy query processing, high request volume, intensive data protection operations, or other system-level processes running on the same host.

Administrators should review CPU usage when:

• OneDB response time becomes slower
• Application requests experience delays
• Tokenization or detokenization operations take longer than expected
• The server is handling high traffic

Memory Usage

The Memory Usage section shows how much system memory is currently being used.

High memory usage may affect OneDB stability and performance, especially when handling large result sets, high concurrent connections, or multiple database operations.

Administrators should review memory usage when:

• OneDB becomes slow or unstable
• Large database queries are being processed
• The system shows frequent memory pressure
• Services require restart more often than expected

Disk Usage

The Disk Usage section shows used and available disk capacity.

This is important because OneDB may require disk space for logs, configuration files, backup files, audit data, or other operational data.

Administrators should review disk usage regularly to prevent service disruption caused by insufficient storage.

Common causes of high disk usage include:

• Large log files
• Backup files stored locally
• Audit trail growth
• Temporary files
• System or application data accumulation

Network Throughput

The Network Throughput section shows current network traffic handled by the OneDB host.

Network throughput helps administrators understand communication activity between OneDB, client applications, and database servers.

Administrators should review network throughput when:

• Applications experience slow database responses
• OneDB is handling high traffic
• Database communication appears unstable
• There is a suspected network bottleneck

Recommended Practice

Administrators should monitor system resource usage regularly, especially in production environments.

Recommended controls:

Recommendation	Description
Monitor resource trends	Review CPU, memory, disk, and network trends regularly.
Set operational thresholds	Define internal thresholds for CPU, memory, disk, and network usage.
Investigate high usage	Review abnormal spikes or sustained high resource consumption.
Manage disk capacity	Clean up old logs, backups, or temporary files when needed.
Plan capacity early	Increase system resources before usage reaches critical levels.
Combine with audit and syslog	Use Audit Trail and Syslog for deeper investigation when abnormal activity occurs.

Important Notes

The Monitoring page provides visibility into resource usage within the OneDB appliance environment.

As OneDB is delivered as an OVA-based package, the displayed resource usage may represent the combined consumption of multiple appliance components, including the operating system, OneDB application services, internal database components, queue management services, logging processes, backup activities, and other supporting services.

Therefore, high resource usage should not be interpreted as being caused solely by the OneDB application layer. Administrators should perform further review of the overall appliance condition, including service activity, logs, internal database behavior, queue activity, storage consumption, and operating system-level indicators.

Monitoring information is provided to support operational visibility, troubleshooting, capacity planning, and early identification of resource pressure within the OneDB appliance. For production environments, administrators should define appropriate operational thresholds and periodically review resource trends to ensure that the appliance has sufficient capacity for the expected workload.