-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
k6 Insights (2/2): Integrate request metadata output to cloud output v1 #3202
Conversation
e5594bb
to
d7395ae
Compare
Codecov Report
@@ Coverage Diff @@
## master #3202 +/- ##
=======================================
Coverage 72.69% 72.70%
=======================================
Files 254 259 +5
Lines 19802 19864 +62
=======================================
+ Hits 14396 14442 +46
- Misses 4497 4519 +22
+ Partials 909 903 -6
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
Let's keep config under a single source of truth.
And question about the runFlushRequestMetadatas
The base branch was changed.
0844bcb
to
2a2f95c
Compare
What?
This PR incorporates the request metadata output into cloud output v1.
Why?
Due to cloud output v2 being at risk for v0.46.0, we decided to incorporate the new request metadata output into cloud output v1. This change is done to mitigate the risk of failing to deliver the new insights features.
Related PR(s)/Issue(s)
This PR is part of a PR chain. Previous PR - #3201.
Previous PRs: