Monitoring node fetches Cloudwatch metrics data from AWS. This node is similar to Add-ons in a Resource node. It helps enrich the resources data with Cloudwatch metrics data. You can use these enriched Cloudwatch metrics data in successor nodes (like Filter node, Notification node, or Reports node) to selectively retain the resources required.
To add a Monitoring node, click on the ‘+’ and select ‘Monitoring’. Click on the node and select ‘edit’ to open the parameters options for the nodes.
‘Start Time’ and ‘Stop Time’ - the period for which you want to access the monitoring data
‘Namespace’ - select the CloudWatch Namespace from the dropdown list, for example AWS/EC2
‘Metric Name’ - select the CloudWatch metric you want to access. For example, CPUCreditUsage, or CPUUtilization.
‘Dimension 1’ - select how you want to bifurcate the resource for the metric. For example, while fetching CPUUtilization data, you can see it for every ‘Instancetype’ - this becomes your dimension
‘Time Period’ - The granularity within the selected time period that you want to see the data for. If you select 5s, you can see the data for every 5s, between the selected start & stop time.
‘Statistic’ - select the statistic you wish to access, like Average, Sum, SampleCount, Minimum, Maximum, etc.
Upon successful execution of this node, the Monitoring node collects all the corresponding metric data that can be further used for:
Filtering metric data to take further action on specific resources.
Generating a report (using Report node as the successor) to keep the team/peer(s) informed.
Generating a message (using Notification node as the successor) to update the team/peer(s) about critical metric data that needs immediate attention.