AWS IoT Greengrass Version 1 entered the extended life phase on June 30, 2023. For more information, see the AWS IoT Greengrass V1 maintenance policy. After this date, AWS IoT Greengrass V1 won't release updates that provide features, enhancements, bug fixes, or security patches. Devices that run on AWS IoT Greengrass V1 won't be disrupted and will continue to operate and to connect to the cloud. We strongly recommend that you migrate to AWS IoT Greengrass Version 2, which adds significant new features and support for additional platforms.
CloudWatch Metrics connector
The CloudWatch Metrics connector publishes custom metrics from Greengrass devices to Amazon CloudWatch. The connector provides a centralized infrastructure for publishing CloudWatch metrics, which you can use to monitor and analyze the Greengrass core environment, and act on local events. For more information, see Using Amazon CloudWatch metrics in the Amazon CloudWatch User Guide.
This connector receives metric data as MQTT messages. The connector batches metrics that are in the same namespace and publishes them to CloudWatch at regular intervals.
This connector has the following versions.
Version |
ARN |
---|---|
5 |
|
4 |
|
3 |
|
2 |
|
1 |
|
For information about version changes, see the Changelog.
Requirements
This connector has the following requirements:
Connector Parameters
This connector provides the following parameters:
Create Connector Example (AWS CLI)
The following CLI command creates a ConnectorDefinition
with an
initial version that contains the CloudWatch Metrics connector.
aws greengrass create-connector-definition --name MyGreengrassConnectors --initial-version '{ "Connectors": [ { "Id": "MyCloudWatchMetricsConnector", "ConnectorArn": "arn:aws:greengrass:
region
::/connectors/CloudWatchMetrics/versions/4", "Parameters": { "PublishInterval" : "600", "PublishRegion" : "us-west-2", "MemorySize" : "16", "MaxMetricsToRetain" : "2500", "IsolationMode" : "GreengrassContainer" } } ] }'
In the AWS IoT Greengrass console, you can add a connector from the group's Connectors page. For more information, see Getting started with Greengrass connectors (console).
Input data
This connector accepts metrics on an MQTT topic and publishes the metrics to CloudWatch. Input messages must be in JSON format.
- Topic filter in subscription
-
cloudwatch/metric/put
- Message properties
-
request
-
Information about the metric in this message.
The request object contains the metric data to publish to CloudWatch. The metric values must meet the specifications of the
PutMetricData
API. Only thenamespace
,metricData.metricName
, andmetricData.value
properties are required.Required:
true
Type:
object
that includes the following properties:namespace
-
The user-defined namespace for the metric data in this request. CloudWatch uses namespaces as containers for metric data points.
Note
You can't specify a namespace that begins with the reserved string
AWS/
.Required:
true
Type:
string
Valid pattern:
[^:].*
metricData
-
The data for the metric.
Required:
true
Type:
object
that includes the following properties:metricName
-
The name of the metric.
Required:
true
Type:
string
dimensions
-
The dimensions that are associated with the metric. Dimensions provide more information about the metric and its data. A metric can define up to 10 dimensions.
This connector automatically includes a dimension named
coreName
, where the value is the name of the core.Required:
false
Type:
array
of dimension objects that include the following properties:name
-
The dimension name.
Required:
false
Type:
string
value
-
The dimension value.
Required:
false
Type:
string
timestamp
-
The time that the metric data was received, expressed as the number of seconds since
Jan 1, 1970 00:00:00 UTC
. If this value is omitted, the connector uses the time that it received the message.Required:
false
Type:
timestamp
Note
If you use between versions 1 and 4 of this connector, we recommend that you retrieve the timestamp separately for each metric when you send multiple metrics from a single source. Don't use a variable to store the timestamp.
value
-
The value for the metric.
Note
CloudWatch rejects values that are too small or too large. Values must be in the range of
8.515920e-109
to1.174271e+108
(Base 10) or2e-360
to2e360
(Base 2). Special values (for example,NaN
,+Infinity
,-Infinity
) are not supported.Required:
true
Type:
double
unit
-
The unit of the metric.
Required:
false
Type:
string
Valid values:
Seconds, Microseconds, Milliseconds, Bytes, Kilobytes, Megabytes, Gigabytes, Terabytes, Bits, Kilobits, Megabits, Gigabits, Terabits, Percent, Count, Bytes/Second, Kilobytes/Second, Megabytes/Second, Gigabytes/Second, Terabytes/Second, Bits/Second, Kilobits/Second, Megabits/Second, Gigabits/Second, Terabits/Second, Count/Second, None
- Limits
-
All limits that are imposed by the CloudWatch
PutMetricData
API apply to metrics when using this connector. The following limits are especially important:-
40 KB limit on API payload
-
20 metrics per API request
-
150 transactions per second (TPS) for the
PutMetricData
API
For more information, see CloudWatch limits in the Amazon CloudWatch User Guide.
-
- Example input
-
{ "request": { "namespace": "Greengrass", "metricData": { "metricName": "latency", "dimensions": [ { "name": "hostname", "value": "test_hostname" } ], "timestamp": 1539027324, "value": 123.0, "unit": "Seconds" } } }
Output data
This connector publishes status information as output data on an MQTT topic.
- Topic filter in subscription
-
cloudwatch/metric/put/status
- Example output: Success
-
The response includes the namespace of the metric data and the
RequestId
field from the CloudWatch response.{ "response": { "cloudwatch_rid":"70573243-d723-11e8-b095-75ff2EXAMPLE", "namespace": "Greengrass", "status":"success" } }
- Example output: Failure
-
{ "response" : { "namespace": "Greengrass", "error": "InvalidInputException", "error_message":"cw metric is invalid", "status":"fail" } }
Note
If the connector detects a retryable error (for example, connection errors), it retries the publish in the next batch.
Usage Example
Use the following high-level steps to set up an example Python 3.7 Lambda function that you can use to try out the connector.
Note
-
If you use other Python runtimes, you can create a symlink from Python3.x to Python 3.7.
-
The Get started with connectors (console) and Get started with connectors (CLI) topics contain detailed steps that show you how to configure and deploy an example Twilio Notifications connector.
-
Make sure you meet the requirements for the connector.
For the group role requirement, you must configure the role to grant the required permissions and make sure the role has been added to the group. For more information, see Managing the Greengrass group role (console) or Managing the Greengrass group role (CLI).
-
Create and publish a Lambda function that sends input data to the connector.
Save the example code as a PY file. Download and unzip the AWS IoT Greengrass Core SDK for Python. Then, create a zip package that contains the PY file and the
greengrasssdk
folder at the root level. This zip package is the deployment package that you upload to AWS Lambda.After you create the Python 3.7 Lambda function, publish a function version and create an alias.
-
Configure your Greengrass group.
-
Add the Lambda function by its alias (recommended). Configure the Lambda lifecycle as long-lived (or
"Pinned": true
in the CLI). -
Add the connector and configure its parameters.
-
Add subscriptions that allow the connector to receive input data and send output data on supported topic filters.
-
Set the Lambda function as the source, the connector as the target, and use a supported input topic filter.
-
Set the connector as the source, AWS IoT Core as the target, and use a supported output topic filter. You use this subscription to view status messages in the AWS IoT console.
-
-
-
Deploy the group.
-
In the AWS IoT console, on the Test page, subscribe to the output data topic to view status messages from the connector. The example Lambda function is long-lived and starts sending messages immediately after the group is deployed.
When you're finished testing, you can set the Lambda lifecycle to on-demand (or
"Pinned": false
in the CLI) and deploy the group. This stops the function from sending messages.
Example
The following example Lambda function sends an input message to the connector.
import greengrasssdk import time import json iot_client = greengrasssdk.client('iot-data') send_topic = 'cloudwatch/metric/put' def create_request_with_all_fields(): return { "request": { "namespace": "Greengrass_CW_Connector", "metricData": { "metricName": "Count1", "dimensions": [ { "name": "test", "value": "test" } ], "value": 1, "unit": "Seconds", "timestamp": time.time() } } } def publish_basic_message(): messageToPublish = create_request_with_all_fields() print("Message To Publish: ", messageToPublish) iot_client.publish(topic=send_topic, payload=json.dumps(messageToPublish)) publish_basic_message() def lambda_handler(event, context): return
Licenses
The CloudWatch Metrics connector includes the following third-party software/licensing:
-
AWS SDK for Python (Boto3)
/Apache License 2.0 -
botocore
/Apache License 2.0 -
dateutil
/PSF License -
docutils
/BSD License, GNU General Public License (GPL), Python Software Foundation License, Public Domain -
jmespath
/MIT License -
s3transfer
/Apache License 2.0 -
urllib3
/MIT License
This connector is released under the
Greengrass Core Software License Agreement
Changelog
The following table describes the changes in each version of the connector.
Version |
Changes |
---|---|
5 |
Fix to add support for duplicate timestamps in input data. |
4 |
Added the |
3 |
Upgraded the Lambda runtime to Python 3.7, which changes the runtime requirement. |
2 |
Fix to reduce excessive logging. |
1 |
Initial release. |
A Greengrass group can contain only one version of the connector at a time. For information about upgrading a connector version, see Upgrading connector versions.
See also
-
Integrate with services and protocols using Greengrass connectors
-
Using Amazon CloudWatch metrics in the Amazon CloudWatch User Guide
-
PutMetricData in the Amazon CloudWatch API Reference