Merge pull request #189 from runreveal/docs-logs-pipelines-updates

Docs logs pipelines updates

Author: jonathanmcintyre1

next

@@ -35,6 +35,61 @@ export default withYAML(withNextra({
         destination: '/detections/writing-detections',
         permanent: true,
       },
+      {
+        source: '/pipelines',
+        destination: '/logs/log-processing/getting-started',
+        permanent: true,
+      },
+      {
+        source: '/pipelines/:path*',
+        destination: '/logs/log-processing/getting-started',
+        permanent: true,
+      },
+      {
+        source: '/logs/pipelines',
+        destination: '/logs/log-processing/getting-started',
+        permanent: true,
+      },
+      {
+        source: '/logs/pipelines/:path*',
+        destination: '/logs/log-processing/getting-started',
+        permanent: true,
+      },
+      {
+        source: '/transforms',
+        destination: '/logs/log-processing/transforms',
+        permanent: true,
+      },
+      {
+        source: '/logs/transforms',
+        destination: '/logs/log-processing/transforms',
+        permanent: true,
+      },
+      {
+        source: '/custom-views',
+        destination: '/logs/custom-views',
+        permanent: true,
+      },
+      {
+        source: '/filtering',
+        destination: '/logs/log-processing/filtering',
+        permanent: true,
+      },
+      {
+        source: '/logs/filtering',
+        destination: '/logs/log-processing/filtering',
+        permanent: true,
+      },
+      {
+        source: '/enrichments',
+        destination: '/logs/log-processing/enrichments',
+        permanent: true,
+      },
+      {
+        source: '/enrichments/:path*',
+        destination: '/logs/log-processing/enrichments/:path*',
+        permanent: true,
+      },
     ]
   },
 }))

next.config.mjs

@@ -8,13 +8,9 @@ export default {
   },
   "how-to-guides": "How To Guides",
   "ai-chat": "AI Chat",
-  "pipelines": "Pipelines",
+  "logs": "Log Management",
   "sources": "Sources",
-  "transforms": "Transforms",
-  "custom-views": "Custom Views",
-  "filtering": "Filtering",
   "detections": "Detections",
-  "enrichments": "Enrichments",
   "notifications": "Notifications",
   "integrations": "Integrations",
   "dashboards": "Dashboards & Graphs",

nextra-docs-template@0.0.1

@@ -283,7 +283,7 @@ Native AI Chat uses a structured approach to investigations:
 - Ask for explanations: "Why did this detection fire?"
 - Request recommendations: "What should I investigate next?" 
 
-## Helpful Resources
+## Related Documentation
 
 Now that you've set up your chat settings, explore these related guides:
 

pages/_meta.ts

@@ -459,7 +459,7 @@ This pattern is useful for detecting:
 3. Multiple signals for same user → Create alert (with notifications)
 4. Incident response team investigates → Take action based on alert context
 
-## Helpful Resources
+## Related Documentation
 
 Now that you understand how to write effective detections, explore these related guides:
 

pages/ai-chat/native-ai-chat.mdx

@@ -272,7 +272,7 @@ The AI will analyze your GitHub logs and suggest detections for high-priority MI
 
 **Note:** The suggested detections may need some tweaking and can be tested on the detections creation page or explore tab, but they provide a solid starting point when you're looking to add coverage for specific sources and MITRE tactics.
 
-## Helpful Resources
+## Related Documentation
 
 Now that you understand how to write effective detections, explore these related guides:
 

pages/detections.mdx

@@ -413,7 +413,7 @@ Now that you have detections, signals, and alerts set up, explore the detailed c
 - **[Sigma Streaming](/detections/sigma-streaming)** - Use Sigma rules for standardized threat detection
 - **[Detection as Code](/detections/detection-as-code)** - Manage detections through code and version control
 - **[Sources](/sources)** - Set up data collection from your systems
-- **[Pipelines](/pipelines)** - Configure data processing workflows
+- **[Pipelines](/logs/log-processing/getting-started)** - Configure data processing workflows
 - **[Notifications Getting Started](/notifications/getting-started)** - Set up alerting and notification channels
 - **[AI Chat](/ai-chat)** - Use AI-powered analysis for threat hunting and investigation
-- **[Enrichments](/enrichments)** - Add context and metadata to your security events
+- **[Enrichments](/logs/log-processing/enrichments)** - Add context and metadata to your security events

pages/detections/writing-detections.mdx

@@ -114,7 +114,7 @@ export default function RunRevealIntroduction() {
       ...colorPatterns[1] // Purple
     },
     {
-      href: "/pipelines/getting-started",
+      href: "/logs/pipelines/getting-started",
       icon: "/icons/rows.svg",
       title: "Pipelines",
       description: "Build and manage data processing pipelines.",
@@ -128,14 +128,14 @@ export default function RunRevealIntroduction() {
       ...colorPatterns[3] // Yellow
     },
     {
-      href: "/transforms",
+      href: "/logs/log-processing/transforms",
       icon: "/icons/Edit.svg",
       title: "Transforms",
       description: "Normalize data for consistent queries and dashboards.",
       ...colorPatterns[4] // Pink
     },
     {
-      href: "/filtering",
+      href: "/logs/log-processing/filtering",
       icon: "/icons/DataSort.svg",
       title: "Filtering",
       description: "Powerful querying and sampling for noisy streams.",
@@ -149,7 +149,7 @@ export default function RunRevealIntroduction() {
       ...colorPatterns[0] // Blue (cycle back)
     },
     {
-      href: "/enrichments",
+      href: "/logs/log-processing/enrichments",
       icon: "/icons/stars.svg",
       title: "Enrichments",
       description: "Add context and metadata to every event.",

pages/how-to-guides/detections-signals-alerts-quick-start.mdx

@@ -0,0 +1,6 @@
+export default {
+  "search": "Explore Logs",
+  "log-processing": "Log Processing",
+  "custom-views": "Custom Views"
+}
+