-
Notifications
You must be signed in to change notification settings - Fork 478
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
New blog post introducing Data Prepper 1.3.0 and its new features. #729
New blog post introducing Data Prepper 1.3.0 and its new features. #729
Conversation
Co-authored-by: Taylor Gray <tylgry@amazon.com> Co-authored-by: David Powers <ddpowers@amazon.com> Signed-off-by: David Venable <dlv@amazon.com>
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 looks pretty good to me. I have a few small requests - mostly formatting and style.
[key-value processor](https://github.com/opensearch-project/data-prepper/blob/main/data-prepper-plugins/key-value-processor/README.md) | ||
provides robust support for extracting keys and values from strings like these. | ||
|
||
The following example shows how you could use the new split_string processor and key_value processor to get query |
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.
split_string, key_value -> put in backticks (``)
|
||
## Setting Timestamps on Events | ||
|
||
Data Prepper new provides a new |
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.
'Data Prepper new provides' -> doesn't parse. Is something missing?
|
||
## Other Improvements | ||
|
||
In addition to the new features already described, we have made a few other improvements to Data Prepper. |
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.
I'd revise this - does 'we' refer to the authors of the blog post or the software?
|
||
You can see the [Data Prepper roadmap](https://github.com/opensearch-project/data-prepper/projects/1) to see other | ||
upcoming changes. If there are any features on the roadmap that you are most interested in, please comment on the | ||
issue to help us prioritize issues. You can also request any changes by creating a |
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.
'help us' -> 'help the team'
for example, would allow a user to add in an entry to their data to help debug the flow of data: | ||
|
||
|
||
``` |
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.
Change to ```yaml
The following example shows how you could use the new split_string processor and key_value processor to get query | ||
parameters from an Apache log line. | ||
|
||
``` |
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.
Change to ```yaml
processor, and then aggregates on those fields over a period of 30 seconds using the `aggregate` processor and | ||
the `put_all` action. At the end of the 30 seconds, the aggregated log is sent to the OpenSearch sink. | ||
|
||
``` |
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.
Change to ```yaml
|
||
Given the following batch of logs: | ||
|
||
``` |
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.
Change to ```json
|
||
The grok processor will extract the `identification_keys` to create the following logs: | ||
|
||
``` |
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.
Change to ```json
And when the group is concluded after a duration of 30 seconds from the time that the first log is | ||
received by the `aggregate` processor, the following aggregated log will be shipped to the sink: | ||
|
||
``` |
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.
Change to ```json
…back. Co-authored-by: Taylor Gray <tylgry@amazon.com> Co-authored-by: David Powers <ddpowers@amazon.com> Signed-off-by: David Venable <dlv@amazon.com>
@stockholmux , Thank you for the feedback. I made the changes you suggested. Thanks for noting the language support. I didn't know that the project page's tooling supported these. I think it especially helps with the YAML. |
…0 release. Co-authored-by: Taylor Gray <tylgry@amazon.com> Co-authored-by: David Powers <ddpowers@amazon.com> Signed-off-by: David Venable <dlv@amazon.com>
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
Description
This blog post introduces Data Prepper 1.3.0. We'd like it to go live on Tuesday Mar 22.
Issues Resolved
N/A
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.