Cloudwatch Publish ComponentNote: This feature is only available for instances hosted on AWS.
Publish metrics to Cloudwatch. Within the AWS console, you may then attach alarms to get alerts when metrics values fall out of a normal range.
|Name||Text||A human-readable name for the component.|
|Region||Select||The AWS region that the metrics are to be published to. The default value is the region that Matillion ETL is running in.|
|Namespace||Text||All Cloudwatch metrics belong to a Namespace. Namespaces starting with AWS are reserved, so you should avoid using AWS as the prefix for the Namespace. The value entered here will become a category under the "Custom Metrics" section of the Cloudwatch console.|
|Metrics||Metric Name||The name of the metric in the given Namespace. Metrics are created on-demand, so there is no requirement to create the metric in advance. They generally show in Cloudwatch within a few minutes.|
|Numeric Variable||The name of an existing Variable, whose type is Numeric. Cloudwatch metrics are numeric, which allows for indicators (using only 0 and 1), proportions/percentages (using real values between 0.0 to 1.0) or domain-specific values such as rowcounts or runtimes. Note:This numeric variable MUST have a default value or an error will be returned. See Using Variables for help with setting default values.|
This orchestration job will publish the runtime and row count of a Database Query to Cloudwatch.
The information is exported from the RDS component into two variables. These variables must be created in advance, and must be numeric since all Cloudwatch metrics are numbers. Their scopes are also 'Copied', so can be used by multiple components concurrently, without overwriting each others values:
These variable values are then published to Cloudwatch