Add ec2MetadataServiceAvailable property #42
Closed
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
|
I like the idea @haukeh but can you remove all of the extraneous changes that have nothing to do with the fix? Thanks. |
|
Could you elaborate which changes you don't like? |
This pull request was closed.
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.
Hi there, while it was totally possible to use the appender while running in ECS containers, where the EC2 MetadataService is not reachable, a stacktrace was logged every time the
lookupInstanceNamefailed, which clutters the log unnecessarily.This PR introduces an appender property, that allows the user to disable the lookup of instanceId and instanceName completely, thus keeping the log free of unwanted stacktraces. This should also fix #39
Let me know what you think.
Best,
Hauke