Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
4 changes: 2 additions & 2 deletions .claude/commands/audit-doc.md
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,7 @@ Apply Sumo Logic style guide rules:

**Terminology:**
* [ ] "Sumo Logic" (not "SumoLogic" or "Sumo")
* [ ] Consistent product names (Cloud SIEM, Cloud SOAR)
* [ ] Consistent product names (SIEM, Cloud SOAR)
* [ ] Proper capitalization for features and products
* [ ] No contractions in formal documentation

Expand Down Expand Up @@ -259,7 +259,7 @@ After presenting the audit report, ask the user if they would like Claude to:

**By type:**

**Cloud SIEM (CSE):**
**SIEM (CSE):**
* Date format with ordinal suffix (12th, 3rd)
* Rule IDs follow pattern (MATCH-SXXXX, etc.)
* Parser paths use full hierarchy
Expand Down
2 changes: 1 addition & 1 deletion .claude/commands/doc-from-jira.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ Use the technical area and doc type to suggest the most likely file path.
| APM | `docs/apm/` |
| Apps/Integrations | `docs/integrations/` |
| Automation | `docs/platform-services/automation-service/` |
| Cloud SIEM | `docs/cse/` |
| SIEM | `docs/cse/` |
| Cloud SOAR | `docs/cloud-soar/` |
| Collectors/Sources | `docs/send-data/` |
| Dashboards | `docs/dashboards/` |
Expand Down
2 changes: 1 addition & 1 deletion .claude/commands/doc.md
Original file line number Diff line number Diff line change
Expand Up @@ -428,7 +428,7 @@ Claude:
* `/docs/api/` — API reference documentation.
* `/docs/apm/` — Application Performance Monitoring and tracing.
* `/docs/cloud-soar/` — Cloud SOAR documentation.
* `/docs/cse/` — Cloud SIEM documentation.
* `/docs/cse/` — SIEM documentation.
* `/docs/dashboards/` — Dashboard and visualization docs.
* `/docs/get-started/` — Getting started guides and onboarding.
* `/docs/integrations/` — Third-party integrations (use specialized commands).
Expand Down
2 changes: 1 addition & 1 deletion .claude/commands/geo-optimize.md
Original file line number Diff line number Diff line change
Expand Up @@ -204,7 +204,7 @@ After the first use, the abbreviation alone is fine. Define the term once at its

* **Code blocks** — never alter code, commands, or configuration values
* **Step-by-step instructions** — do not reorder or reword steps; only improve surrounding prose
* **Product names and proper nouns** — do not rephrase "Cloud SIEM" or "Hosted Collector"
* **Product names and proper nouns** — do not rephrase "SIEM" or "Hosted Collector"
* **Warnings, notes, and admonitions** — these are already structured for extraction; leave them
* **Tables** — do not convert tables to prose; they are already GEO-friendly

