Optionally log tabbyAPI output to a file in addtion to stdout #228
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes logging to file in JSON format an option at runtime in support of bare metal systemd implementations.
Why should this feature be added?
Tabby should include the option to output logs to a file. Further, it should support serializing the logs to JSON as an option. It is easier to ingest a web application's logs to common solutions like the Elastic Stack when the application writes log output to disk as structured data. The file that the logs are written to can be specified via an environment variable.
log_to_file
is set to false by default. If enabled, tabbyAPI will write logs to both stdout and to ./tabbyAPI.log unlessTABBY_LOG_FILE
is specified.Examples
Additional context
You guys rock. No hard feelings if you think this is unnecessary. If my changes don't meet your standards I am happy to adjust as needed.