-
Notifications
You must be signed in to change notification settings - Fork 513
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
[DOC] Add kv processor content gap doc #5781
Conversation
Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
@reta @gaobinlong Please take a look at the draft kv processor documentation. We particularly need your input for a real-life example of a kv processor ingest pipeline (see the section Using the processor steps 1-3). Thank you for your review! For reference, if you'd like to see recent documentation for other processors, go to https://opensearch.org/docs/latest/ingest-pipelines/processors/index-processors/. |
Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
@gaobinlong do you mind providing those, I believe you should have them ready, thank you |
Co-authored-by: Andriy Redko <drreta@gmail.com> Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
@reta @gaobinlong Thank you for your review. I've addressed your feedback. I'll move this forward for doc and editorial review and then get the PR merged. Thank you! |
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.
Looks good! Just a few suggestions/nits.
_ingest-pipelines/processors/kv.md
Outdated
|
||
The following table lists the required and optional parameters for the `lowercase` processor. | ||
|
||
| Name | Required/Optional | Description | |
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.
For consistency with the other processors, should the headings be: Parameter | Required | Description |
(Although, sometimes "Required/Optional" is the heading. See https://opensearch.org/docs/latest/ingest-pipelines/processors/date-index-name/ )
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.
We are updating the tables to now read Required/Optional. The first round originally said Required, but those need updating. I'll sync them this week. Good comment. Thanks!
Co-authored-by: Heather Halter <HDHALTER@AMAZON.COM> Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
Co-authored-by: Heather Halter <HDHALTER@AMAZON.COM> Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
Co-authored-by: Heather Halter <HDHALTER@AMAZON.COM> Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
Co-authored-by: Heather Halter <HDHALTER@AMAZON.COM> Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
@hdhalter I accepted your suggestions. I'll update the first round of processors that used Required instead of Required/Optional and Name instead of Parameter. Thanks for the review. |
Signed-off-by: Melissa Vagi <vagimeli@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.
@vagimeli Please see my comments and changes and let me know if you have any questions. Thanks!
_ingest-pipelines/processors/kv.md
Outdated
|
||
# KV processor | ||
|
||
The `kv` processor automatically extracts specific event fields or messages that are in a`key=value` format. This structured format organizes your data by grouping it together based on keys and values. It's helpful for analyzing, visualizing, and using data such as user behavior analytics, performance optimizations, or security investigations. |
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.
Last sentence: I suggest just "It's helpful in use cases such as user behavior analytics...". Otherwise, "...and using data, such as user behavior analytics, performance optimization, or security investigation data."
The `kv` processor automatically extracts specific event fields or messages that are in a`key=value` format. This structured format organizes your data by grouping it together based on keys and values. It's helpful for analyzing, visualizing, and using data such as user behavior analytics, performance optimizations, or security investigations. | ||
|
||
## Example | ||
The following is the syntax for the `kv` processor: |
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.
Please add a line between the heading and the following text.
_ingest-pipelines/processors/kv.md
Outdated
|
||
| Parameter | Required/Optional | Description | | ||
|---|---|---| | ||
`field` | Required | The name of the field that contains the data to be parsed. Supports [template snippets]({{site.url}}{{site.baseurl}}/ingest-pipelines/create-ingest/#template-snippets). | |
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.
`field` | Required | The name of the field that contains the data to be parsed. Supports [template snippets]({{site.url}}{{site.baseurl}}/ingest-pipelines/create-ingest/#template-snippets). | | |
`field` | Required | The name of the field containing the data to be parsed. Supports [template snippets]({{site.url}}{{site.baseurl}}/ingest-pipelines/create-ingest/#template-snippets). | |
_ingest-pipelines/processors/kv.md
Outdated
`exclude_keys` | Optional | The keys to exclude from the document. Default is `null`. | | ||
`include_keys` | Optional | The keys for filtering and inserting. Default is to include all keys. | | ||
`prefix` | Optional | The prefix to add to the extracted keys. Default is `null`. | | ||
`strip_brackets` | Optional | If set to `true`, strips brackets `()`, `<>,` or `[]` and quotes `'` or `"` from extracted values. Default is `false`. |
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.
Can we put parentheses around the examples?: (()
, <>,
or []
) and quotes ('
or "
)
_ingest-pipelines/processors/kv.md
Outdated
``` | ||
{% include copy-curl.html %} | ||
|
||
**Step 2 (Optional): Test the pipeline.** |
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.
**Step 2 (Optional): Test the pipeline.** | |
**Step 2 (Optional): Test the pipeline** |
_ingest-pipelines/processors/kv.md
Outdated
``` | ||
{% include copy-curl.html %} | ||
|
||
#### Response |
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.
Confirm heading level.
_ingest-pipelines/processors/kv.md
Outdated
} | ||
``` | ||
|
||
**Step 3: Ingest a document.** |
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.
**Step 3: Ingest a document.** | |
**Step 3: Ingest a document** |
_ingest-pipelines/processors/kv.md
Outdated
``` | ||
{% include copy-curl.html %} | ||
|
||
**Step 4 (Optional): Retrieve the document.** |
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.
**Step 4 (Optional): Retrieve the document.** | |
**Step 4 (Optional): Retrieve the document** |
Co-authored-by: Nathan Bower <nbower@amazon.com> Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
Co-authored-by: Nathan Bower <nbower@amazon.com> Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
* Add kv processor content gap doc --------- Signed-off-by: Melissa Vagi <vagimeli@amazon.com> Co-authored-by: Andriy Redko <drreta@gmail.com> Co-authored-by: Heather Halter <HDHALTER@AMAZON.COM> Co-authored-by: Nathan Bower <nbower@amazon.com> (cherry picked from commit 424956d) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
* Add kv processor content gap doc --------- (cherry picked from commit 424956d) Signed-off-by: Melissa Vagi <vagimeli@amazon.com> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Andriy Redko <drreta@gmail.com> Co-authored-by: Heather Halter <HDHALTER@AMAZON.COM> Co-authored-by: Nathan Bower <nbower@amazon.com>
* Add kv processor content gap doc --------- Signed-off-by: Melissa Vagi <vagimeli@amazon.com> Co-authored-by: Andriy Redko <drreta@gmail.com> Co-authored-by: Heather Halter <HDHALTER@AMAZON.COM> Co-authored-by: Nathan Bower <nbower@amazon.com>
Description
Adds documentation about kv processor; addresses content gap
Issues Resolved
#5651
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.