Skip to content

SUMO-282473 - Add AI Parse Assist to parse anchor UI tool doc - #6792

Open
JV0812 wants to merge 2 commits into
mainfrom
ai-parse-assist-doc-update
Open

SUMO-282473 - Add AI Parse Assist to parse anchor UI tool doc#6792
JV0812 wants to merge 2 commits into
mainfrom
ai-parse-assist-doc-update

Conversation

@JV0812

@JV0812 JV0812 commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

Purpose of this pull request

Updates the Parse Predictable Patterns Using an Anchor doc to cover the new AI Parse Assist feature. The parse anchor UI tool section has been restructured into two subsections — Manual parse (existing) and AI Parse Assist (new) — with steps, screenshots, and inter-links between them. Includes a service release note.

Select the type of change

  • Minor Changes - Typos, formatting, slight revisions
  • Update Content - Revisions, updating sections
  • New Content - New features, sections, pages, tutorials
  • Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

https://sumologic.atlassian.net/browse/SUMO-282473

- Restructure parse anchor UI tool section into Manual parse and AI Parse Assist subsections
- Add steps and screenshots for AI Parse Assist feature
- Add inter-links between the two parsing method subsections
- Add service release note for AI Parse Assist

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@JV0812 JV0812 self-assigned this Jun 11, 2026
@cla-bot cla-bot Bot added the cla-signed Contributor approved, listed in .clabot file label Jun 11, 2026
hide_table_of_contents: true
---

We're excited to introduce **AI Parse Assist** in the parse anchor UI tool that automatically generates a parse statement and field names from any text you highlight in a log message. This eliminates the need to manually identify and label fields, helping you build parse queries faster, especially when working with complex or unfamiliar log formats. [Learn more](/docs/search/search-query-language/parse-operators/parse-predictable-patterns-using-an-anchor/#ai-parse-assist).

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

it is not exactly in "in the parse anchor UI tool"

import useBaseUrl from '@docusaurus/useBaseUrl';

The parse operator (also called the parse anchor) parses strings according to specified start and stop anchors, and then labels them as fields for use in subsequent aggregation functions in the query such as sorting, grouping, or other functions.
The parse operator (also called the parse anchor) parses strings according to specified start and stop anchors, and then labels them as fields for use in subsequent aggregation functions in the query such as sorting, grouping, or other functions.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

(also called the parse anchor) - this is wrong statement.we can remove this. since this is existing - that is fine

1. Click **Submit**. The query is updated with the parse operation you constructed.<br/><img src={useBaseUrl('img/search/searchquerylanguage/parse-operators/anchor/query-from-parse-UI-tool.png')} alt="Screenshot of a query parsing the log entry with the commands method, ip, port." style={{border: '1px solid gray'}} width="600" />
1. Click **Start** to display the search results, which now show the parsed message.<br/><img src={useBaseUrl('img/search/searchquerylanguage/parse-operators/anchor/parsed-results.png')} alt="Search results which now show the parsed message." style={{border: '1px solid gray'}} width="800" />

### AI Parse Assist

@dineshmeka701557 dineshmeka701557 Jul 29, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

We should also mention limitations of AI Parse Assist @prakhar-sumo can help Eg: 1. We dont allow AI Parse assist on Json logs 2. There is 600 char limit for highlighed text to parse

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed Contributor approved, listed in .clabot file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants