-
Notifications
You must be signed in to change notification settings - Fork 207
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
Updates Trace Analytics documentation for Data Prepper 2.0 #1748
Updates Trace Analytics documentation for Data Prepper 2.0 #1748
Conversation
…ur documentation. Also includes a short guide to migrating to Data Prepper 2.0 for Trace Analytics. Signed-off-by: David Venable <[email protected]>
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.
This record_type
parameter will be removed completely in Data Prepper 2.0, and only support event
right? So we will have to revert this soon if it is merged
Codecov Report
@@ Coverage Diff @@
## main #1748 +/- ##
============================================
+ Coverage 93.38% 93.40% +0.01%
Complexity 1372 1372
============================================
Files 182 182
Lines 4068 4077 +9
Branches 323 323
============================================
+ Hits 3799 3808 +9
Misses 189 189
Partials 80 80
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Possibly, that is correct. But, for now, users are having difficulty starting Data Prepper. I've mentioned in a few threads that it may be valuable to keep |
This looks good to me. The PR to remove |
…n on either Data Prepper 2.0 or 1.x. Signed-off-by: David Venable <[email protected]>
Description
Updates documentation to set the
record_type: event
property. Also includes a short migration guide to 2.0 for Trace pipelines.Issues Resolved
Resolves #1735
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.