Share This:

There are many ways that a collector can capture HTTP/HTTPS traffic for Analysis; you can span it, tap it, gre-tunnel / erspan it, use Akamai to post receipt data and you can also setup a switch -virtual or physical to be in promiscuous mode to allow the traffic capture.  What if the traffic is in a cloud and all of these other mentioned methods of gathering traffic are not available to you?  You guessed it - the Cloud Probe may be your answer.

 

Cloud Probe is an agent that you install on a web application server you are interested in monitoring.  It collects and sends the HTTP(s) data to an EUEM collector for processing.

 

I recently worked with a customer to capture traffic from servers that were being hosted in the Amazon cloud.  There were many rules and restrictions limiting monitor-ability in this cloud but with cloud probes installed on the servers, it allowed the capture of  traffic needed to show End User Experience.

 

You have the option to manually or 'silent' install the Cloud Probe.  The manual way offers a GUI and the silent install allows for scripting installs.

Once installed and the service is running, you will see it check in with the collector:

cp_on_collector.jpg

 

The APM Console can also show the cloud probe status and capture rate.  If you have many Cloud Probes deployed communicating with different collectors, you can see them all from the same UI:

cp.jpg

Current supported installs for the cloud probe are:

  • Operating system:
    • Red Hat Enterprise Linux 5.8 (64-bit)
    • Red Hat Enterprise Linux 6.1 (64-bit) (Basic Server or Minimal installations)
    • Red Hat Enterprise Linux 6.3 (64-bit)
    • Windows 2008 Server (R2)
    • Windows Server 2012
    • Windows Win 7 (64-bit)
    • Windows Win 8 (64-bit)

If you are running server not seen on the list, feel free to 'create an idea'!