Go back to previous timestamp on logging#8925
Conversation
|
The PR is ready for review, I just need to test it manually on all components, until then I'll keep it on draft. |
|
Is this really needed @JoaoJandre ? seems to me this is a user choice and taking a standard as the default is not that bad a choice. (did you get complaints?) |
This will revert the default timestamp to what it used to be before the Log4j2 update, I mistakenly changed the default timestamp when upgrading the default log4j configurations on #7131. This PR will change the timestamp to the one that was being used before #7131. The change on the timestamp pattern could break users' log parsers, that's why I created this PR. If they wish, they can change the value to ISO8601 or whatever they prefer. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8925 +/- ##
=============================================
+ Coverage 13.17% 15.54% +2.36%
- Complexity 9214 11974 +2760
=============================================
Files 2725 5493 +2768
Lines 258235 481034 +222799
Branches 40249 58580 +18331
=============================================
+ Hits 34013 74758 +40745
- Misses 219913 398014 +178101
- Partials 4309 8262 +3953
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
@blueorangutan package |
|
@JoaoJandre a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 10578 |
|
@blueorangutan test |
|
@DaanHoogland a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
[SF] Trillian Build Failed (tid-11059) |
|
@blueorangutan package |
|
@DaanHoogland a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 10619 |
|
@blueorangutan LLtest |
|
@DaanHoogland a [LL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
@blueorangutan package |
|
@rohityadavcloud a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 10942 |
|
@blueorangutan test |
|
@rohityadavcloud a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-11337)
|
Description
Before #7131, the logs' timestamp was in the
2024-04-02 22:04:28,617, with the upgrade to log4j2, the logs' timestamp was changed to the2024-04-02T21:55:12,724format. This PR changes the timestamp back to the previous format.Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?