to fix the pipelines folder issue

DebashisBorgohainO2 · DebashisBorgohainO2 · commit 52554121e84a · 2025-07-08T13:28:04.000+05:30
diff --git a/docs/user-guide/pipelines/.pages b/docs/user-guide/pipelines/.pages
@@ -1,7 +1,7 @@
 nav:
     - Pipelines Overview: index.md
-    - Pipelines in OpenObserve: pipelines-in-openobserve.md
-    - Create and Use Pipelines: create-and-use-pipelines.md
+    - Pipelines in OpenObserve: pipelines.md
+    - Create and Use Pipelines: use-pipelines.md
     - Import and Export Pipelines: import-and-export-pipelines.md
     - Manage Pipelines: manage-pipelines.md
     - Configurable Delay in Scheduled Pipelines: configurable-delay-in-scheduled-pipelines.md
diff --git a/docs/user-guide/pipelines/configurable-delay-in-scheduled-pipelines.md b/docs/user-guide/pipelines/configurable-delay-in-scheduled-pipelines.md
@@ -1,5 +1,5 @@
 
-This guide explains how to use the configurable delay feature for [scheduled pipelines](../create-and-use-pipelines/).
+This guide explains how to use the configurable delay feature for [scheduled pipelines](../use-pipelines/).
 This feature allows you to delay the execution of a scheduled pipeline by a set number of minutes after its scheduled start time. This is useful to ensure data completeness and accommodate late-arriving events before the pipeline runs.
 
 ## How to Configure Delay
@@ -34,5 +34,5 @@ At 10:00 AM (scheduled time), the pipeline executes at 10:02 AM, processing data
 - **Data Window Unchanged**: Delay only affects when execution starts. It does not change the data range.
 
 **Related Links**<br>
-For steps on creating scheduled pipelines, see [Scheduled Pipelines](../create-and-use-pipelines/).  
+For steps on creating scheduled pipelines, see [Scheduled Pipelines](../use-pipelines/).  
 
diff --git a/docs/user-guide/pipelines/import-and-export-pipelines.md b/docs/user-guide/pipelines/import-and-export-pipelines.md
diff --git a/docs/user-guide/pipelines/index.md b/docs/user-guide/pipelines/index.md
@@ -2,8 +2,8 @@ In OpenObserve, pipelines are data processing workflows used to transform logs,
 
 **Learn more:**
 
-- [Pipelines in OpenObserve](../pipelines/pipelines-in-openobserve/)
-- [Create and Use Pipelines](../pipelines/create-and-use-pipelines/)
+- [Pipelines in OpenObserve](../pipelines/pipelines/)
+- [Create and Use Pipelines](../pipelines/use-pipelines/)
 - [Import and Export Pipelines](../pipelines/import-and-export-pipelines/)
 - [Manage Pipelines](../pipelines/manage-pipelines/)
 - [Configurable Delay in Scheduled Pipelines](../pipelines/configurable-delay-in-scheduled-pipelines/)
diff --git a/docs/user-guide/pipelines/manage-pipelines.md b/docs/user-guide/pipelines/manage-pipelines.md
diff --git a/docs/user-guide/pipelines/pipelines.md b/docs/user-guide/pipelines/pipelines.md
@@ -76,5 +76,5 @@ To configure an external destination for pipelines:
 
 
 ## Next Steps
-- [Create and Use Pipelines](create-and-use-pipelines.md)
-- [Manage Pipelines](manage-pipelines.md)
+- [Create and Use Pipelines](../use-pipelines/)
+- [Manage Pipelines](../manage-pipelines/)
diff --git a/docs/user-guide/pipelines/use-pipelines.md b/docs/user-guide/pipelines/use-pipelines.md
@@ -30,7 +30,7 @@ This opens up the pipeline editor.
         - In the **Build Query** section, select the **Stream Type** (Logs, Metrics, or Traces) and **Stream Name**. Use the seach bar to search for the desired field in the source stream. 
         - In the **SQL Query** section, write a query to fetch data from a source. For **Metrics**, you also have the option to write **PromQL**.
         ![scheduled pipeline](../../images/create-pipeline-sch-query.png)
-        - Under **Set Variables**, schedule the query execution by setting the **Frequency** and **Period**. For more details, visit [Pipelines in OpenObserve](../pipelines-in-openobserve/).
+        - Under **Set Variables**, schedule the query execution by setting the **Frequency** and **Period**. For more details, visit [Pipelines in OpenObserve](../pipelines/).
         - Adjust the time filter and click **Run Query** to view the output.
         ![scheduled pipeline](../../images/create-pipeline-sch-output.png) 
         <br>In the above example, data is ingested periodically into the stream `default`. The query runs every 6 minutes and fetches all data that was ingested into the stream `default` in the preceding 6-minute interval.
