update docs

Author: DebashisBorgohainO2

docs/.pages

@@ -5,7 +5,7 @@ nav:
 - Enterprise Edition Installation: openobserve-enterprise-edition-installation-guide.md
 - Releases: releases.md
 - Example Queries: example-queries.md
-- SQL SQL Function Reference: sql_reference.md
+- SQL Function Reference: sql_reference.md
 - Architecture: architecture.md
 - HA Deployment: ha_deployment.md
 - Environment Variables: environment-variables.md

docs/data-management/storage.md

@@ -10,7 +10,7 @@ By default:
 
 - Metadata is always stored on disk using **SQLite** in **Local mode**.
 - Metadata is always stored on disk using **postgres** in **Cluster mode**.
-- Stream data can be stored on disk or S3-compatible object storage such as Amazon S3, minIO, Google GCS, Alibaba OSS, or Tencent COS.
+- Stream data can be stored on disk or object storage such as Amazon S3, minIO, Google GCS, Alibaba OSS, or Tencent COS.
 
 ## Storage Modes
 

docs/openobserve-enterprise-edition-installation-guide.md

@@ -1,6 +1,8 @@
+## Deploy OpenObserve Enterprise Edition as a Highly Available (HA) installation using Helm.
+
 This guide explains how to deploy [OpenObserve Enterprise Edition](https://openobserve.ai/downloads/)  in a **Kubernetes** environment using **Helm**. 
 
-> These instructions use Amazon EKS and S3 for demonstration, but the deployment works with any Kubernetes platform such as GKE or AKS, and other S3-compatible storage services such as Azure Blob, MinIO, or GCS.
+> These instructions use Amazon EKS and S3 for demonstration, but the deployment works with any Kubernetes environment, such as GKE or AKS, and other object storage services such as Azure Blob, MinIO, or GCS.
 
 > For support, reach out in the [Slack channel](https://short.openobserve.ai/community).
 
@@ -13,7 +15,7 @@ This guide explains how to deploy [OpenObserve Enterprise Edition](https://openo
     - **Dex and OpenFGA** enable Single Sign-On (SSO) and Role-Based Access Control (RBAC).
 
 
-## Installation Steps
+### Installation Steps
 Follow these steps to install OpenObserve Enterprise Edition:
 
 
@@ -158,10 +160,9 @@ Follow these steps to install OpenObserve Enterprise Edition:
     helm --namespace openobserve -f values.yaml install o2 openobserve/openobserve
     ```
 
-    **After installation, Helm will output a kubectl port-forward command. Run the command and open http://localhost:<port>/ in your browser.**
-
-    **Installation complete**
-    OpenObserve is now running in your Kubernetes cluster. You can log in using the root user credentials and begin configuring data streams, dashboards, and alerting.
-
+  After installation, the output displays a `kubectl port-forward` command. Run that command and then open `http://localhost:<port>` in your browser, replacing `<port>` with the actual port number shown.
 
+  OpenObserve is now running in your Kubernetes cluster. Log in using the root user credentials configured in Step 5 to start using OpenObserve.
 
+!!! info "Note"
+    OpenObserve also provides an Infrastructure as Code (IAC) workflow using [Terraform](https://www.terraform.io/downloads.html) or [OpenTofu](https://opentofu.org/docs/intro/install/). This streamlines the deployment of Amazon Elastic Kubernetes Service (EKS) and OpenObserve in HA mode. It enables teams to quickly provision and manage OpenObserve infrastructure in Amazon EKS using prebuilt, flexible modules. To explore this option, visit the [openobserve-eks-iac repository](https://github.com/openobserve/openobserve-eks-iac).

docs/sql_reference.md

@@ -1,18 +1,33 @@
-# Functions
+This guide describes the custom SQL functions supported in OpenObserve for querying and processing logs and time series data. These functions extend the capabilities of standard SQL by enabling full-text search, array processing, and time-based aggregations.
 
-## FUll text search functions
+## Full-text Search Functions
+These functions allow you to filter records based on keyword or pattern matches within one or more fields.
 
-### str_match(field, 'v')
+### `match_field(field, 'value')`
+**Alias for**: `str_match(field, 'v')` <br>
+**Description**: <br>
+Filters logs by matching the exact string value within the specified field. The match is case-sensitive. <br>
+**Example**:
+```sql
+SELECT * FROM logs WHERE match_field("status", 'Success')
+```
+This filters logs where the status field contains the string 'Success'. It does not match 'success' or 'SUCCESS'.
 
-filter the keyword in the field.
+### `match_field_ignore_case(field, 'value')`
+**Alias for**: `str_match_ignore_case` <br>
+**Description**: <br>
+Filters logs by matching the string value within the specified field, ignoring case. The match is case-insensitive. <br>
+**Example**:
+```sql
+SELECT * FROM logs WHERE match_field_ignore_case("status", 'success')
+```
+This matches logs where the status field contains 'success', 'Success', 'SUCCESS', or any other casing variation.
 
-### str_match_ignore_case(field, 'v')
 
-filter the keyword in the field with case_insensitive. it can match `KeyWord` or `keyWord`.
 
 ### match_all('v')
-
-filter the keyword in the fields, whose **Index Type** is set to `Full text search` in streams settings. To utilize Inverted Index, you must set environment variable `ZO_ENABLE_INVERTED_INDEX` to `true` first,
+**Description**: <br>
+Filters the keyword in the fields, whose **Index Type** is set to `Full text search` in streams settings. To utilize Inverted Index, you must set environment variable `ZO_ENABLE_INVERTED_INDEX` to `true` first,
 then you can specify Index Type for one or multiple fields (e.g. `body`, `message`) to `Inverted Index` by going to stream settings.
 
 > We have default fields: `log`, `message`, `msg`, `content`, `data`, `json`. you can set the full text search fields in the UI or through `index.setting` API.

docs/user-guide/dashboards/manage-dashboards.md

@@ -71,5 +71,3 @@ In the Tabs section, you can add, edit, and delete Tabs within the Dashboard.
 ![tabs](../../images/dashboard-manage-5.png)
 
 
-FAQs
-Q: Why does my dashboard chart say "No data"?

docs/user-guide/dashboards/panels/panel-management.md

@@ -1,7 +1,5 @@
 This guide explains how to use and manage panels in the dashboard. It includes features available in the panel toolbar, step-by-step instructions, and troubleshooting tips for common issues.
 
-## Panel Toolbar Features
-
 The panel toolbar offers the following controls to adjust, organize, and customize your panels:
 
 ## Viewing and Refresh Controls  
@@ -14,6 +12,17 @@ Maximizes the panel to cover the entire display, providing an expanded view. <br
 - To expand the view, click the **Full Screen Mode** button in the panel toolbar.  
 - To exit **Full Screen Mode**, press **Escape** on your keyboard. 
 
+### Information Icon
+The information icon on panel shows the description of the panel. <br>  
+![Panel Description](../../../images/manage-panels-panel-description.png)  
+
+**To add, edit, or remove a panel description:**
+
+1. In the panel toolbar, open the dropdown menu and select **Edit Panel**.  
+2. On the right side of the screen, select the **Config** tab.  
+3. Under **Description**, enter, update, or delete the panel description as needed.  
+4. Select **Apply** to save your changes.
+
 ### Last Refreshed At  
 Displays the timestamp of when the panel’s data was last updated. <br> 
 **How to Use:** Hover over the timestamp icon to view the time when the panel was last refreshed. 
@@ -103,11 +112,9 @@ Allows you to add notes to selected data points or time ranges across multiple p
 
     - Use the dropdown menu to select panels. You can apply annotations across multiple panels based on your selection.    
     - If you do not select any panel, the annotation applies to all panels for the selected time range, within the dashboard by default.
-
-![Select Panels](../../../images/manage-panels-select-panels.png)
+    ![Select Panels](../../../images/manage-panels-select-panels.png)
 
 5. **Save Annotation.**
-
 ![Save Annotation](../../../images/manage-panels-save-annotations.png)
 
 
@@ -120,13 +127,3 @@ Allows you to add notes to selected data points or time ranges across multiple p
   ![Delete Annotations](../../../images/manage-panels-delete-annotations.png)
 
 
-!!! Note
-    Information icon on panel shows the description of the panel.   
-    ![Panel Description](../../../images/manage-panels-panel-description.png)  
-
-    **To add, edit, or remove a panel description:**
-
-    1. In the panel toolbar, open the dropdown menu and select **Edit Panel**.  
-    2. On the right side of the screen, select the **Config** tab.  
-    3. Under **Description**, enter, update, or delete the panel description as needed.  
-    4. Select **Apply** to save your changes.

docs/user-guide/identity-and-access-management/organizations.md

@@ -1,4 +1,4 @@
-This guide explains how organizations work in OpenObserve. It covers organization types, creation methods, identifiers, access control, and switching behavior. 
+This guide explains how organizations work in OpenObserve. It covers organization types, creation methods, identifiers, access control, and limitations. 
 
 ## Overview   
 Organizations provide logical boundaries for separating data, users, and access controls, enabling secure multi-tenant usage in a single OpenObserve deployment.

docs/user-guide/streams/extended-retention.md

@@ -1,6 +1,6 @@
 ## Extended Retention
 
-The Extended Retention feature in the Stream Details panel allows you to retain specific segments of your stream data beyond the configured stream-level or global retention period. 
+The Extended Retention feature in **Stream Details** allows you to retain specific segments of your stream data beyond the configured stream-level or global retention period. 
 
 ## When to Use Extended Retention
 
@@ -9,10 +9,11 @@ For example, logs from a known incident that occurred last month, you can config
 
 ## How to Apply Extended Retention
 
-1. Navigate to the **Stream Details** panel.  
-2. Select the **Extended Retention** tab.  
-3. Use the date selector to specify a time range in UTC. Click **Apply**.  
-4. Click **Update Settings** to apply the retention policy.
+1. From the **Streams** page, select the **Explore** icon from the **Actions** column. 
+2. Navigate to [**Stream Details**](../../user-guide/streams/stream-details.md/#access-the-stream-details).  
+3. Select the **Extended Retention** tab.  
+4. Use the date selector to specify a time range in UTC. Click **Apply**.  
+5. Click **Update Settings** to apply the retention policy.
 
 !!! Note  
     The data within the selected time range will be retained for an additional 3,650 days.

docs/user-guide/streams/schema-settings.md

@@ -1,4 +1,4 @@
-The **Schema Settings** tab in the [Stream Details](stream-details.md) panel allows you to inspect and manage the schema used to store and query ingested data. A schema defines the structure of log data in a stream, including:
+The **Schema Settings** tab in [Stream Details](stream-details.md) allows you to inspect and manage the schema used to store and query ingested data. A schema defines the structure of log data in a stream, including:
 
 - The fields present in the logs  
 - The detected data types for each field  

docs/user-guide/streams/stream-details.md

@@ -1,20 +1,18 @@
-After data [ingestion is complete](streams-in-openobserve.md/#ingest-data-into-stream), you can view detailed information about a stream using the **Stream Details** panel. 
-This guide explains how to access the **Stream Details** panel and the information available in the panel. 
+After After you complete [data ingestion](streams-in-openobserve.md/#ingest-data-into-stream), use **Stream Details** to view configuration and usage information for a stream and update its settings.
 
-## Access 
-From the Streams page, select the **Explore** icon from the **Actions** column.   
-![stream details access](../../images/stream-details-access.png) 
+This guide explains how to open **Stream Details** and the information it displays. 
 
-This opens the **Stream Details** panel, which provides configuration details, schema settings, and extended retention options.
+## Access the Stream Details 
+From the **Streams** page, select the **Explore** icon from the **Actions** column.   
+![stream details access](../../images/stream-details-access.png) 
 
 ## Permission
-
 User roles that have permission to update Streams can modify the stream settings from the **Stream Details** page. The permission needs to be assigned to appropriate user roles using role-based access control (RBAC). 
 
 ![stream details permission](../../images/stream-details-permission.png)
 
 ## Stream Details
-The **Stream Details** panel displays key configuration and usage information for the selected stream:
+**Stream Details** shows key configuration and usage information for the selected stream:
 
 ![stream details](../../images/stream-details.png)
 
@@ -42,10 +40,15 @@ The **Stream Details** panel displays key configuration and usage information fo
     ```
     ZO_DEFAULT_MAX_QUERY_RANGE_DAYS  
     ```  
-    > However, when a non-zero Max query range is set on a stream, the value set from the Stream Details panel overrides the global value. <br> By default, both the environment variable and **Max Query Range** in the UI is set to zero (o), which means no limit.
+    > However, when a non-zero Max query range is set on a stream, the value set through **Stream Details** overrides the global value. <br> By default, both the environment variable and the **Max Query Range** value are set to zero, which means there is no limit.
   
 - **Use Stream Stats for Partitioning**: When you enable this toggle, OpenObserve assumes that all your data present in the stream is equally split and creates equal sized partitions between the start and end time. 
 
+## Troubleshooting
+
+- If stream details appear blank, verify that the data has been successfully ingested.
+- Ensure you have the necessary role permissions to view or modify stream settings.
+
 ## Next Steps
 
 - [Schema Settings](schema-settings.md)