RUM-2441 make synthetics logs more verbose#1813
Merged
Merged
Conversation
0xnm
approved these changes
Jan 8, 2024
xgouchet
force-pushed
the
xgouchet/RUM-2441/verbose_synthetics_logs
branch
from
January 8, 2024 14:05
f0360f9 to
48344ed
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #1813 +/- ##
===========================================
- Coverage 83.44% 83.42% -0.02%
===========================================
Files 466 466
Lines 16375 16378 +3
Branches 2455 2454 -1
===========================================
Hits 13663 13663
+ Misses 2047 2042 -5
- Partials 665 673 +8
|
mariusc83
approved these changes
Jan 9, 2024
Merged
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Prints the application and session id whenever a view changes.
Motivation
The Synthetics team have a delay when fetching logs from the device running the app under test. Because of this the initial Application and Session ID (printed early in the app's lifecycle) are lost and can't be retrieved. Repeating them whenever a view is started provides a workaround if the first logs of the app can't be read.