-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Filebeat module for zookeeper logs #25061
Comments
Pinging @elastic/integrations (Team:Integrations) |
can u post sample logs. I think this would be very interesting. I see the audit logs here, https://zookeeper.apache.org/doc/r3.7.0/zookeeperAuditLogs.html. Are there other logs? |
I've created a draft PR to add a module for ZooKeeper. I currently only have the audit log fileset. If there are other log types, please let me know and provide sample data. |
nice. Thanks @legoguy1000! Here's a sample Alternatively, we could probably change the logging output format rather than grokking (zookeeper just uses log4j). Not sure what sort of precedent filebeat modules have in that space though. Maybe better to have modules just assume default output configuration. |
Those logs are disgusting. Working on a basic grok pattern now. Will probably need help to parse the actual messages. Using https://stackoverflow.com/questions/45569100/what-is-the-format-of-zookeeper-logs and to parse the format as best I can https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html |
I've updated the PR with the zookeeper.log fileset. Can you let me know if/how to parse the logs more? Or if you think its good, I can make it not draft. |
Describe the enhancement:
We have a lot of great modules in https://github.com/elastic/beats/tree/master/x-pack/filebeat/module but nothing for https://zookeeper.apache.org/
It'd be great to have a module with pre-defined beats & ingest pipeline configs to get those logs into ECS format.
Describe a specific use case for the enhancement or feature:
We run zookeeper as part of backend infrastructure for https://cloud.elastic.co/ and would like to ingest structured logs.
The text was updated successfully, but these errors were encountered: