Monitoring Collector Status and Troubleshooting Connectivity

Introduction

Welcome to the Virtana Service Observability support guide on monitoring collector status and connectivity. This guide provides detailed instructions for IT Operations Teams, Infrastructure Engineers, Cloud Architects, and DevOps Professionals on how to verify collector status, troubleshoot connectivity issues, and ensure reliable data collection across your hybrid and multi-cloud environments.

Checking Collector Status

To verify the current status and authentication of your monitoring collectors, run the following command as root from the master host:

serviced host list

This command lists all active collectors along with their authentication status, helping you quickly identify any that are offline or unauthenticated.

Troubleshooting Connectivity Issues

If you experience connectivity problems with your collectors, follow these steps to diagnose and resolve them effectively:

1. Connectivity tests: Perform ping connectivity tests between the master and the affected collector hosts
2. Verify Configuration: Confirm that no unexpected reboots or configuration changes occurred on the collector without prior notification.
3. Consult Error Logs: Examine system journal and syslog logs for detailed messages related to connectivity failures.

Resolving Data Collection Issues

If data collection for Windows servers under a specific collector is failing, ensure the following:

1. Perfmon Service: Verify that the Windows Performance Monitor (Perfmon) service is enabled and running on the monitored device.
2. Review Data Logs: Check the relevant data logs for warnings or errors that could explain collection failures on the monitored device.

If data collection for SNMP servers under a specific collector is failing, ensure the following

1. SNMPD service: Make sure that the SNMPD service is running on the monitored device
2. Check configuration: Verify /etc/snmpd.conf is configured correctly to allow visibility into the OIDs you are polling, and that the configuration matches the corresponding device configuration properties (zSnmpCommunity, zSnmpVer) in Virtana Service Observability
3. Confirm you can SNMPwalk various OIDs on the target device from both the corresponding zenperfsnmp container and the target device.

Restarting ZenModeler Services

To resolve persistent issues with ZenModeler services on collector pools, follow these steps:

1. Identify impacted collector pools, for example, Collector-East or Collector-West.
2. Restart the zenmodeler services on these collector pools to restore normal operations.

Need Further Assistance?

If you require additional help, please open a new support ticket with Virtana Service Observability. Our team is committed to delivering innovative, reliable solutions and ensuring your success with our full-stack monitoring and observability platform.