Dashboard doc fix (#264)

DebashisBorgohainO2 · web-flow · commit 8296efe0fefe · 2025-11-18T19:56:13.000+05:30
* doc fix: streams docs and custom charts docs

* update pipelines pages, alert history, custom chart for metrics using promql doc

* doc fix: formatting and 404 fixes
diff --git a/docs/images/import-pipelines.png b/docs/images/import-pipelines.png
diff --git a/docs/images/scheduled-pipeline-config-delay.png b/docs/images/scheduled-pipeline-config-delay.png
diff --git a/docs/user-guide/pipelines/configurable-delay-in-scheduled-pipelines.md b/docs/user-guide/pipelines/configurable-delay-in-scheduled-pipelines.md
@@ -3,41 +3,40 @@ description: >-
   Delay scheduled pipeline execution in OpenObserve to ensure data completeness
   by waiting minutes after the trigger time before processing data.
 ---
-
-This guide explains how to use the configurable delay feature for [scheduled pipelines](../use-pipelines/).
+This guide explains how to use the configurable delay feature for [scheduled pipelines](../pipelines/create-and-use-scheduled-pipeline/).
 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
+## How to configure delay
 
 When editing the **Associate Query** page:
 
-1. In the **Set Variables** section, configure:  
-
-    - **Frequency**: How often the pipeline should run.  
-    - **Period**: The data window the pipeline should process.  
-    - **Delay**: How many minutes to wait after the scheduled time before running the pipeline.
+1. In the **Set Variables** section, add **Delay**. Delay defines how many minutes the system waits after the scheduled trigger time. The pipeline runs only after this waiting period completes.
 ![configurable-delay](../../images/scheduled-pipeline-config-delay.png)
 
 2. Select **Validate and Close**.
 
-**Note**: Since Delay is a required field when setting up a scheduled pipeline, enter 0 minutes if you want the pipeline to run exactly at the scheduled time without any delay.
+!!! note "Note"
+    Since Delay is a required field when setting up a scheduled pipeline, enter 0 minutes if you want the pipeline to run exactly at the scheduled time without any delay.
 
-**Example**
+!!! note "Example"
 
-If the pipeline is configured with the following settings:
+    If the pipeline is configured with the following settings:
 
-- Frequency: 5 minutes  
-- Period: 5 minutes  
-- Delay: 2 minutes
+    - Frequency: 5 minutes  
+    - Period: 5 minutes  
+    - Delay: 2 minutes
 
-**Behavior:** The pipeline is scheduled every 5 minutes and runs 2 minutes after each scheduled time, processing data from the previous 5-minute window.  
-At 10:00 AM (scheduled time), the pipeline executes at 10:02 AM, processing data from 9:55 AM to 10:00 AM.
+    **Behavior:** The pipeline is scheduled every 5 minutes and runs 2 minutes after each scheduled time, processing data from the previous 5-minute window.  
+    At 10:00 AM (scheduled time), the pipeline executes at 10:02 AM, processing data from 9:55 AM to 10:00 AM.
 
-**Note**
+    **Note**
 
-- **Works with Cron**: Delay also applies when using cron-based schedules.  
-- **Data Window Unchanged**: Delay only affects when execution starts. It does not change the data range.
+    - **Works with Cron**: Delay also applies when using cron-based schedules.  
+    - **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](../use-pipelines/).  
+## Related links
+- [Pipelines in OpenObserve](../pipelines/pipelines/)
+- [Create and Use Real-time Pipeline](../pipelines/create-and-use-real-time-pipeline/)
+- [Create and Use Scheduled Pipeline](../pipelines/create-and-use-scheduled-pipeline/)
+- [Manage Pipelines](../pipelines/manage-pipelines/)
 
diff --git a/docs/user-guide/pipelines/create-and-use-real-time-pipeline.md b/docs/user-guide/pipelines/create-and-use-real-time-pipeline.md
@@ -153,7 +153,7 @@ Use this guide to create and run real-time pipelines. Real-time pipelines proces
 
 ## Related links
 - [Pipelines in OpenObserve](../pipelines/pipelines/)
