Cloudwatch logs serving Jenkins build logs taking 30 seconds to load

Question

We are using the Jenkins Pipeline Plugin for Cloudwatch logs on a Jenkins instance. It simultaneously uploads and downloads the console logs for our jobs. Initially the console logs loaded pretty much instantaneously however as we have added more instances to our account this duration has increased dramatically taking  up to 30 seconds in some instances. 
Intermittently we receive the following com.amazonaws.services.logs.model.AWSLogsException: Rate exceeded
Researching on the web and it appears we're exceeding our  CloudWatch API limits. Would anyone be able to tell me where I can view these limits within our account and how to request to have them increased? Any help would be greatly appreciated.

Thanks,
Mark.

Answer

Hi Mark, thanks for reaching out!

You can review your CloudWatch Logs quotas using the [Service Quotas console](https://console.aws.amazon.com/servicequotas/home/services/logs/quotas) for CloudWatch Logs. This will show you your default and current Logs quotas, as well as which quotas can be increased.

You can determine which CloudWatch Logs API is being throttled by checking the Logs [service usage metrics in the AWS/Usage namespace](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatch-Logs-Monitoring-CloudWatch-Metrics.html#CloudWatchLogs-Usage-Metrics), and checking for ThrottleCount metrics related to Logs APIs. Once you have that info, you can use the Service Quotas console to request a limit increase for the affected API, as long as that API allows for limit increases.

General info regarding CloudWatch Logs quotas and instructions on requesting increases via the Service Quotas console [can be found here](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/cloudwatch_limits_cwl.html).

Cloudwatch logs serving Jenkins build logs taking 30 seconds to load

関連するコンテンツ