-
Notifications
You must be signed in to change notification settings - Fork 29
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
chore: Remove logging.yaml #1809
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like we could also remove the config/logging.*
files
ac92663
to
a8bdd95
Compare
@@ -263,7 +252,6 @@ dockers: | |||
extra_files: | |||
- release_deps/VERSION.txt | |||
- release_deps/plugins | |||
- config/logging.stdout.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will containers continue to log to stdout / error?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unsure about containers. All I know is the supervisor starts the agent as it's own subprocess and directs output from stdout to a file called agent.log
. I'm not sure what that means for containers...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be a blocker that we resolve before cutting over to v2. Logging to a file within the container will be a no go.
To be clear, it does not need to block this PR, but we do need to track this as an issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dakota and I spoke offline about supporting container stdout / stderr logging. The tentative plan is to push for Supervisor support in this area, probably by capturing agent output and writing it to its own stdout / stderr.
* remove logging.yaml * remove logging files
* remove logging.yaml * remove logging files
* remove logging.yaml * remove logging files
* remove logging.yaml * remove logging files
* remove logging.yaml * remove logging files
Proposed Change
Cleanup references to
logging.yaml
Checklist