-- [Create and Use Scheduled Pipeline](create-and-use-scheduled-pipeline.md)
+- [Create and Use Scheduled Pipeline](../pipelines/create-and-use-scheduled-pipeline/)
 - [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/create-and-use-scheduled-pipeline.md b/docs/user-guide/pipelines/create-and-use-scheduled-pipeline.md
@@ -9,7 +9,7 @@ Use this guide to create and run scheduled pipelines. Scheduled pipelines run at
 ## Steps to create a scheduled pipeline
 
 ??? "Step 1: Open the pipeline editor"
-### Step 1: Open the pipeline editor
+    ### Step 1: Open the pipeline editor
     1. Log in to OpenObserve.
     2. In the left navigation panel, select **Pipelines**. By default, the system opens the **Pipelines** tab. 
     ![Pipelines tab](../../images/pipelines-tab.png)
@@ -24,25 +24,25 @@ Use this guide to create and run scheduled pipelines. Scheduled pipelines run at
     Scheduled pipelines do not use a **Stream** node as the source. They always begin with a **Query** node.
 
     1. From the **Source** section, drag the **Query** node into the editor.  
-    2. The **Associate Query** panel opens. The panel contains two sections, Build Query and Set Variables. 
+    2. The **Associate Query** panel opens. The panel contains the following sections, **Build Query**, **SQL Query** editor, **Output**, **Set Variables**. 
     ![Associate Query](../../images/associate-query.png) 
     3. In the **Build Query** section: 
 
         1. Select the **Stream Type**.  
         2. Select the **Stream Name**.  
-    4. Edit or write your SQL query in the SQL editor.  
+    4. Edit or write your SQL query in the **SQL query** editor.  
     5. Select the time range from the time range selector at the top-right corner. 
     5. Click **Run query** to preview data in the **Output** panel.  
-   ![output-preview](../../images/query-output.png)
+    ![output-preview](../../images/query-output.png)
     6. In the **Set Variables** section configures how the pipeline runs using the following settings: 
 
         - **Enable Cron**: Switch from interval-based scheduling to cron-based scheduling.  
         - **Frequency**: How often the pipeline runs.  
         - **Period**: The data window to process. Period must equal Frequency.  
         - **Delay**: How many minutes the pipeline waits after the scheduled time before execution. 
         
-        > Visit the [Pipelines overview](https://openobserve.ai/docs/user-guide/pipelines/pipelines/) page to learn more about frequency, period, and cron.
-        > Learn more about [Configurable Delay in Scheduled Pipelines](https://openobserve.ai/docs/user-guide/pipelines/configurable-delay-in-scheduled-pipelines/).
+        > See the [Pipelines overview](https://openobserve.ai/docs/user-guide/pipelines/pipelines/) page to learn more about frequency, period, and cron.
+        > See the [Configurable Delay in Scheduled Pipelines](https://openobserve.ai/docs/user-guide/pipelines/configurable-delay-in-scheduled-pipelines/) page to learn how to configure delay in scheduled-pipelines.
 
         ![variables](../../images/scheduled-variables.png)
 
@@ -60,10 +60,6 @@ Use this guide to create and run scheduled pipelines. Scheduled pipelines run at
         3. Enter a value in the **Value** input box.
         4. Add more conditions if needed.
 
-        !!! note "Important"
-            **Condition nodes require a stream schema.** <br>
-            If you create a new stream in **Step 3** and do not define any fields, the **Condition** editor does not display field names.
-            To use conditions, add at least one field while creating the source stream or ingest sample data so that the schema is inferred.
         !!! note "Guidelines"
             - Use an empty string to check for empty values. For example, `app_name != ""`
             - Use null to check for null values. For example, `app_name != null`
@@ -104,13 +100,13 @@ Use this guide to create and run scheduled pipelines. Scheduled pipelines run at
     2. In the **Associate Stream** panel, configure the destination stream.
     3. Select an existing stream or create a new one. Stream creation follows the same configuration as shown in Step 3.  
 
-        !!! note "Note"
-            - You can add **Enrichment_tables** as a destination stream for scheduled pipelines. 
-        
-        !!! note "Dynamic stream names"
-            You can configure the stream name dynamically with curly braces.  
-            Example: `static_text_{fieldname}_postfix`  
-            Static text before and after the braces is optional.
+    !!! note "Note"
+        You can add **Enrichment_tables** as a destination stream for scheduled pipelines. 
+    
+    !!! note "Dynamic stream names"
+        You can configure the stream name dynamically with curly braces.  
+        Example: `static_text_{fieldname}_postfix`  
+        Static text before and after the braces is optional.
 
 
     **To add an external destination:** 
@@ -133,7 +129,7 @@ Use this guide to create and run scheduled pipelines. Scheduled pipelines run at
     Click **Save**. The pipeline becomes active immediately.
     ![scheduled-pipeline-list-view](../../images/scheduled-pipeline-list-view.png)
 
-## Use the real-time pipeline
+## Use the scheduled pipeline
 
 ??? "Step 1: Ingest data"
     ### Step 1: Ingest data
@@ -152,7 +148,7 @@ Use this guide to create and run scheduled pipelines. Scheduled pipelines run at
 
 ## Related links
 - [Pipelines in OpenObserve](../pipelines/pipelines/)
-- [Create and Use Real-time Pipeline](../create-and-use-real-time-pipeline/)
+- [Create and Use Real-time Pipeline](../pipelines/create-and-use-real-time-pipeline/)
 - [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/import-and-export-pipelines.md b/docs/user-guide/pipelines/import-and-export-pipelines.md
@@ -16,14 +16,13 @@ To export an existing pipeline configuration:
 ![download-pipeline](../../images/download-pipeline-json.png)
 The downloaded `.json` file contains the pipeline configuration and can be used to import the pipeline into another environment.<br>
 
-For example, exporting the pipeline `scheduled-pipeline-demo` generates a JSON file similar to the following:  
-![json-file-pipeline-export](../../images/json-file-pipeline-export.png)
+!!! note "Example" 
+    Exporting the pipeline `scheduled-pipeline-demo` generates a JSON file similar to the following:"  
+    ![json-file-pipeline-export](../../images/json-file-pipeline-export.png)
 
 ## Import a pipeline
-
 To import a previously exported pipeline:
-![pipeline-import](../../images/pipeline-import.png)
-
+![alt text](../../images/import-pipelines.png)
 1. Go to **Pipelines**.  
 2. Click **Import Pipeline** in the top-right corner.<br>  
 3. Choose one of the supported import methods:  
@@ -32,7 +31,6 @@ To import a previously exported pipeline:
     - **Enter URL**: Provide a URL to fetch the pipeline configuration.  
     - **Paste JSON Object**: Copy and paste the JSON pipeline definition in the JSON editor.
 
-![import methods](pipeline-import-json.png) 
 4. To import pipelines in bulk, choose multiple JSON files. 
 5. Click **Import**. 
 The imported pipeline appears in the **Pipelines** tab.
@@ -53,9 +51,9 @@ If any validation errors occur during import, refer to the following resolutions
 - **Remote Destination does not exist:** Ensure the remote destination is accurate. 
 
 
-## Related Links
+## Related links
 - [Pipelines in OpenObserve](../pipelines/pipelines/)
-- [Create and Use Real-time Pipeline](../create-and-use-real-time-pipeline/)
-- [Create and Use Scheduled Pipeline](create-and-use-scheduled-pipeline.md)
+- [Create and Use Real-time Pipeline](../pipelines/create-and-use-real-time-pipeline/)
+- [Create and Use Scheduled Pipeline](../pipelines/create-and-use-scheduled-pipeline/)
 - [Manage Pipelines](../pipelines/manage-pipelines/)
 - [Configurable Delay in Scheduled Pipelines](../pipelines/configurable-delay-in-scheduled-pipelines/)
diff --git a/docs/user-guide/pipelines/index.md b/docs/user-guide/pipelines/index.md
@@ -3,8 +3,8 @@ In OpenObserve, pipelines are data processing workflows used to transform logs,
 **Learn more:**
 
 - [Pipelines in OpenObserve](../pipelines/pipelines/)
-- [Create and Use Real-time Pipeline](../create-and-use-real-time-pipeline/)
-- [Create and Use Scheduled Pipeline](create-and-use-scheduled-pipeline.md)
+- [Create and Use Real-time Pipeline](../pipelines/create-and-use-real-time-pipeline/)
+- [Create and Use Scheduled Pipeline](../pipelines/create-and-use-scheduled-pipeline/)
 - [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
@@ -36,7 +36,7 @@ Each pipeline row includes the following actions.
 
 ### Pause and resume pipelines
 
-You can pause both real-time and scheduled pipelines.
+You can pause both real-time and scheduled pipelines. <br>
 
 **Pausing a pipeline:**
 
@@ -74,9 +74,9 @@ Scheduled pipelines display a Resume Pipeline Ingestion dialog with two options.
 
 ### Pipeline error
 If a pipeline encounters an error, an error icon appears in the **Actions** column.
-![pipeline-error](pipeline-error.png)
+![pipeline-error](../../images/pipeline-error.png)
 Selecting this icon opens a dialog that displays the full error summary.
-![pipeline-error-view](pipeline-error-view.png)
+![pipeline-error-view](../../images/pipeline-error-view.png)
 
 ## Pipeline history
 You can view past executions, errors, and performance statistics in the Pipeline History page.
@@ -88,7 +88,7 @@ You can export any pipeline and import pipeline configurations through the Impor
 
 ## Related links
 - [Pipelines in OpenObserve](../pipelines/pipelines/)
-- [Create and Use Real-time Pipeline](../create-and-use-real-time-pipeline/)
-- [Create and Use Scheduled Pipeline](create-and-use-scheduled-pipeline.md)
+- [Create and Use Real-time Pipeline](../pipelines/create-and-use-real-time-pipeline/)
+- [Create and Use Scheduled Pipeline](../pipelines/create-and-use-scheduled-pipeline/)
 - [Import and Export Pipelines](../pipelines/import-and-export-pipelines/)
 - [Configurable Delay in Scheduled Pipelines](../pipelines/configurable-delay-in-scheduled-pipelines/)
