Verifying the Cloud Probe installation and service

After you have installed Real User Cloud Probe, perform the following tasks to check system health:

To check the Cloud Probe service on Windows

Open the Services list and verify that BMC Real User Cloud Probe service is started.

To check the Cloud Probe service on Linux

Run the following command to ensure that the Cloud Probe process is up and running:

ps –ef | grep cloud

If you have installed a Cloud Probe on a Red Hat Linux 5.8 operating system, and the agent does not start after installation, change the maximum packet size (in bytes) allowed for the EPX:

Open the epx_properties.conf file located in [CloudProbeInstallDir]/cloudprobe/conf folder.
Change the value of the SYSTEM.PROPERTIES.EPX.global.max_packet_size parameter. You can set the maximum packet size value between 1500 and 65535 bytes.
Start the Cloud Probe service using the service cloud-probe start command.

To verify the Cloud Probe is sending traffic data to the Real User Collector

In the Real User Collector or Real User Monitor to which you connected the Cloud Probe, select Administration > Integration, then click Cloud Probes. Find your Cloud Probe instance in the list and ensure it is processing traffic data. For details, see Monitoring-Cloud-Probe-system-health-and-statistics-on-the-Console.
In the BMC Application Management Console, select System Deployment > Components, and click on the Real User Collector to which you connected the Cloud Probe. Find your Cloud Probe instance in the list and ensure it is processing traffic data. For details, see Monitoring-Cloud-Probe-system-health-on-a-Collector.

Tip

If your Cloud Probe instance was not installed properly or it is not processing data, see Troubleshooting-the-Cloud-Probe.

Where to go from here

To filter unnecessary traffic, set traffic inclusion and exclusion policies.

Configure confidentiality policies on the Cloud Probe.

Configure the Cloud Probe SSL keys and settings for traffic decryption.