adding examples to drop_event processor in data prepper #11225
Conversation
Signed-off-by: Anton Rubin <[email protected]>
AntonEliatra
requested review from
AMoo-Miki,
dlvenable,
epugh,
kolchfa-aws,
natebower and
sumobrian
as code owners
|
Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged. Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer. When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review. |
|
@dlvenable Can you please review this PR? |
Signed-off-by: Anton Rubin <[email protected]>
| :--- | :--- | :--- | :--- | ||
| drop_when | Yes | String | Accepts an OpenSearch Data Prepper expression string following the [expression syntax]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/expression-syntax/). Configuring `drop_events` with `drop_when: true` drops all the events received. | ||
| handle_failed_events | No | Enum | Specifies how exceptions are handled when an exception occurs while evaluating an event. Default value is `drop`, which drops the event so that it is not sent to OpenSearch. Available options are `drop`, `drop_silently`, `skip`, and `skip_silently`. For more information, see [handle_failed_events](https://github.com/opensearch-project/data-prepper/tree/main/data-prepper-plugins/drop-events-processor#handle_failed_events). | ||
| handle_failed_events | No | Enum | Specifies how exceptions are handled when an exception occurs while evaluating an event. Default value is `drop`, which drops the event so that it is not sent to OpenSearch. Available options are: <br> - `drop`: The event will be dropped and a warning will be logged.<br> - `drop_silently`: The event will be dropped without warning. <br> - `skip`: The event will not be dropped and a warning will be logged. <br> - `skip_silently`: The event will not be dropped and no warning will be logged.<br>For more information, see [handle_failed_events](https://github.com/opensearch-project/data-prepper/tree/main/data-prepper-plugins/drop-events-processor#handle_failed_events). |
There was a problem hiding this comment.
so that it is not sent to OpenSearch
Data Prepper can send to multiple sinks. Also, it won't go to any other processors after this. It would be more accurate to say:
so that it is not sent to any sinks or further processors.
| filter-debug-logs-pipeline: | ||
| source: | ||
| http: | ||
| port: 2021 |
There was a problem hiding this comment.
Let's not include the port configuration. 2021 is the default.
| multi-condition-filter-pipeline: | ||
| source: | ||
| http: | ||
| port: 2022 |
There was a problem hiding this comment.
Let's not include the port configuration and use the 2021 default. It is not likely that people are running these at the same time.
3 participants
Description
adding examples to drop_event processor in data prepper
Version
all
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.