Conversation
Adds an explicit statement that Dynamic Parsing and Auto Parse are the same feature, per team confirmation, and rewords a sentence that implied Auto Parse Mode merely triggers Dynamic Parsing rather than being the same thing. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Adds explicit statements that Dynamic Parsing and Auto Parse are the same feature, per team confirmation, across all pages that use both terms: - docs/search/.../build-search/dynamic-parsing.md (main guide): clarifies terminology in the intro, documents all three ways to enable Auto Parse Mode (Log Search page, Scheduled Views, and the Search Job API's autoParsingMode parameter), cross-references the Dynamic Parsing Management API's createDynamicParsingRule operation for setting up Run Time FERs, converts the non-sequential "Rules and behavior" list from numbered to bulleted (per style guide, numbered lists are for sequential steps only), and tightens wording that had become redundant across these additions - docs/api/dynamic-parsing.md: adds the same terminology note - docs/api/index.md: updates the Dynamic Parsing hub card title to match - docs/manage/scheduled-views/add-scheduled-view.md, docs/manage/views-visibility.md: reword the Search Mode field description and fix a relative doc link to use the canonical absolute URL - New/updated screenshots reflecting the above Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Continues the terminology and consolidation pass on
dynamic-parsing.md:
- Corrects an inaccurate claim that "Dynamic Parsing" appears in the
UI (it doesn't; only "Auto Parse" does), per verification
- Cuts a redundant restatement of "same feature" in the intro that
duplicated an earlier sentence
- Trims the intro of "How it works" so it no longer restates the
page's opening claim, keeping only its new content (the FER
framing and "run time" terminology)
- Moves "Manual mode" next to "Enabling Auto Parse mode" as its
natural counterpart, instead of being separated by several
Auto-Parse-specific sections
- Nests the Log Search page's behavior notes under that bullet
instead of leaving them as a trailing paragraph after all three
enable methods are listed
- Removes an unsupported/contradictory claim that Manual mode offers
"optimized performance" (elsewhere the page says a well-scoped
Auto Parse FER is what optimizes performance)
- Replaces two Field Browser bullets that were fully duplicated
(with their own screenshots) by the field-browser hub page with
links to the existing content there
- Fixes two passive-voice sentences to active voice
- Fixes parallel structure in the Limitations bullets (two didn't
start with the same part of speech as the rest) and a grammar
error ("100 dynamic parsed extracted field")
- Removes the "Set up a Custom Run Time FER" step-by-step walkthrough,
which fully duplicated create-field-extraction-rule.md's
"Creating a new Field Extraction Rule" section, replacing it with
a link plus a Dynamic-Parsing-specific note about an expected
"duplicate rule" warning
- Fixes a relative doc link with an incorrect path depth that broke
the production build (onBrokenMarkdownLinks: throw) in
views-visibility.md, and standardizes both Scheduled Views pages'
links to the absolute path form
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
JV0812
approved these changes
Sep 1, 2026
JV0812
left a comment
JV0812
left a comment
Collaborator
There was a problem hiding this comment.
Terminology consolidation looks solid — verified the new cross-references (autoParsingMode/AutoParse against search-job.md, and the #search-for-fields / #nested-field-groupings anchors against field-browser/index.md) and they all resolve correctly.
Two small things worth a follow-up (not blocking):
- Broken sentence in
dynamic-parsing.md(Field Browser section, "total time-series" example): the comma + "it" were dropped when trimming this sentence, leaving "...is total time-series would be automatically formatted to..." Should read "...is total time-series; it would be automatically formatted..." or similar. - Orphaned screenshot:
static/img/.../dynamic-parsing/manual-parse.pngwas added in this PR but isn't referenced by any<img>tag — looks like it was meant to illustrate the new "Manual mode" section.
Approving since these are minor and easy to clean up in a follow-up.
- Fix a broken sentence in the field browser section ("...is total
time-series would be automatically formatted..." -> appositive).
- Reference the manual-parse.png screenshot in the Manual mode section;
it was added but orphaned.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This PR replaced the "+ Add to create an FER" step (its only reference) with a link to Creating a new Field Extraction Rule, leaving the image unused. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
kimsauce
enabled auto-merge
September 1, 2026 09:50
kimsauce
disabled auto-merge
September 1, 2026 09:54
vikas-sumo
approved these changes
Sep 1, 2026
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
3 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.
Purpose of this pull request
Clarifies that Dynamic Parsing and Auto Parse are the same feature, per team confirmation, across every page that uses both terms.
Main guide (
docs/search/.../build-search/dynamic-parsing.md):autoParsingModeparameter (previously only the Log Search page was documented)createDynamicParsingRuleoperation as the programmatic way to set up a Run Time FERRelated pages:
docs/api/dynamic-parsing.md: adds the same terminology clarificationdocs/api/index.md: updates the Dynamic Parsing hub card title to matchdocs/manage/scheduled-views/add-scheduled-view.md,docs/manage/views-visibility.md: reword the Search Mode field description to de-emphasize treating "Dynamic Parsing" as a separate proper noun, and fix a relative doc link to use the canonical absolute URLPlus new/updated screenshots reflecting the above.
Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/DOCS-1835
🤖 Generated with Claude Code