Change runtime log level #293
Merged
Conversation
This file contains 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
…ing runtime. Updated amazon-cloudwatch-agent-ctl with action to set log level.
adam-mateen
reviewed
Oct 13, 2021
adam-mateen
approved these changes
Oct 13, 2021
adam-mateen
reviewed
Oct 13, 2021
This was referenced Apr 6, 2022
sky333999
pushed a commit
that referenced
this pull request
Jul 21, 2023
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.
Description of the issue
For this issue: #280
The CloudWatch agent uses the telegraf logger to manage its logging. Currently, to change the log level, the agent configuration file needs to be updated to include
debug: truein the agent section and the process needs to be restarted for the change to take effect.Description of changes
Added a goroutine created in the
reload_loopthat will check theenv_config.jsonfile every 30 seconds to see if it has been changed. If the file has been changed, it will re-read the file and update the known environment variables. Normally, this is only done once on start up. It then tries to set the log level to theCWAGENT_LOG_LEVELenvironment variable.The user is able to manually update the
env-config.jsonfile if desired, but asetenvflag has been added to theamazon-cloudwatch-agentbinary that will update the log level in the file. This can be accessed by running:on linux:
sudo /opt/aws/amazon-cloudwatch/bin/amazon-cloudwatch-agent-ctl -a set-log-level -l DEBUGor
on windows:
& $Env:ProgramFiles\Amazon\AmazonCloudWatchAgent\amazon-cloudwatch-agent-ctl.ps1 -a set-log-level -l DEBUGNote: If a user has
debug:truepresent in their configuration file,CWAGENT_LOG_LEVELwill be set to "DEBUG" after translation of the configuration file has completed.License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Tests
Tested on linux and windows ec2 instances.