Skip to content

Conversation

@joshkalpin
Copy link
Contributor

Summary

Change logging "Fetching data file from..." to debug level from info.

Info level logging on this is causing us two problems:

  1. It's spamming our logs (which company wide are info) with this log line
  2. We don't want the datafile name, which happens to correspond to the api key in our logs either

Debug solves both of these and we can optionally turn it on if we are seeing issues with datafile fetching.

Test plan

N/A, only logging level

Issues

N/A

…ug level Info level logging on this is causing us two problems: 1) It's spamming our logs (which company wide are info) with this log line 2) We don't want the datafile name, which happens to correspond to the api key in our logs either Debug solves both of these and we can optionally turn it on if we are seeing issues with datafile fetching.
Copy link
Contributor

@mikecdavis mikecdavis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @kapin, the change looks good to me. If you can sign the Contributor License Agreement (CLA) I'll get this merged right away.

@joshkalpin
Copy link
Contributor Author

@joshkalpin
Copy link
Contributor Author

Would you also be able to retry the builds? The errors look unrelated to my change

@coveralls
Copy link

Pull Request Test Coverage Report for Build 1357

  • 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 89.354%

Totals Coverage Status
Change from base Build 1353: 0.0%
Covered Lines: 3777
Relevant Lines: 4227

💛 - Coveralls
@mikeproeng37
Copy link
Contributor

Builds are all passing now. Gonna merge.

@mikeproeng37 mikeproeng37 merged commit 568f9ed into optimizely:master Mar 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants