-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle cloudtrail message where the message is not json #249
Comments
Just found #117 but I checked and we have raw delivery disabled. |
@hamstah Thanks for the info. I will do some investigation to see if I can figure out why these messages are intermittently appearing in the queue. |
Hi @hamstah, Once you have everything set up, these messages should not continue to be generated. The workaround is to manually delete the validation messages on the SQS queue. There is a View/Delete Messages option in the menu on the main SQS page. |
Hey Dan,
Yeah that's what I've been doing to purge the queue, good to know it's only
on update and not periodical at least.
Thanks for looking into it
…On Mon, 30 Sep 2019, 8:25 pm Dan Torrey, ***@***.***> wrote:
Hi @hamstah <https://github.com/hamstah>,
I really appreciate you bringing this to our attention. These "CloudTrail
validation message" SNS notifications get created when the SNS topic for a
trail is updated or created. We will need to change the Graylog SNS
processing logic to safely ignore them.
Once you have everything set up, these messages should not continue to be
generated.
The workaround is to manually delete the validation messages on the SQS
queue. There is a View/Delete Messages option in the menu on the main SQS
page.
[image: image]
<https://user-images.githubusercontent.com/3423655/65905231-cf532900-e385-11e9-8fae-b26c5e6157da.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#249?email_source=notifications&email_token=AABN7DVPWAWPNH3SNWCDCITQMJADHA5CNFSM4I2BQNPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD76TVII#issuecomment-536689313>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABN7DXDH73R5HZ4TT4WFG3QMJADHANCNFSM4I2BQNPA>
.
|
Stacktrace
This is caused by those messages being put in the SQS queue by SNS sometimes (not sure what causes it). The Message field is not JSON so it fails to be parsed and the message stays in the queue and gets refetched forever in a loop, polluting the graylog logs with the stacktrace.
The text was updated successfully, but these errors were encountered: