Repository navigation
Remove recurring exception from the Management Server logs - #14441
bernardodemarco wants to merge 1 commit into
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #14441 +/- ##
=========================================
Coverage 20.39% 20.40%
Complexity 21283 21283
=========================================
Files 6481 6481
Lines 588040 588040
Branches 72021 72021
=========================================
+ Hits 119957 119977 +20
+ Misses 455052 455034 -18
+ Partials 13031 13029 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
@blueorangutan package |
|
@bernardodemarco a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✖️ el8 ✖️ el9 ✔️ debian ✔️ suse15. SL-JID 19655 |
|
@blueorangutan package |
|
@bernardodemarco a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 19839 |
Description
Whenever the Management Server attempts to retrieve the accessing API key from an HTTP request authenticated via a session, an exception is logged at the
WARNlevel. However, since this scenario is extremely common, the exception is logged repeatedly, which can be undesired during troubleshooting.This PR changes the log level to
TRACEand modifies the log output to only include the exception message, which contains all the information required for troubleshooting.Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?