-
Notifications
You must be signed in to change notification settings - Fork 30
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
feat: Add Zookeeper Plugin #499
Conversation
That example parse doesn't look like it's working right; I'd expect to see the severity + timestamp parsed, and also a few attributes on the LogRecord like Maybe we need to take some of the changes that were being made in observIQ/stanza-plugins#399? Seems like there is a regex there for messages w/ no ID, which seems to be the problem with this data. I also wonder if the log format ends up being different for "standalone" zookeeper, as opposed to when it's run in conjunction with hbase/kafka. Seems strange that we didn't account for this in the original plugin. |
@BinaryFissionGames and @dmikolay
I ran into this when working on ops agent. If the node is part of a cluster it'll have the Here's what I did in ops-agent https://github.com/GoogleCloudPlatform/ops-agent/blob/master/apps/zookeeper.go#L76-L120 |
9aa2e13
to
fd81a8c
Compare
After adding a router and making regex changes, here's a new example of the plugin at work This line in the test file:
Produced this example log:
|
fd81a8c
to
f6c7912
Compare
f6c7912
to
3032d1f
Compare
Proposed Change
Checklist