-
Notifications
You must be signed in to change notification settings - Fork 210
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
Skip Timestamp For Agent Log #885
Conversation
0bed125
to
9a0580a
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #885 +/- ##
==========================================
+ Coverage 57.58% 62.64% +5.05%
==========================================
Files 370 338 -32
Lines 17548 17016 -532
==========================================
+ Hits 10105 10659 +554
+ Misses 6848 5800 -1048
+ Partials 595 557 -38
☔ View full report in Codecov by Sentry. |
6fd1144
to
81e3ecd
Compare
9d13f64
to
c8d710a
Compare
08f5a67
to
613b7c6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should update the branch with main, but except for that looks good to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! I had PR which will modify the timestamp_layout
and timestamp_regex
. I can make the changes in my PR if this gets merged first but aside from that all good
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should update the branch with main, but except for that looks good to me!
Description of the issue
The customer noticed the issue because we now log the toml output on start of agent. This includes a line with the date format that is old.
We keep logging the same entry for a bad time stamp config when recording agent logs.
If we have a valid timestamp in the log we will not keep logging the same log line.
Description of changes
Do not use timestamp when reading agent log file.
License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Tests
Manual testing to see no log for invalid timestamp in logs with config
log out if time stamp is skipped in translation layer