Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Architecture
The collector that is used to gather the cloud data from Amazon Web Services is a Java process. The PATROL Agent launches the external process and continues to communicate with this process through a PATROL Scripting Language (PSL) channel.
Amazon Web Services supports monitoring of the cloud environment by using Amazon CloudWatch APIs. The handler provided by PATROL for Amazon Web Services (PATROL for AWS) uses Amazon CloudWatch APIs to gather data for the Knowledge Module (KM).
The following major steps are involved:
The PATROL Agent initiates the request to collect the data. The collection request initiated by the PATROL Agent is in a pre-defined format. The KM starts one or multiple external processes for data collection.
The external process collects the necessary cloud data. The handler provided by Amazon Web Services collects the cloud data.
The external process sends the data back to the PATROL Agent in an appropriate format.
The PATROL Agent reads the data and takes the necessary action on the data. The necessary action taken by the KM and the PATROL Agent can involve creating a required instance or setting the appropriate parameters.
The following figure shows how PATROL for AWS interacts with Amazon Web Services through the Amazon CloudWatch APIs.
PATROL for Amazon Web Services collector details
The following table lists different PATROL for Amazon Web Services collectors and explains how they work:
Collector
Collection interval (minutes)
Application class for which it collects performance data