Expand Down
6 changes: 3 additions & 3 deletions .claude/commands/jira.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Use this list to select the correct Technical Area when creating or updating tic
- APM (Traces, RUM)
- Apps/Integrations
- Automation
- Cloud SIEM
- SIEM
- Cloud SOAR
- Collectors/Sources
- Dashboards
Expand Down Expand Up @@ -77,7 +77,7 @@ Use these keywords and file path patterns to suggest the most relevant Technical
- **APM**: trace, span, RUM, real user monitoring, application performance
- **Apps/Integrations**: app, integration, connector, third-party
- **Automation**: automation, playbook, workflow, orchestration
- **Cloud SIEM**: SIEM, security, threat, detection, rule
- **SIEM**: SIEM, security, threat, detection, rule
- **Cloud SOAR**: SOAR, incident response, security orchestration
- **Collectors/Sources**: collector, source, ingestion, data collection
- **Dashboards**: dashboard, panel, visualization, chart
Expand All @@ -101,7 +101,7 @@ Use these keywords and file path patterns to suggest the most relevant Technical
- **/apm/**, **/traces/**, **/real-user-monitoring/** → APM (Traces, RUM)
- **/integrations/**, **/apps/** → Apps/Integrations
- **/automation-service/** → Automation
- **/cse/**, **/cloud-siem/** → Cloud SIEM
- **/cse/**, **/siem/** → SIEM
- **/csoar/**, **/cloud-soar/** → Cloud SOAR
- **/send-data/**, **/collectors/** → Collectors/Sources
- **/dashboards/** → Dashboards
Expand Down
28 changes: 14 additions & 14 deletions .claude/commands/release-note-cse.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Create New Cloud SIEM Release Note
# Create New SIEM Release Note

Automates the creation of Cloud SIEM (CSE) release notes with proper formatting, frontmatter, and structure.
Automates the creation of SIEM (CSE) release notes with proper formatting, frontmatter, and structure.

## What this command does

Expand All @@ -14,16 +14,16 @@ When you invoke `release-note-cse`, Claude will guide you through:

## When to use this command

* Publishing Cloud SIEM content updates (rules, log mappers, parsers).
* Announcing new Cloud SIEM features or bug fixes.
* Publishing SIEM content updates (rules, log mappers, parsers).
* Announcing new SIEM features or bug fixes.
* Creating regular bi-weekly or monthly CSE release notes.
* Documenting Cloud SIEM application updates.
* Documenting SIEM application updates.

## Release types

### Content Release (`-content.md`)

For updates to Cloud SIEM detection content:
For updates to SIEM detection content:
* **Rules**: New or updated detection rules
* **Log Mappers**: New or updated log mapping configurations
* **Parsers**: Parser updates and enhancements
Expand All @@ -33,7 +33,7 @@ For updates to Cloud SIEM detection content:

### Application Release (`-application.md`)

For Cloud SIEM product features and updates:
For SIEM product features and updates:
* **New features**: UI improvements, new capabilities
* **Bug fixes**: Issue resolutions
* **Performance improvements**: Optimizations
Expand Down Expand Up @@ -117,7 +117,7 @@ hide_table_of_contents: true
* **Always ask user to confirm keywords before creating file**
* Suggested defaults:
* Content releases: `rules`, `log mappers`, `parsers`
* Application releases: Feature-specific keywords (e.g., `insights`, `entities`, `signals`, `cloud siem`)
* Application releases: Feature-specific keywords (e.g., `insights`, `entities`, `signals`, `siem`)
* User may want to add or modify keywords based on specific content

**Date formatting:**
Expand Down Expand Up @@ -303,14 +303,14 @@ Use standard vendor names:
**Archive structure:**
```markdown
---
title: {Year} Release Notes Archive - Cloud SIEM
keywords: [rules, signals, schema, log mappers, parsers, cloud siem]
title: {Year} Release Notes Archive - SIEM
keywords: [rules, signals, schema, log mappers, parsers, siem]
image: https://assets-www.sumologic.com/company-logos/_800x418_crop_center-center_82_none/SumoLogic_Preview_600x600.jpg?mtime=1617040082
---

import useBaseUrl from '@docusaurus/useBaseUrl';

This is an archive of {Year} Cloud SIEM release notes. [View the full archive](/release-notes-cse/archive).
This is an archive of {Year} SIEM release notes. [View the full archive](/release-notes-cse/archive).

<!--truncate-->

Expand Down Expand Up @@ -339,7 +339,7 @@ This is an archive of {Year} Cloud SIEM release notes. [View the full archive](/
After successfully creating the release note, tell the user:

```
Cloud SIEM release note created successfully!
✅ SIEM release note created successfully!

File created:
* 📄 blog-cse/{date}-{type}.md.
Expand All @@ -365,7 +365,7 @@ Checklist:
* [ ] Links tested and working.
* [ ] No placeholder text remaining.

The release note will appear on the Cloud SIEM release notes page in reverse chronological order (newest first).
The release note will appear on the SIEM release notes page in reverse chronological order (newest first).

Would you like me to help fill in any additional details?
```
Expand Down Expand Up @@ -414,6 +414,6 @@ Would you like me to help fill in any additional details?

## References

* [Cloud SIEM Release Notes](https://sumologic.com/help/release-notes-cse)
* [SIEM Release Notes](https://sumologic.com/help/release-notes-cse)
* [Release Notes Index](/docs/release-notes).
* [Style Guide](/docs/contributing/style-guide).
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
[![Node.js >=20](https://img.shields.io/static/v1?label=Node.js&message=%3E%3D20&color=339933&style=flat&logo=nodedotjs&logoColor=white)](https://nodejs.org)
[![Yarn v1](https://img.shields.io/static/v1?label=Yarn&message=v1&color=2C8EBB&style=flat&logo=yarn&logoColor=white)](https://yarnpkg.com)

Sumo Logic Docs is the open-source documentation site for Sumo Logic, an AI-powered security operations platform providing Cloud SIEM and security analytics to help teams automate, detect, and investigate threats. Sumo Logic empowers users to monitor, troubleshoot, and defend their environments using AI insights powered by log analytics. Learn more at [sumologic.com](https://www.sumologic.com).
Sumo Logic Docs is the open-source documentation site for Sumo Logic, an AI-powered security operations platform providing SIEM and security analytics to help teams automate, detect, and investigate threats. Sumo Logic empowers users to monitor, troubleshoot, and defend their environments using AI insights powered by log analytics. Learn more at [sumologic.com](https://www.sumologic.com).

Our site is built with [Docusaurus 3](https://docusaurus.io/) and supports React, Rehype, and Remark plugins.

Expand Down Expand Up @@ -62,7 +62,7 @@ Any broken links or images will be listed in the output. Fix them, rebuild, and
| `/docs` | Documentation source files |
| `/blog-service` | Service release notes |
| `/blog-collector` | Collector release notes |
| `/blog-cse` | Cloud SIEM release notes |
| `/blog-cse` | SIEM release notes |
| `/blog-csoar` | Cloud SOAR release notes |
| `/static/img` | Images and media assets |
| `sidebars.ts` | Left-nav sidebar configuration |
Expand Down
Loading
Loading