aws probe not sending QoS data or performs slowly when submitting data

Document ID : KB000010871
Last Modified Date : 14/02/2018
Show Technical Document Details

The aws probe may appear to stop sending QoS data over time; sometimes restarting the probe or robot helps data collection resume but only for a short time. Other times, it may appear that data is taking an extraordinarily long time to be collected.

This problem occurs in high-scale environments, where hundreds (or more) of EC2 instances, Lambda functions, etc. are being monitored from a single probe instance.

The aws probe, depending on how it is configured, can transmit a very large amount of data per collection cycle, and this in turn can overwhelm the robot spooler.


For high-scale environments, CA recommends placing the aws probe on a hub, instead of a robot.  A dedicated hub would be ideal, but any hub which doesn't have a lot of other probes running on it would be fine.

Additional Information:

The hub's spooler is multi-threaded whereas the robot spooler is single-threaded; therefore, the hub is capable of handling larger volumes of QoS from high-scale probes.