Cloudwatch Agent SIGHUP Log Rotation Fix #1645
Open
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.
Description of the issue
Currently Cloudwatch agent stops detecting log file rotation after recieving a SIGHUP signal. This issue can be resolving by having a persistent context for monitoring only to ensure that log rotation happens correclty.
Note: This is a solution to this problem, this solution makes the log Agent context persistent meaning clean up only happens in agent shut down. If we do prefer a alternative solution, we can work towards that. This is a good initial step.
Tests
Tested this locally by running
Log below shows the testing below
Requirements
Before commit the code, please do the following steps.
make fmt
andmake fmt-sh
make lint