Monitoring with CloudWatch metrics
CloudWatch Logs sends metrics 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. Valid Dimensions: LogGroupName, DestinationType, FilterName Valid Statistic: Sum Units: None |
|
|
The number of log events for which CloudWatch Logs was throttled when forwarding data to the subscription destination. Valid Dimensions: LogGroupName, DestinationType, FilterName Valid Statistic: Sum Units: None |
|
|
The number
of metrics
that were detected
in EMF logs,
but failed
to be published
to CloudWatch metrics.
This can occur due
to validation errors,
parsing errors,
or internal errors.
See the respective metrics
Valid Dimensions: Valid Statistic: Sum Unit: None |
|
|
The number
of parsing errors
encountered
while processing EMF logs.
Such errors happen
when logs are identified
as EMF via the
Valid Dimensions: Valid Statistic: Sum Units: None |
|
|
The number of internal errors encountered while processing EMF logs. Such errors happen when valid EMF logs cannot be processed due to AWS internal issues. CloudWatch Logs will retry processing the EMF log for up to 24 hours.
Valid Dimensions: Valid Statistic: Sum Units: None |
|
|
The number
of validation errors
encountered
while processing EMF logs.
These errors occur
when metric definitions
within EMF logs do not adhere
to the EMF and Certain 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 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 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 CloudWatch Logs metrics are listed below.
| 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 Kinesis 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 (?). |
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, |
