-
-
Notifications
You must be signed in to change notification settings - Fork 405
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
Develop a pluggable logging API for Cacti to be able to log to alternate logging formats #5852
Comments
Thoughts about capabilities and formatsThe local logging must be unified
Considerations for configuration
Additional considerations:
log items/identifiersMinimum/mandatory set of information (identifiers)
Optional items (where applicable / during debugging)
Collection of possible (sub)sections:
support for output plug-insThe logging function should act as a hub for plug-ins that allow logging to not only a local file but also other destinations.
Thoughts about implementation phasesprepare the refactoring
reforming the logging concept
|
Whoever has ideas that need to be considered, please speak up! :) |
Subsection also for plug-in modules. It could be useful if I can filter messages only from a specific plugin, for example if I have debug enabled for it |
I hope to provide some comments next week. |
Feature Request
Is your feature request related to a problem? Please describe
Support extensible logging to Splunk, Kafka, Elastic, etc.
Describe the solution you'd like
We need to determine the minimum logging attributes that are required to encompass these various logging solutions and then define the JSON, XML, etc. structures that are the minimum to perform such logging, and finally an API and class library that extends the output format using a pluggable and extensible output class function.
Describe alternatives you've considered
Continuing one size fit's all logging format.
Additional context
This is an R&D project that should deliver a report on what should happen vs. simply coding an enhancement. So, it's a call for a design document.
The text was updated successfully, but these errors were encountered: