Helyx Monitoring
Helyx provides real-time monitoring capabilities that help users observe, validate, and manage data replication pipelines effectively. The monitoring feature provides operational visibility into pipeline health, performance, and availability while replication is actively running.
By continuously collecting and displaying key runtime metrics, Helyx helps users identify replication delays, connector issues, resource constraints, and other operational conditions that may affect pipeline performance.
Monitoring Dashboard
The Helyx monitoring dashboard provides a centralized view of important pipeline and infrastructure metrics, including:
- Replication Lag — Monitor the delay between source and destination systems.
- Connector Status — Verify whether replication connectors are running and healthy.
- Active Sessions — View currently active database or replication sessions.
- CPU Utilization — Monitor CPU consumption of the Helyx environment.
- Memory Utilization — Track memory usage and identify potential resource constraints.
- Throughput — Monitor the volume and rate of data being processed.
- Pipeline Status — Review the current operational state of replication pipelines.
- Environment Metrics — View additional indicators relevant to the Helyx deployment.
These metrics provide visibility across both the data replication layer and the underlying infrastructure layer, helping users determine whether replication is operating within expected limits.
Metric Collection
Helyx uses an internal metric collection mechanism to capture runtime monitoring data at regular intervals of approximately five seconds.
This frequent collection cycle provides near real-time visibility into changes in:
- Replication performance
- Replication lag
- Connector availability
- System resource utilization
- Data processing activity
The monitoring data is continuously updated on the dashboard so that users can quickly identify changes in pipeline behavior.
Troubleshooting and Operational Visibility
Helyx Monitoring helps operational teams proactively identify and investigate potential issues before they become service-impacting incidents.
By providing a consolidated view of pipeline and system activity, the monitoring dashboard makes it easier to determine whether an issue is related to:
- Data ingestion
- Replication lag
- Connector health
- Database sessions
- CPU or memory utilization
- Data processing throughput
- Underlying system resources
This visibility enables users to analyze runtime behavior, identify the source of performance issues, and take corrective action quickly.
Proactive Monitoring
Helyx Monitoring helps operational teams proactively identify and investigate potential issues before they become service-impacting incidents.
Create the Configuration Directory
1. Create the configuration directory :
mkdir -p /var/lib/helyx/monitor2. Create a configuration file named helyx-monitor.conf inside the directory /var/lib/helyx/monitor.
vi /var/lib/helyx/monitor/helyx-monitor.conf3. Specify the BOOTSTRAP_IP value in the configuration file.
BOOTSTRAP_IP=your-vm-host-ipConfiguration
Create a service file inside /etc/systemd/system
vi /etc/systemd/system/helyx-monitor.serviceThe following section describes the configuration procedure for Helyx Monitor. After downloading and extracting the installation package, locate the helyx-monitor component in the extracted directory.
Create a system service file for Helyx Monitor using the sample configuration shown below:
[Unit]
Description=Helyx Monitoring Service
After=network-online.target
Wants=network-online.target
[Service]
Type=simple
WorkingDirectory=<Your Location where you unzipped the file>
EnvironmentFile=/var/lib/helyx/monitor/helyx-monitor.conf
ExecStart= path of helyx-monitor exe
Restart=always
RestartSec=5
[Install]
WantedBy=multi-user.targetStart helyx-monitor service
systemctl daemon-reloadsystemctl enable helyx-monitorsystemctl start helyx-monitorCheck the status of helyx-monitor Service
systemctl status helyx-monitorAccess UI for monitoring helyx data pipeline
Access the monitoring UI using the following URL and log in with the default username and password set to admin
http://<your VM IP>:3005