Skip to content

Commit b23dd2f

Browse files
committed
add rn
1 parent 39766e7 commit b23dd2f

File tree

2 files changed

+24
-7
lines changed

2 files changed

+24
-7
lines changed

blog-service/2025-04-01-copilot.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
title: Now in Beta - Copilot Supports Unstructured Logs (Copilot)
3+
image: https://help.sumologic.com/img/sumo-square.png
4+
keywords:
5+
- copilot
6+
- log-search
7+
- search
8+
hide_table_of_contents: true
9+
---
10+
11+
You can now use Copilot to analyze raw, unstructured log data, even if it’s not in JSON or lacks Field Extraction Rules (FERs). This Beta expands Copilot’s reach to custom, legacy, and inconsistent log formats with no setup required.
12+
13+
* Ask questions in plain English—no schema or FERs needed.
14+
* Works with raw logs like firewalls, syslog, and homegrown formats.
15+
* Ideal for error triage, threat hunting, and exploratory analysis.
16+
17+
To join the Beta, [enroll here](https://forms.gle/LozrrAppM9FM94tS9) or reach out to your Sumo Logic account team.

docs/search/copilot-unstructured-logs.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -21,16 +21,16 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
2121

2222
This feature is in Beta. To participate, contact your Sumo Logic account executive or [enroll here](https://forms.gle/LozrrAppM9FM94tS9).
2323

24-
Unstructured Logs Support for [Sumo Logic Copilot](/docs/search/copilot), our AI assistant, enables it to understand and provide insights from raw, text-based logseven if they don't follow a structured format like JSON. This means you can ask questions in plain English and get meaningful results from nearly any log data, without requiring Field Extraction Rules (FERs).
24+
Unstructured Logs Support for [Sumo Logic Copilot](/docs/search/copilot), our AI assistant, enables it to understand and provide insights from raw, text-based logs, even if they don't follow a structured format like JSON. This means you can ask questions in plain English and get meaningful results from nearly any log data, without requiring Field Extraction Rules (FERs).
2525

2626
## What's new
2727

28-
Previously, Copilot worked best on structured (JSON) logs. Now, it automatically applies parsing logic to unstructured logs, even if no FERs are configured. This allows Copilot to interpret logs from many popular data sources out-of-the-box.
28+
Currently, [Copilot works best on structured (JSON) logs](/docs/search/copilot/#compatible-log-formats). With this beta update, Copilot automatically applies parsing logic to unstructured logs, even if no FERs are configured. This allows Copilot to interpret logs from many popular data sources out-of-the-box and enables support for a broader range of log types.
2929

30-
Copilot learns from usage patternsif a log source is already used in dashboards or commonly queried, it’s more likely to produce strong results.
30+
Copilot learns from usage patterns; if a log source is already used in dashboards or commonly queried, it’s more likely to produce accurate, actionable results.
3131

3232
* **Broader coverage**. Copilot now parses and generates insights from unstructured log formats, even without FERs, making it useful for environments that include custom or inconsistent log types.
33-
* **Improved usability**. Ask questions in natural language. Copilot interprets your intent and suggests relevant searcheseven for raw, non-JSON logs.
33+
* **Improved usability**. Ask questions in natural language. Copilot interprets your intent and suggests relevant searches, even for raw, non-JSON logs.
3434
* **Performance and reliability**. Response times and suggestion accuracy are consistent with Copilot’s structured log experience.
3535
* **Security and compliance**. The same strict data handling and privacy standards apply. Unstructured Logs Support builds on Copilot’s secure foundation.
3636
* **Common use cases**.
@@ -46,15 +46,15 @@ Copilot learns from usage patterns—if a log source is already used in dashboar
4646
- “Find logs with IP 192.0.2.0”
4747
- “What are the top 5 errors from nginx logs today?”
4848
* Use dashboards to monitor your log sources. Copilot performs better when logs are part of existing queries and visualizations.
49-
* Logs with clear timestamps, separators (like commas or tabs), and consistent patterns tend to yield better results.
49+
* Logs with consistent formats, clear timestamps, and standard separators (like commas or tabs) yield better results.
5050

5151
## Related updates
5252

5353
These recent Copilot enhancements make it even easier to work with unstructured logs:
5454

55-
* **Dynamic conversation titles**. Your queries are automatically named for easy organization and retrieval.
55+
* **Dynamic conversation titles**. Your queries are automatically titled for easy organization and retrieval.
5656
* **"Open in Copilot" for alerts**. Investigate alerts directly in Copilot without losing context.
57-
* **Suggestion pinning**. Pin suggestions inside a conversation to revisit them during your investigation.
57+
* **Suggestion pinning**. Pin suggestions inside a conversation to revisit them later.
5858

5959
## FAQ
6060

0 commit comments

Comments
 (0)