Skip to main content

Triage SQS Queue Idle Monitor NO_MESSAGES_SENT

  1. Configure SQS Queue Idle Monitor
  2. Use Case for SQS Queue Idle Monitor
  3. Triage Guides by Violation Type
    1. Triage SQS Queue Idle Monitor NO_MESSAGES_SENT

Triage Guide: No Messages Sent

Understand​

Why should I care about fixing this issue? Idle SQS queues generate unnecessary costs with no operational benefit.

Validate​

How am I sure that this alert is true and accurate? Verify the NumberOfMessagesSent and NumberOfEmptyReceives metrics via the AWS CloudWatch console.

Does this policy scan on a schedule or is it Reactive? The policy is reactive and scans daily.

Triage​

What is the impact if it is unfixed? Continued costs without operational payoff.

Does this problem get worse over time if it is unaddressed? Costs will accumulate over time without addressing the idle queue.

Can remediation cause outages or downtime to any other running service? Removing an idle queue should not affect active services but verify to ensure no service depends on this queue.

Act​

What do I do to fix this alarm? Evaluate the queue's purpose, consider deleting the queue if it's confirmed idle, or reconfigure it to be part of a working message processing setup.

Reflect​

What should I do if this alarm wasn't a good use of time? Adjust the policy's thresholds to better fit the queue's expected usage patterns or disable the policy for this particular queue.