Merged
Conversation
…docs into DT-588-new-processors
- Introduced the `break` processor to halt execution of remaining processors in the pipeline, with detailed configuration options and examples. - Added the `network_split` processor to separate host and port from a combined address string, including various usage scenarios and configuration details. - Updated topics.json to include new processor entries for `break` and `network_split`.
📝 WalkthroughWalkthroughThis PR adds documentation for five new processors (Break, Matches, Network Split, Suppress, and TSV), enhances the Contains processor documentation with new configuration fields, and updates processor count references from 169+ to 174+ across multiple files. Navigation and topic mapping entries are added to reflect the new documentation. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
Deploying virtualmetric-docs-test with
|
| Latest commit: |
700a920
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://8fa245a7.virtualmetric-docs-test.pages.dev |
| Branch Preview URL: | https://dt-588-new-processors.virtualmetric-docs-test.pages.dev |
|
📄 Docs Preview: https://dt-588-new-processors.virtualmetric-docs.pages.dev |
yusufozturk
approved these changes
Feb 27, 2026
Member
|
@coderabbitai full review |
✅ Actions performedFull review triggered. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (2)
docs/configuration/pipelines/processors/tsv.mdx (1)
53-53: Clarify the CSV fallback sentence for readability.Line 53 is a bit redundant and can be simplified to make the fallback guidance easier to scan.
✍️ Suggested wording
-The processor reads a single line of TSV data and maps each tab-delimited column to the corresponding target field. The tab separator is hardcoded and cannot be configured — use the `csv` processor with `separator: "\t"` equivalent or the `csv` processor's `separator` field for other delimiters. +The processor reads a single line of TSV data and maps each tab-delimited column to the corresponding target field. The tab separator is fixed and cannot be configured. For equivalent behavior, use the `csv` processor with `separator: "\t"`; for other delimiters, configure the `csv` processor accordingly.As per coding guidelines, Ensure consistency in terminology and formatting across all documentation files.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/configuration/pipelines/processors/tsv.mdx` at line 53, Simplify the redundant fallback sentence: replace the current line explaining the hardcoded tab separator with a single, clear sentence such as "Use the csv processor with separator: \"\\t\" to parse TSV data, or set the csv processor's separator field to parse other delimiters." Ensure terminology matches existing docs (use "csv processor" and "separator") and maintain the same formatting style as surrounding documentation.docs/configuration/pipelines/processors/contains.mdx (1)
166-187: Consider standardizing outcome wording in the example.“returns no match” is slightly less explicit than other outcome phrasing (e.g., “returns success”); using a canonical result term (such as “returns failure”) would improve consistency.
As per coding guidelines “Ensure consistency in terminology and formatting across all documentation files.”
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/configuration/pipelines/processors/contains.mdx` around lines 166 - 187, In the "Case Sensitive" ExampleGrid replace the outcome wording in the final CommentCol from "returns no match" to the canonical term used elsewhere (e.g., "returns failure") so terminology is consistent; update the CommentCol text that explains the result of the case_sensitive example to read "returns failure because \"WARNING\" does not equal \"warning\" in case-sensitive mode" (or similar canonical phrasing) within the same ExampleGrid block.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@docs/configuration/pipelines/processors/contains.mdx`:
- Around line 166-187: In the "Case Sensitive" ExampleGrid replace the outcome
wording in the final CommentCol from "returns no match" to the canonical term
used elsewhere (e.g., "returns failure") so terminology is consistent; update
the CommentCol text that explains the result of the case_sensitive example to
read "returns failure because \"WARNING\" does not equal \"warning\" in
case-sensitive mode" (or similar canonical phrasing) within the same ExampleGrid
block.
In `@docs/configuration/pipelines/processors/tsv.mdx`:
- Line 53: Simplify the redundant fallback sentence: replace the current line
explaining the hardcoded tab separator with a single, clear sentence such as
"Use the csv processor with separator: \"\\t\" to parse TSV data, or set the csv
processor's separator field to parse other delimiters." Ensure terminology
matches existing docs (use "csv processor" and "separator") and maintain the
same formatting style as surrounding documentation.
ℹ️ Review info
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Jira integration is disabled
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
static/img/graphics/feature-processor-support.svgis excluded by!**/*.svg
📒 Files selected for processing (10)
docs/about/key-features.mdxdocs/configuration/pipelines/processors/break.mdxdocs/configuration/pipelines/processors/contains.mdxdocs/configuration/pipelines/processors/matches.mdxdocs/configuration/pipelines/processors/network-split.mdxdocs/configuration/pipelines/processors/suppress.mdxdocs/configuration/pipelines/processors/tsv.mdxsidebars.tsstatic/img/graphics/feature-processor-support.mmdtopics.json
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
breakprocessor to halt execution of remaining processors in the pipeline, with detailed configuration options and examples.network_splitprocessor to separate host and port from a combined address string, including various usage scenarios and configuration details.breakandnetwork_split.Summary by CodeRabbit
Release Notes
New Features
Documentation