Server Monitor

The Server Monitor module provides administrators with real-time insights into server availability, performance metrics, memory consumption, and bundle activity. This tool is essential for maintaining platform stability, ensuring scalability, and proactively managing infrastructure health for analytics workloads and workflows.

Access the Server Monitor

1. From the Admin module, click Server Monitoring.

2. The Server Monitor page opens, displaying nodes that represent various modules of the BDB Platform.

   • By default, the Gateway tab is selected.

Tip: Select a node to view node-specific server details. For example, selecting the Pipeline & Data Prep node shows JVM heap memory, OS memory usage, and bundle status.

Node-Level Metrics

Each node provides detailed server performance metrics, including Heap Memory, OS Memory, and Bundle Status.

Heap Memory (Java Virtual Machine)

• Current Heap Size: 286 MB — memory currently used by the JVM.

• Committed Heap Size: 2016 MB — memory reserved for the JVM and guaranteed to be available.

• Max Heap Size: 2016 MB — maximum limit of JVM heap growth, useful for tuning large-scale data processing.

• Usage Gauge: A color-coded dial showing current heap usage.

  • Green = low usage

  • Red = high usage

  • Example: 286 MB usage indicates efficient memory utilization.

OS Memory (Physical Server RAM Usage)

• Committed Virtual Memory: 0 GB — no memory committed to virtual memory, minimizing disk swapping.

• Free Physical Memory: 4 GB — available RAM for launching new jobs or services.

• Total Physical Memory: 6 GB — total RAM on the server instance.

• Memory Usage Bar: Visual representation of usage percentage.

  • Example: 33% usage indicates optimal performance for real-time tasks.

Bundle Status Panel (OSGi Services Monitor)

This panel tracks modular service components (bundles) active within the analytics platform. Each bundle corresponds to a functionality or integration (e.g., messaging, routing, data transformation).

Key Columns

Column	Description
Bundle Name	Name of the deployed module (e.g., camel-api, Apache MINA Core). Many are based on Apache Camel and Apache Karaf, common in enterprise integration.
Start ID	Internal identifier representing the launch sequence or service registration.
Status	Service state. Active bundles are marked with green indicators, confirming operational health.

Key Benefits

• Monitor JVM heap and physical memory for proactive resource management.

• Track service uptime and ensure all bundles are active.

• Maintain stability and scalability across distributed platform modules.