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

[epilogue] Allow individual data loggers to have configurable logging levels #7292

Open
SamCarlberg opened this issue Oct 26, 2024 · 0 comments
Labels
component: epilogue Annotation-based logging library type: fix Iterations on existing features or infrastructure.

Comments

@SamCarlberg
Copy link
Member

Epilogue allows users to specify the importance of individual logged fields, which the generated loggers will compare against the runtime-configured minimum importance level. This allows certain groups of data to be conditionally logged or not, but it does not allow individual loggers in multi-logger setup to have different logging levels (for example, users may not want to log low importance data to NT to save on bandwidth, but still log it to disk).

This could be implemented by adding and importance level argument to data loggers log methods, and passing in the importance level of the logged fields. Data loggers would need to be configurable with a minimum importance level; the global configuration can be kept, since it's useful as a fallback and to prevent expensive calls to retrieve unimportant data

@SamCarlberg SamCarlberg added the component: epilogue Annotation-based logging library label Oct 26, 2024
@calcmogul calcmogul added the type: fix Iterations on existing features or infrastructure. label Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: epilogue Annotation-based logging library type: fix Iterations on existing features or infrastructure.
Projects
None yet
Development

No branches or pull requests

2 participants