Sqs queue metrics8/11/2023 ![]() ![]() The endpoint /_aws/sqs/messages allows you to access all messages within a queue without triggering the visibility timeout our modifying access metrics. Our SQS implementation provides additional endpoints for developers under /_aws/sqs, that allow you to inspect queues without side effects.įor instance, sometimes you want to peek into queues without actually performing a ReceiveMessage operation. SQS_DISABLE_CLOUDWATCH_METRICS=1 will disable all CloudWatch metrics for SQS (including Approximate* metrics). This AWS parity feature is enabled by default, but can be deactivated.ĭeactivating CloudWatch metrics can improve the performance of SQS message operations, but will disable any integration with CloudWatch such as triggering alarms.Īdditionally, metrics about Approximate* messages are send to CloudWatch by default once every minute, but the interval (in seconds) can also be configured using SQS_CLOUDWATCH_METRICS_REPORT_INTERVAL=120. Sending, receiving, and deleting SQS messages will automatically trigger CloudWatch metrics. LocalStack disables this behavior by default, but it can be enabled by starting LocalStack with SQS_DELAY_RECENTLY_DELETED=1. Enabling QueueDeletedRecently errorsĪWS does not allow creating a queue with the same name for 60 seconds after it was deleted. LocalStack disables this behavior by default, but it can be enabled by starting LocalStack with SQS_DELAY_PURGE_RETRY=1. Since this format does not encode the region, you cannot query queues that exist in different regions with the same name.ĪWS only allows one call to PurgeQueue every 60 seconds. prefix is omitted.Īn alternative that can be useful if you cannot resolve LocalStack’s localhost domainĬurrently the default for backwards compatibility. This strategy behaves like the SQS legacy service endpoints, and uses to resolve to localhost. You can control the format of the generated Queue URLs by setting the environment variable SQS_ENDPOINT_STRATEGY when starting LocalStack to one of the following values. To run a GetQueueUrl request, add the ?Action=GetQueueUrl&QueueName=" query string to the URL. This has since been aligned to the behavior of AWS, which returns a. ![]() NoteIn previous releases, an empty HTTP request to a queue would return a.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |