fix: use new path instead of the deprecated path in docs (#2104)

Signed-off-by: shuiyisong <[email protected]>

Author: shuiyisong

docs/greptimecloud/integrations/fluent-bit.md

@@ -18,7 +18,7 @@ Fluent Bit can be configured to send logs to GreptimeCloud using the HTTP protoc
     Match            *
     Host             <host>
     Port             443
-    Uri              /v1/events/logs?db=<dbname>&table=<table_name>&pipeline_name=<pipeline_name>
+    Uri              /v1/ingest?db=<dbname>&table=<table_name>&pipeline_name=<pipeline_name>
     Format           json
     Json_date_key    scrape_timestamp
     Json_date_format iso8601

docs/reference/http-endpoints.md

@@ -222,9 +222,9 @@ Refer to the original Prometheus documentation for more information on the [Prom
 ## Log Ingestion Endpoints
 
 - **Paths**:
-  - `/v1/events/logs`
-  - `/v1/events/pipelines/{pipeline_name}`
-  - `/v1/events/pipelines/dryrun`
+  - `/v1/ingest`
+  - `/v1/pipelines/{pipeline_name}`
+  - `/v1/pipelines/dryrun`
 - **Methods**:
   - `POST` for ingesting logs and adding pipelines.
   - `DELETE` for deleting pipelines.

docs/user-guide/ingest-data/for-observability/fluent-bit.md

@@ -19,7 +19,7 @@ Using Fluent Bit's [HTTP Output Plugin](https://docs.fluentbit.io/manual/pipelin
     Match            *
     Host             greptimedb
     Port             4000
-    Uri              /v1/events/logs?db=public&table=your_table&pipeline_name=pipeline_if_any
+    Uri              /v1/ingest?db=public&table=your_table&pipeline_name=pipeline_if_any
     Format           json
     Json_date_key    scrape_timestamp
     Json_date_format iso8601

docs/user-guide/ingest-data/for-observability/loki.md

@@ -222,7 +222,7 @@ In the `greptime_loki`, the `x-greptime-pipeline-name` header is added to indica
 2. [Upload](/user-guide/logs/manage-pipelines.md#create-a-pipeline) the pipeline configuration to the database using `curl`:
 
 ```bash
-curl -X "POST" "http://localhost:4000/v1/events/pipelines/pp" -F "[email protected]"
+curl -X "POST" "http://localhost:4000/v1/pipelines/pp" -F "[email protected]"
 ```
 
 3. Start the Alloy Docker container to process the logs:

docs/user-guide/logs/manage-pipelines.md

@@ -21,7 +21,7 @@ Assuming you have prepared a pipeline configuration file `pipeline.yaml`, use th
 
 ```shell
 ## Upload the pipeline file. 'test' is the name of the pipeline
-curl -X "POST" "http://localhost:4000/v1/events/pipelines/test" \
+curl -X "POST" "http://localhost:4000/v1/pipelines/test" \
   -H "Authorization: Basic {{authentication}}" \
   -F "[email protected]"
 ```
@@ -34,7 +34,7 @@ You can use the following HTTP interface to delete a pipeline:
 
 ```shell
 ## 'test' is the name of the pipeline
-curl -X "DELETE" "http://localhost:4000/v1/events/pipelines/test?version=2024-06-27%2012%3A02%3A34.257312110Z" \
+curl -X "DELETE" "http://localhost:4000/v1/pipelines/test?version=2024-06-27%2012%3A02%3A34.257312110Z" \
   -H "Authorization: Basic {{authentication}}"
 ```
 
@@ -46,13 +46,13 @@ Querying a pipeline with a name through HTTP interface as follow:
 
 ```shell
 ## 'test' is the name of the pipeline, it will return a pipeline with latest version if the pipeline named `test` exists.
-curl "http://localhost:4000/v1/events/pipelines/test" \
+curl "http://localhost:4000/v1/pipelines/test" \
   -H "Authorization: Basic {{authentication}}"
 ```
 
 ```shell
 ## with the version parameter, it will return the specify version pipeline.
-curl "http://localhost:4000/v1/events/pipelines/test?version=2025-04-01%2006%3A58%3A31.335251882%2B0000" \
+curl "http://localhost:4000/v1/pipelines/test?version=2025-04-01%2006%3A58%3A31.335251882%2B0000" \
   -H "Authorization: Basic {{authentication}}"
 ```
 
@@ -192,7 +192,7 @@ You may encounter errors when creating a Pipeline. For example, when creating a
 
 
 ```bash
-curl -X "POST" "http://localhost:4000/v1/events/pipelines/test" \
+curl -X "POST" "http://localhost:4000/v1/pipelines/test" \
      -H "Content-Type: application/x-yaml" \
      -H "Authorization: Basic {{authentication}}" \
      -d $'processors:
@@ -228,7 +228,7 @@ The pipeline configuration contains an error. The `gsub` Processor expects the `
 Therefore, We need to modify the configuration of the `gsub` Processor and change the value of the `replacement` field to a string type.
 
 ```bash
-curl -X "POST" "http://localhost:4000/v1/events/pipelines/test" \
+curl -X "POST" "http://localhost:4000/v1/pipelines/test" \
      -H "Content-Type: application/x-yaml" \
      -H "Authorization: Basic {{authentication}}" \
      -d $'processors:
@@ -263,7 +263,7 @@ We can test the Pipeline using the `dryrun` interface. We will test it with erro
 
 
 ```bash
-curl -X "POST" "http://localhost:4000/v1/events/pipelines/dryrun?pipeline_name=test" \
+curl -X "POST" "http://localhost:4000/v1/pipelines/dryrun?pipeline_name=test" \
      -H "Content-Type: application/json" \
      -H "Authorization: Basic {{authentication}}" \
      -d $'{"message": 1998.08,"time":"2024-05-25 20:16:37.217"}'
@@ -275,7 +275,7 @@ The output indicates that the pipeline processing failed because the `gsub` Proc
 Let's change the value of the message field to a string type and test the pipeline again.
 
 ```bash
-curl -X "POST" "http://localhost:4000/v1/events/pipelines/dryrun?pipeline_name=test" \
+curl -X "POST" "http://localhost:4000/v1/pipelines/dryrun?pipeline_name=test" \
      -H "Content-Type: application/json" \
      -H "Authorization: Basic {{authentication}}" \
      -d $'{"message": "1998.08","time":"2024-05-25 20:16:37.217"}'

docs/user-guide/logs/quick-start.md

@@ -22,7 +22,7 @@ GreptimeDB offers a built-in pipeline, `greptime_identity`, for handling JSON lo
 
 ```shell
 curl -X POST \
-  "http://localhost:4000/v1/events/logs?db=public&table=pipeline_logs&pipeline_name=greptime_identity" \
+  "http://localhost:4000/v1/ingest?db=public&table=pipeline_logs&pipeline_name=greptime_identity" \
   -H "Content-Type: application/json" \
   -H "Authorization: Basic {{authentication}}" \
   -d '[
@@ -133,7 +133,7 @@ Execute the following command to upload the configuration file:
 
 ```shell
 curl -X "POST" \
-  "http://localhost:4000/v1/events/pipelines/nginx_pipeline" \
+  "http://localhost:4000/v1/pipelines/nginx_pipeline" \
      -H 'Authorization: Basic {{authentication}}' \
      -F "[email protected]"
 ```
@@ -154,7 +154,7 @@ The following example writes logs to the `custom_pipeline_logs` table and uses t
 
 ```shell
 curl -X POST \
-  "http://localhost:4000/v1/events/logs?db=public&table=custom_pipeline_logs&pipeline_name=nginx_pipeline" \
+  "http://localhost:4000/v1/ingest?db=public&table=custom_pipeline_logs&pipeline_name=nginx_pipeline" \
   -H "Content-Type: application/json" \
   -H "Authorization: Basic {{authentication}}" \
   -d '[

docs/user-guide/logs/write-logs.md

@@ -14,7 +14,7 @@ Before writing logs, please read the [Pipeline Configuration](pipeline-config.md
 You can use the following command to write logs via the HTTP interface:
 
 ```shell
-curl -X "POST" "http://localhost:4000/v1/events/logs?db=<db-name>&table=<table-name>&pipeline_name=<pipeline-name>&version=<pipeline-version>" \
+curl -X "POST" "http://localhost:4000/v1/ingest?db=<db-name>&table=<table-name>&pipeline_name=<pipeline-name>&version=<pipeline-version>" \
      -H "Content-Type: application/x-ndjson" \
      -H "Authorization: Basic {{authentication}}" \
      -d "$<log-items>"
@@ -190,7 +190,7 @@ Example of Incoming Log Data:
 
 To instruct the server to use ts as the time index, set the following query parameter in the HTTP header:
 ```shell
-curl -X "POST" "http://localhost:4000/v1/events/logs?db=public&table=pipeline_logs&pipeline_name=greptime_identity&custom_time_index=ts;epoch;s" \
+curl -X "POST" "http://localhost:4000/v1/ingest?db=public&table=pipeline_logs&pipeline_name=greptime_identity&custom_time_index=ts;epoch;s" \
      -H "Content-Type: application/json" \
      -H "Authorization: Basic {{authentication}}" \
      -d $'[{"action": "login", "ts": 1742814853}]'
@@ -231,7 +231,7 @@ If flattening a JSON object into a single-level structure is needed, add the `x-
 Here is a sample request:
 
 ```shell
-curl -X "POST" "http://localhost:4000/v1/events/logs?db=<db-name>&table=<table-name>&pipeline_name=greptime_identity&version=<pipeline-version>" \
+curl -X "POST" "http://localhost:4000/v1/ingest?db=<db-name>&table=<table-name>&pipeline_name=greptime_identity&version=<pipeline-version>" \
      -H "Content-Type: application/x-ndjson" \
      -H "Authorization: Basic {{authentication}}" \
      -H "x-greptime-pipeline-params: flatten_json_object=true" \
@@ -338,7 +338,7 @@ mode](/user-guide/deployments-administration/performance-tuning/design-table.md#
 If you want to skip errors when writing logs, you can add the `skip_error` parameter to the HTTP request's query params. For example:
 
 ```shell
-curl -X "POST" "http://localhost:4000/v1/events/logs?db=<db-name>&table=<table-name>&pipeline_name=<pipeline-name>&version=<pipeline-version>&skip_error=true" \
+curl -X "POST" "http://localhost:4000/v1/ingest?db=<db-name>&table=<table-name>&pipeline_name=<pipeline-name>&version=<pipeline-version>&skip_error=true" \
      -H "Content-Type: application/x-ndjson" \
      -H "Authorization: Basic {{authentication}}" \
      -d "$<log-items>"

i18n/zh/docusaurus-plugin-content-docs/current/greptimecloud/integrations/fluent-bit.md

@@ -17,7 +17,7 @@ Fluent Bit 可以配置为使用 HTTP 协议将日志发送到 GreptimeCloud。
     Match            *
     Host             <host>
     Port             443
-    Uri              /v1/events/logs?db=<dbname>&table=<table_name>&pipeline_name=<pipeline_name>
+    Uri              /v1/ingest?db=<dbname>&table=<table_name>&pipeline_name=<pipeline_name>
     Format           json
     Json_date_key    scrape_timestamp
     Json_date_format iso8601

i18n/zh/docusaurus-plugin-content-docs/current/reference/http-endpoints.md

@@ -222,9 +222,9 @@ is_strict_mode = false
 ## 日志写入端点
 
 - **路径**:
-  - `/v1/events/logs`
-  - `/v1/events/pipelines/{pipeline_name}`
-  - `/v1/events/pipelines/dryrun`
+  - `/v1/ingest`
+  - `/v1/pipelines/{pipeline_name}`
+  - `/v1/pipelines/dryrun`
 - **方法**:
   - `POST` 写入日志和添加 Pipeline。
   - `DELETE` 用于删除 Pipeline。

i18n/zh/docusaurus-plugin-content-docs/current/user-guide/ingest-data/for-observability/fluent-bit.md

@@ -19,7 +19,7 @@ description: 将 GreptimeDB 与 Fluent bit 集成以实现 Prometheus Remote Wri
     Match            *
     Host             greptimedb
     Port             4000
-    Uri              /v1/events/logs?db=public&table=your_table&pipeline_name=pipeline_if_any
+    Uri              /v1/ingest?db=public&table=your_table&pipeline_name=pipeline_if_any
     Format           json
     Json_date_key    scrape_timestamp
     Json_date_format iso8601