Monitoring with CloudWatch metrics
You can use the tables in this section to review the metrics that Amazon CloudWatch Logs sends to Amazon CloudWatch every minute.
CloudWatch Logs metrics
The AWS/Logs namespace includes the following metrics.
| Metric | Description |
|---|---|
|
|
The number of specified API operations performed in your account.
Valid Dimensions: Class, Resource, Service, Type Valid Statistic: Sum Units: None |
|
|
The number of log events for which CloudWatch Logs received an error when forwarding data to the
subscription destination. If the destination service returns a retryable error such as a
throttling exception or a retryable service exception (HTTP 5xx for example), CloudWatch Logs
continues to retry delivery for up to 24 hours. CloudWatch Logs does not try to re-deliver if
the error is a non-retryable error, such as Valid Dimensions: LogGroupName, DestinationType, FilterName, PolicyLevel Valid Statistic: Sum Units: None |
|
|
The number of log events for which CloudWatch Logs was throttled when forwarding data to the subscription destination. If the destination service returns a retryable error such as a
throttling exception or a retryable service exception (HTTP 5xx for example), CloudWatch Logs
continues to retry delivery for up to 24 hours. CloudWatch Logs does not try to re-deliver if
the error is a non-retryable error, such as Valid Dimensions: LogGroupName, DestinationType, FilterName, PolicyLevel Valid Statistic: Sum Units: None |
|
|
The number of parsing errors encountered while processing embedded metric format logs. Such errors happen when logs are identified as embedded metric format but do not follow the correct format. For more information about the embedded metric format, see Specification: Embedded metric format.
Valid Dimensions: Valid Statistic: Sum Units: None |
|
|
The number
of validation errors
encountered
while processing embedded metric format logs.
These errors occur
when metric definitions
within embedded metric format logs do not adhere
to the embedded metric format and NoteCertain validation errors can lead to multiple metrics within an EMF log not being published. For example, all metrics set with an invalid namespace will be dropped.
Valid Dimensions: Valid Statistic: Sum Units: None |
|
|
The number of API operations performed in your account that resulted in errors.
Valid Dimensions: Class, Resource, Service, Type Valid Statistic: Sum Units: None |
|
|
The volume of log events in compressed bytes forwarded to the subscription destination. Valid Dimensions: LogGroupName, DestinationType, FilterName Valid Statistic: Sum Units: Bytes |
|
|
The number of log events forwarded to the subscription destination. Valid Dimensions: LogGroupName, DestinationType, FilterName, PolicyLevel Valid Statistic: Sum Units: None |
|
|
The volume of log events in uncompressed bytes uploaded to CloudWatch Logs.
When used with the Valid Dimensions: LogGroupName Valid Statistic: Sum Units: Bytes |
|
|
The number of log events uploaded to CloudWatch Logs. When used with the
Valid Dimensions: LogGroupName Valid Statistic: Sum Units: None |
|
|
The number of log events that matched a data string that you are auditing using the CloudWatch Logs data protection feature. For more information, see Help protect sensitive log data with masking. Valid Dimensions: None Valid Statistic: Sum Units: None |
|
|
The number of API operations performed in your account that were throttled because of usage quotas.
Valid Dimensions: Class, Resource, Service, Type Valid Statistic: Sum Units: None |
Dimensions for CloudWatch Logs metrics
The dimensions that you can use with most CloudWatch Logs metrics are listed in the following table.
| Dimension | Description |
|---|---|
LogGroupName
|
The name of the CloudWatch Logs log group for which to display metrics. |
DestinationType
|
The subscription destination for the CloudWatch Logs data, which can be AWS Lambda, Amazon Kinesis Data Streams, or Amazon Data Firehose. |
FilterName
|
The name of the subscription filter that is forwarding data from the log group to the destination. The subscription filter name is automatically converted by CloudWatch to ASCII and any unsupported characters get replaced with a question mark (?). |
Subscription filter metric dimensions
The dimensions for metrics related to account-level subscription filters are listed in the following table.
| Dimension | Description |
|---|---|
PolicyLevel
|
The level where the policy applies. Currently, the only valid value for this dimension
is |
DestinationType
|
The subscription destination for the CloudWatch Logs data, which can be AWS Lambda, Amazon Kinesis Data Streams, or Amazon Data Firehose. |
FilterName
|
The name of the subscription filter that is forwarding data from the log group to the destination. The subscription filter name is automatically converted by CloudWatch to ASCII and any unsupported characters get replaced with a question mark (?). |
Log transformer metrics and dimensions
CloudWatch Logs publishes the following log transformer metrics to CloudWatch in the AWS/Logs namespace.
| Metric | Description |
|---|---|
TransformationErrors
|
The number of errors encountered while transforming log events with the specified transformer. Unit: None Valid statistic: Sum |
TransformedBytes
|
The volume of the output of transformed log events, in uncompressed bytes. Unit: Bytes Valid statistic: Sum |
TransformedLogEvents
|
The number of transformed log events. Unit: None Valid statistic: Sum |
The following dimensions are used by transformer metrics.
| Dimension | Description |
|---|---|
LogGroupname
|
This dimension is used only for log-group-level transformers. |
PolicyLevel
|
This dimension is used only for account-level transformers. Currently the only valid value for this dimension is |
CloudWatch Logs service usage metrics
CloudWatch Logs sends metrics to CloudWatch that track the usage CloudWatch Logs API operations. These metrics correspond to AWS service quotas. Tracking these metrics can help you proactively manage your quotas. For more information, see Service Quotas Integration and Usage Metrics.
For example, you could track the ThrottleCount metric or set an alarm
on that metric. If the value of this metric rises, you should consider requesting
a quota increase for the API operation that is getting throttled. For more information
about CloudWatch Logs service quotas, see CloudWatch Logs quotas.
CloudWatch Logs publishes service quota usage metrics every minute in both the AWS/Usage
and AWS/Logs
namespaces.
The following table lists the service usage metrics published by CloudWatch Logs. These
metrics do not have a specified unit. The most useful statistic
for these metrics is SUM, which represents the total operation count for the 1-minute
period.
Each of these metrics is published with values for all of the Service,
Class, Type, and Resource dimensions. They are
also published with a single dimension called Account Metrics. Use the
Account Metrics dimension to see the sum of metrics for all
API operations in your account. Use the other dimensions and specify the name of
an API operation for the Resource dimension to find the metrics for
that particular API.
Metrics
| Metric | Description |
|---|---|
|
|
The number of specified operations performed in your account.
|
|
|
The number of API operations performed in your account that resulted in errors.
|
|
|
The number of API operations performed in your account that were throttled because of usage quotas.
|
Dimensions
| Dimension | Description |
|---|---|
|
|
Use this dimension to get a sum of the metric across all of the CloudWatch Logs APIs. If you want to see the metrics for one particular API,
use the other dimensions listed in this table and specify the
API name as the value of |
|
|
The name of the AWS service containing the resource. For CloudWatch Logs usage metrics, the value
for this dimension is |
|
|
The class of resource being tracked. CloudWatch Logs API usage metrics use this
dimension with a value of |
|
|
The type of resource being tracked. Currently, when the |
|
|
The name of the API operation. Valid values include all of the API operation names
that are listed in
Actions. For example, |
