-
Notifications
You must be signed in to change notification settings - Fork 623
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
Generalize kernel monitor. #44
Comments
With systemd-journal plugin enabled you can monitor the node for user space core files (either generated by ABRT or systemd-coredump). ABRT also logs uncaught Python, Ruby and Java exceptions to systemd-journal (systemd developers are working on their own Python exception handler). In Kernel you don't need to limit yourself to oopses, you can also detect Hardware issues in the form of MCEs and pstore oopses. |
@jfilak Thanks for your suggestion.
That's why we want to make NPD as configurable and plug-able as possible. I'd like to:
Any ideas and suggestions are welcome! |
We plan to add arbitrary log support in 1.6, there are following working items need to be done:
|
Close since this is done. |
Discussed with @apatil.
Kernel monitor was initially introduced to monitor kernel log and detect kernel issues.
However, in fact it could be extended to monitor other logs such as docker log, systemd log etc. by adding new
translator
. Currently it is already doable, but not very intuitive because:kernel xxx
.We should refactor the code to make it easier and more intuitive to extend kernel monitor:
kernelmonitor
tologmonitor
. We'll only use log monitor to monitor kernel log for K8s, but it should be easy for other users to reconfigure and extend it to monitor other logs./cc @kubernetes/sig-node
The text was updated successfully, but these errors were encountered: