This plugin provides native AWS instrumentation for monitoring and metrics collection, including: health and metrics for various AWS services, such as EC2, RDS, ELB, and more, as well as handlers for EC2, SES, and SNS.
[ ] Update Changelog following the conventions laid out here
[ ] Update README with any necessary configuration snippets
[ ] Binstubs are created if needed
[ ] RuboCop passes
[ ] Existing tests pass
Purpose
Highlight false positives in check-sqs-messages when metric is unsupported
Previously you could see something like this:
bundle _1.17.3_ exec ./bin/check-sqs-messages.rb -r us-east-1 -q test-sensu-380 -m ApproximateAgeOfOldestMessage -c 1
NEWER VERSION AVAILABLE: Please upgrade to AWS SDK For Ruby V3
SQSMsgs OK: 0 messages in test-sensu-380 queue
Instead this will now properly notify responders to the (now) known bug. As it appears to be an api limitation and not something we did in our code we will keep the discussion open for a proper solution but first things first is getting it to tell the truth. After the fix it should look something like this:
There is a bug that is being masked, this surfaces it. This will not actually break any code, system, etc but deploying this will result in several unknowns from community members.
Pull Request Checklist
380
General
[ ] Update Changelog following the conventions laid out here
[ ] Update README with any necessary configuration snippets
[ ] Binstubs are created if needed
[ ] RuboCop passes
[ ] Existing tests pass
Purpose
Highlight false positives in
check-sqs-messages
when metric is unsupportedPreviously you could see something like this:
Instead this will now properly notify responders to the (now) known bug. As it appears to be an api limitation and not something we did in our code we will keep the discussion open for a proper solution but first things first is getting it to tell the truth. After the fix it should look something like this:
Signed-off-by: Ben Abrams me@benabrams.it
Known Compatibility Issues
There is a bug that is being masked, this surfaces it. This will not actually break any code, system, etc but deploying this will result in several
unknown
s from community members.