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

Make log level configurable #145

Open
x4e-jonas opened this issue May 10, 2023 · 4 comments
Open

Make log level configurable #145

x4e-jonas opened this issue May 10, 2023 · 4 comments

Comments

@x4e-jonas
Copy link
Contributor

By default, CottontailDB runs in DEBUG mode. This is nut suitable for production deployments.

The log level should be runtime configurable (either by argument, option in config file or environment variable) and it might be a good idea to consider and document a sane default value.

@x4e-jonas x4e-jonas changed the title Make log level configurable #377 Make log level configurable May 10, 2023
@ppanopticon
Copy link
Member

ppanopticon commented May 10, 2023

In the next major release, it will be possible possible to provide a custom log4j2.xml via program configuration.

@x4e-jonas
Copy link
Contributor Author

That's great, though it's more convenient if you're able to define the log lever rather than deploying a whole XML config file yourself.

@x4e-jonas
Copy link
Contributor Author

A very simple implementation is shown here: vitrivr/cineast#378

@ppanopticon
Copy link
Member

While this may very well be ideal in your case, I still prefer the specification of the configuration file.

There is much more to logging than just the log level (e.g., logging to file vs. logging to console, log rotation etc.). Being able to specify your own log4j2.xml enables you to fine-tune these aspect to your particular use-case and setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants