Merge remote-tracking branch 'origin/main' into ci/add_gitworkflow

Author: mmosarafO2

docs/api/traces/trace-search-api.md

@@ -77,21 +77,7 @@ curl -X GET \
 
 Retrieve detailed span information for a specific trace using the traces `/latest` endpoint with a `trace_id` filter.
 
-### Method 1: Using Traces Latest API 
-
-**Endpoint**
-```
-GET /api/{org_id}/{stream_name}/traces/latest?filter=trace_id%{trace_id}&start_time={start_time}&end_time={end_time}&from=0&size=25
-```
-
-**Example Request**
-```bash
-curl -X GET \
-  "https://your-openobserve-instance/api/your_org/default/traces/latest?filter=trace_id%3Dc2dc93864163b4f0e25342c2b8ca9a8b&start_time=1751443100969000&end_time=1751444000969000&from=0&size=25" \
-  -H "Authorization: Basic <your-auth-token>"
-```
-
-### Method 2: Using Search API 
+### Using Search API 
 
 For complex queries, you can use the [search API](https://openobserve.ai/docs/api/search/search/) with SQL queries:
 ```sql
@@ -100,6 +86,25 @@ SELECT * FROM default WHERE trace_id = {trace_id} ORDER BY start_time
 
 **Note:** Traces do not support full SQL queries in the traces interface, however, the search API supports SQL for trace data when needed for complex queries.
 
+**Example:**
+```sql
+{
+    "query": {
+        "sql": "SELECT * FROM default WHERE trace_id = b1eeb579ae863bdf9408e7d64c02d5d1" ORDER BY start_time, 
+        "start_time": 1751443100969000,
+        "end_time": 1751444000969000,
+        "from": 0,
+        "size": 25
+    },
+    "search_type": "ui",
+    "timeout": 0
+}
+```
+**Note:** 
+
+- When `size` is set to `25`, only the first `25` spans for the trace are returned.
+- To retrieve all spans, set `size` to `-1`. In this case, you do not need to define the `from` parameter.
+
 ## Error Handling
 
 Common HTTP Status Codes:

docs/ingestion/traces/nodejs.md

@@ -44,9 +44,9 @@ sdk.start();
 </br>
 ##Setup up credentials </br>
 
-You will get `url` and `Authorization` key here [http://cloud.openobserve.ai/ingestion/traces/](http://cloud.openobserve.ai/ingestion/traces/)
+You will get `url` and `Authorization` key [here](https://cloud.openobserve.ai/web/ingestion/custom/traces/opentelemetry).
 
-Replace the `url` and `Authorization` key in the `tracing.js` file
+Replace the `url` and `Authorization` key in the `tracing.js` file.
 
 ##Setup Service/Application </br>
 Run commands

docs/ingestion/traces/python.md

@@ -48,9 +48,9 @@ trace.set_tracer_provider(tracer_provider)
 ```
 ##Setup up credentials 
 
-You will get `url` and `Authorization` key here [http://cloud.openobserve.ai/ingestion/traces/](http://cloud.openobserve.ai/ingestion/traces/)
+You will get `url` and `Authorization` key [here](https://cloud.openobserve.ai/web/ingestion/custom/traces/opentelemetry).
 
-Replace the `url` and `Authorization` key in the `tracing.py` file
+Replace the `url` and `Authorization` key in the `tracing.py` file.
 
 ##Setup Service/Application 
 Follow the steps given in the sample-tracing-python readme and then start server
@@ -65,9 +65,7 @@ Refresh page couple of times to get more traces exported.
 
 
 
-Traces are captured, you can check these captured traces here [https://cloud.openobserve.ai/traces](https://cloud.openobserve.ai/traces)
-
-![Traces Page](./images/traces_python.png)
+Traces are captured, you can check these captured traces here [https://cloud.openobserve.ai/web/traces](https://cloud.openobserve.ai/web/traces).
 
 Filter traces with your service name `python-service`
 

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

@@ -6,13 +6,13 @@ This guide explains how to deploy [OpenObserve Enterprise Edition](https://openo
 
 > For support, reach out in the [Slack channel](https://short.openobserve.ai/community).
 
-??? info "Architecture Overview" 
+!!! info "Architecture Overview" 
     OpenObserve Enterprise Edition depends on several components to support scalable ingestion, search, storage, and access control:
 
     - **Object Storage**, such as S3, Azure Blob, GCS, or MinIO, stores all telemetry data in Parquet format.
     - **PostgreSQL** stores metadata such as dashboards, stream configurations, users, and the filelist table.
     - **NATS** coordinates communication between ingestion and query nodes.
-    - **Dex and OpenFGA** enable Single Sign-On (SSO) and Role-Based Access Control (RBAC).
+    - **Dex and OpenFGA** enable [Single Sign-On (SSO)](../user-guide/identity-and-access-management/sso/) and [Role-Based Access Control (RBAC)](../user-guide/identity-and-access-management/role-based-access-control/).
 
 
 ### Installation Steps