Skip to content
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

Add NO_COLOR env var to coralogix-aws-shipper #159

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

m-wynn
Copy link

@m-wynn m-wynn commented May 10, 2024

Description

The tracing library that coralogix-aws-shipper supports NO_COLOR, which avoids sending ansi control characters to cloudwatch logs.

Before:

�[2m2024-05-08T18:15:41.991174Z�[0m �[33m WARN�[0m �[2mcoralogix_aws_shipper::process�[0m�[2m:�[0m Non Cloudtrail Log Ingested - Skipping -

After:

2024-05-08T18:15:41.991174Z WARN coralogix_aws_shipper::process: Non Cloudtrail Log Ingested - Skipping -

How Has This Been Tested?

You can set NO_COLOR to 1 in your lambda and see that the control characters are no longer present in cloudwatch logs.

Checklist:

  • I have updated the relevant example in the examples directory for the module.
  • I have updated the relevant test file for the module.
  • This change does not affect module (e.g. it's readme file change)

The tracing library that coralogix-aws-shipper supports NO_COLOR, which
avoids sending ansi control characters to cloudwatch logs.

* [tracing library pr](tokio-rs/tracing#2647)

* [NO_COLOR](https://no-color.org/)
@m-wynn m-wynn requested a review from a team as a code owner May 10, 2024 17:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant