Skip to content

Conversation

@szesch
Copy link

@szesch szesch commented Nov 12, 2015

When running a KCL application that consumes from many shards, output from DefaultCWMetricsPublisher will often log too much unnecessary information. This makes reading log files a bit of a headache and it wastes bytes when shipping log files to downstream log collectors.

@samcday
Copy link

samcday commented Mar 2, 2016

Big +1 on this. We worked around it by setting the log level for the com.amazonaws.services.kinesis.metrics.impl package to WARN.

@Kahn
Copy link

Kahn commented Apr 4, 2016

This apparently shipped in https://github.com/awslabs/amazon-kinesis-client#release-162-march-23-2016 @manango can you close or merge this PR please? Its confusing to leave open.

@manango
Copy link
Contributor

manango commented Apr 5, 2016

Thanks szesch for providing the fix. This change has been incorporated into 1.6.2 release. Closing the PR.

@manango manango closed this Apr 5, 2016
ychunxue pushed a commit to ychunxue/amazon-kinesis-client that referenced this pull request Jul 9, 2020
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.

4 participants