Skip to content

[DOCS-13410] Move processor shortcode content inline (Batch 2)#34608

Merged
maycmlee merged 5 commits intomasterfrom
may/move-processor-shortcodes-batch-2
Feb 18, 2026
Merged

[DOCS-13410] Move processor shortcode content inline (Batch 2)#34608
maycmlee merged 5 commits intomasterfrom
may/move-processor-shortcodes-batch-2

Conversation

@maycmlee
Copy link
Contributor

@maycmlee maycmlee commented Feb 13, 2026

What does this PR do? What is the motivation?

Fixes DOCS-13410

No net new content. Just moving shortcode content into the docs.

Changes made:

  • Moved shortcode content inline from layouts/shortcodes/observability_pipelines/processors/
  • Added Overview and Setup headers
  • Converted image syntax to img src shortcode
  • Kept filter_syntax shortcode as-is

Processors updated:

  • parse_json
  • parse_xml
  • quota
  • reduce
  • remap_ocsf

Merge instructions

Merge readiness:

  • Ready for merge

Additional notes

This is part 2 of 3 batches to complete this task.

Move shortcode content into processor docs and restructure into Overview and Setup sections for:
- parse_json
- parse_xml
- quota
- reduce
- remap_ocsf
@maycmlee maycmlee added the WORK IN PROGRESS No review needed, it's a wip ;) label Feb 13, 2026
@maycmlee maycmlee requested a review from a team as a code owner February 13, 2026 22:03
@maycmlee maycmlee added the WORK IN PROGRESS No review needed, it's a wip ;) label Feb 13, 2026
@maycmlee maycmlee added review:quick and removed WORK IN PROGRESS No review needed, it's a wip ;) labels Feb 17, 2026
Copy link
Contributor

@domalessi domalessi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As long as all the header levels are as expected/desired, then good to go!

- If **Booleans** is selected, `true` and `false` are parsed as Booleans.
- If **Nulls** is selected, the string `null` is parsed as null.

##### Path notation example {#path-notation-example-parse-xml}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just confirming you want this to be a 5th level header?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Updating this one and the rest!

1. If you select **send events to overflow destination**, an overflow destination is added with the following cloud storage options: **Amazon S3**, **Azure Blob**, and **Google Cloud**.
1. Select the cloud storage you want to send overflow logs to. See the setup instructions for your cloud storage: [Amazon S3][2], [Azure Blob Storage][3], or [Google Cloud Storage][4].

#### Examples
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirming we want this to be a 4th level header (so nested under Setup, instead of being at the same level)?

@maycmlee maycmlee merged commit 5a9bb23 into master Feb 18, 2026
16 checks passed
@maycmlee maycmlee deleted the may/move-processor-shortcodes-batch-2 branch February 18, 2026 16:12
GLorenzo679 pushed a commit that referenced this pull request Feb 24, 2026
* fixes

* Move processor shortcode content inline for batch 2

Move shortcode content into processor docs and restructure into Overview and Setup sections for:
- parse_json
- parse_xml
- quota
- reduce
- remap_ocsf

* Update content/en/observability_pipelines/processors/reduce.md

* Apply suggestions from code review
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants