Skip to content
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

sns events to graylog #18

Open
eyablonowitz opened this issue Sep 29, 2016 · 2 comments
Open

sns events to graylog #18

eyablonowitz opened this issue Sep 29, 2016 · 2 comments

Comments

@eyablonowitz
Copy link

eyablonowitz commented Sep 29, 2016

I would like to send SNS events to Graylog. This is a feature that is available in competitive products (e.g. https://www.loggly.com/docs/amazon-sns/).

It seems like this Plugin already has a lot of the pieces to make this happen. It can already poll an SQS queue subscribed to an SNS topic for Cloudtrail log notifications. But it doesn't appear to support the more generic case of simply wanting to send events from any SNS topic into Graylog.

Is there a way to make this work with graylog-plugin-aws as-is? If not, would it make sense to support the SNS->Graylog use case in this plugin?

@wrsuarez
Copy link

wrsuarez commented Nov 4, 2016

You could use a Lambda event to send the SNS payload to Graylog using the pygelf library. If all you want is the SNS message and don't need to use the payload to follow down a trail to another data element a Lambda event would do it. Even a simply Python script could read and parse the SNS message (as the JSON structure is fairly fixed) and send it as a GELF entry to Graylog.

@eyablonowitz
Copy link
Author

Thanks @wrsuarez! I will have a look at that option.

But whether through graylog-plugin-aws or some other means (e.g. Lambda/pygelf), SNS to Graylog still seems like a use-case that should be well supported/documented as it is for Loggly (https://www.loggly.com/docs/amazon-sns/).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants