Page tree

Skip to end of metadata
Go to start of metadata

The Cloud Probe captures web traffic passing through the network and sends information to the Real User Collector so the BMC Real End User Experience Monitoring Software Edition can monitor applications that are deployed on premises, or in a public cloud environment, such as Amazon EC2, a private data center, or a hybrid deployment.

The Cloud Probe's deployment in your system depends on several factors. The placement is determined by where the traffic is visible to the Cloud Probe, and how the Cloud Probe connects to the Real User Collector. By design, a Cloud Probe sends data to only one Collector, but a Collector can receive data from several Cloud Probes. You must plan the placement of the Cloud Probes and the recipient Collectors so that you know which Collector instance connects to each Cloud Probe.

You can also install a Cloud Probe directly onto a Linux or Windows operating system to provide passive real end-user monitoring capabilities in environments where network taps or spanning ports are not accessible.

The following examples describe the typical deployment methods in which a Cloud Probe, or several Cloud Probes, can be connected to a Real User Collector.

Cloud Probe on a dedicated system

The Cloud Probe is installed on a dedicated Windows or Linux computer. The Cloud Probe captures the web traffic through a network tap or an appliance that supports a Generic Routing Encapsulation (GRE) tunnel.

Cloud Probe deployment with a network tap

You can install the Cloud Probe on a dedicated Windows or Linux computer. As shown in the following illustration, this deployment uses a network tap to capture the traffic.

With a network tap, the Promiscuous Mode must be enabled so that the Cloud Probe can capture all of the traffic that passes through the network. If the Promiscuous Mode is disabled, the Cloud Probe only captures the traffic going in or out of the system on which it is hosted.

For additional information about using a Cloud Probe with a tapping point, see Traffic capture and tapping points for BMC Real End User Experience Monitoring Software Edition.

Network tap deployment option for the Cloud Probe

Note

Promiscuous mode traffic capture is not possible with a Hyper-V host because the Virtual Switch (vSwitch) will not forward packets to a virtual machine unless it has the machine's MAC address as a destination.

To deploy a Real User Collector on Hyper-V host, you must use a Generic Routing Encapsulation (GRE) tunnel to encapsulate and carry the traffic.

Cloud Probe deployment with a GRE tunnel

The Cloud Probe captures mirrored traffic through a Generic Routing Encapsulation (GRE) tunnel. The GRE tunneling protocol encapsulates a wide variety of network layer protocols inside a virtual point-to-point link over an  Internet Protocol network.

This deployment is useful when the Cloud Probe cannot be connected directly to a tap or a mirror port of a network appliance. If your network appliance supports functioning as a GRE source, the Cloud Probe can run on a remote dedicated system and deliver mirrored traffic encapsulated over IP protocol.

GRE tunnel deployment option for the Cloud Probe

Cloud Probe on a load balancer

It is possible to use a load balancer as a tap point by installing the Cloud Probe on the system that provides the load-balancing operations for the application. It is not necessary to enable the Promiscuous Mode/Accept with this deployment.

To install the Cloud Probe on a load-balancing system:

  • You must have access to install the Cloud Probe on the load balancer.
  • The load balancer must use an operating system supported by the Cloud Probe.

Load balancer deployment option for the Cloud Probe

Cloud Probe on a web server

You can install the Cloud Probe on your web servers. This approach requires resources from the web server. If you adopt this deployment option:

  • You must install the Real User Cloud Probe on each web server
  • You do not need to enable the Promiscuous Mode/Accept with this deployment

Web server deployment option for the Cloud Probe

For information on preparing the network interface card (NIC) for traffic capture, see Setting up the monitored NIC for the Cloud Probe.

Related topics

Setting up the monitored NIC for the Cloud Probe

Traffic capture and tapping points for BMC Real End User Experience Monitoring Software Edition

System requirements for Cloud Probe

Installing the Cloud Probe

17 Comments

  1.  

    1.  

      1.  

  2.  

    1.  

  3.  

    1.  

  4. Dears, 

     

    If i have to NIC Card in Linus Machine . Can i monitor these two cards to get the traffic or only one. can i deploy cloud Probe Twice 

  5. Hi,

    I will consult with a developer about this issue and post a response.

    Thanks,

    Michael

    1. Dear Michael, 

       

      Any update about the above request 

      1. Hi Mohamed,

         

        The answers are no and no. The current versions of Cloud Probe (up to 10.7) do not support multiple NICs. One Cloud Probe instance can only monitor one and only one NIC. And while installing several Cloud Probes on a single server can technically be done, this kind of setup is not tested and approved by R&D and QA, so it is not supported.

         

        If you have a Linux server, and if you can bond your physical NICs into one single bond interface, then you could monitor that bonded interface with a single Cloud Probe.

         

        Another avenue, untested and not supported, would be to use netfilter (iptables) rules to copy the ingress and egress traffic of those two physical NICs to a third Virtual NIC, set in promiscuous mode, monitored by a Cloud Probe. I would not recommend that avenue at all since this can put a serious load on the kernel depending on the amount of traffic.

         

        Eventually in the future will Cloud Probe be able to support multiple NICs at once. I kindly invite you to open an idea on the BMC Communities, this is a fantastic improvment for CP indeed!

         

        Thank you.

         

        Best regards,

         

        Alexandre Boyer

        Sr. Technical Support Analyst

        BMC Software.

         

        1.  

          Hi Alexander,

          Thank you for your reply and the information that you shared with me.

          I have searched for the bond solution. but i need to know which type of bond mode i need to use.

          in order to get the traffic from both NIC cards in the same time.

          Best Regards 

          Mohamed Eraky

            

  6. Is it necessary to have cloud probe in environment? I mean cant we connect collector directly to network tap?

    If cloud probe is must then can you please suggest necessary hardware configuration?


    Regards

    Ajit C

    1. Hi Ajit,

      Yes Cloud Probe is mandatory. It is the EUEM component that is capturing the traffic. The collector is not capturing traffic anymore (comipared to previous version 2.x).

      For Cloud Probe requirements, please refer to this docs page:

      System requirements for Cloud Probe

      Do not hesitate to open a support case if you have any additional question.

      Thank you.


      Best regards,


      Alexandre Boyer

      Sr. Technical Support Analyst

      BMC Software.


  7. Thanks Alex,

    can we install cloud probe on same server as collector?

    Regards

    Ajit C

    1. Hi Ajit,

      Yes we can, as long as you are making sure you configure a distinct NIC for the capture than the management one used to access the UI.

      Best regards,


      Alexandre Boyer

      Sr. Technical Support Analyst

      BMC Software.


  8. Hi Alex,

    Thanks

    Does spanning is supported on cloud probe/collector running as ESXi virtual machine?

    or do we have to go with GRE in that case also?


    Regards

    Ajit C