Verifying the Real User Cloud Probe installation

After you have installed Real User Cloud Probe, check the following indicators of system health:

• Cloud Probe service is up and running
  
  • In the Cloud Probe Windows machine, open the list of services verify that cloud Probe service is up and running under services,

  • In Linux, run the following command to ensure that the Cloud Probe process is up and running:

    ps –ef | grep cloud
• Cloud Probe is sending traffic data to the Real User Collector:
  • In the Real User Collector instance, to which you connected Cloud Probe, select Administration > Integration, then click Cloud Probes. Find your Cloud Probe instance in the list and ensure it processes traffic data.
  • In the BMC Application Performance Management Console instance, select System Deployment > Components, and click on the Real User Collector instance, to which you connected Cloud Probe. Find your Cloud Probe instance in the list and ensure it processes traffic data.
    
    

If you have installed Cloud Probe on 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:

1. Open the epx_properties.conf file located in [CloudProbeInstallDir]/cloudprobe/conf folder.
2. 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.
   
   
3. Start the Cloud Probe service using the service cloud-probe start command.

Where to go from here

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

Configure confidentiality policies on the Cloud Probe.

Related topic

Managing-SSL-keys-and-settings-for-Cloud-Probe-traffic-decryption
Modifying the Real User Cloud Probe configuration
Starting-and-stopping-the-Real-User-Cloud-Probe