config: Remove syslog handler #2250
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Pull Request Overview
This PR removes the syslog handler from the logging configuration since the app no longer runs on Heroku.
- Removed syslog host and port configuration
- Removed the syslog handler block from the logging handlers configuration
- Updated the root logger to no longer include the syslog handler
Now that this app is not running on Heroku there's no need to use the syslog handler
blarghmatey
force-pushed
the
tm/k8s_logging
branch
from
44c346d to
eb43198
Compare
This was referenced May 16, 2025
Closed
Closed
Closed
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What are the relevant tickets?
N/A
Description (What does it do?)
Remove syslog handler for logging
How can this be tested?
Verify that logs are still displayed in docker-compose output
Additional Context
Now that this app is not running on Heroku there's no need to use the syslog handler