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 EC2 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 Amazon EC2 interacts with Amazon Web Services through the Amazon CloudWatch APIs.
PATROL for Amazon EC2 collector details
The following table lists different PATROL for Amazon EC2 collectors and explains how they work:
Collectors (Collection interval) | Explanation |
|---|---|
CollECC | Gathers all of the parameters and variables for the Elastic Compute Cloud application class |
CollEC2 | Gathers all of the parameters and variables for the Elastic Compute Cloud application class |
CollInventory | Responsible for collecting resources for given AWS subscriptions under AWS account. |
CollELB | Gathers all of the parameters and variables for the Elastic Load Balancer application class |
CollEBS | Gathers all of the parameters and variables for the Elastic Block Storage application class |
Related topics