refactor: add standalone monitoring and remove export metrics (GreptimeTeam#1971)

Author: nicecui

docs/user-guide/deployments-administration/capacity-plan.md

@@ -18,7 +18,7 @@ there are several key considerations:
 - Data retention policy
 - Hardware costs
 
-To monitor the various metrics of GreptimeDB, please refer to [Monitoring](/user-guide/deployments-administration/monitoring/export-metrics.md).
+To monitor the various metrics of GreptimeDB, please refer to [Monitoring](/user-guide/deployments-administration/monitoring/overview.md).
 
 ## CPU
 

docs/user-guide/deployments-administration/configuration.md

@@ -485,7 +485,7 @@ The `meta_client` configures the Metasrv client, including:
 ### Monitor metrics options
 
 These options are used to save system metrics to GreptimeDB itself.
-For instructions on how to use this feature, please refer to the [Monitoring](/user-guide/deployments-administration/monitoring/export-metrics.md) guide.
+For instructions on how to use this feature, please refer to the [Monitoring](/user-guide/deployments-administration/monitoring/overview.md) guide.
 
 ```toml
 [export_metrics]

docs/user-guide/deployments-administration/monitoring/cluster-monitoring-deployment.md

@@ -5,7 +5,7 @@ description: Guide to deploying monitoring for GreptimeDB clusters on Kubernetes
 
 # Cluster Monitoring Deployment
 
-After deploying a GreptimeDB cluster using GreptimeDB Operator, by default, its components (Metasrv / Datanode / Frontend) expose a `/metrics` endpoint on their HTTP port (default `4000`) for Prometheus metrics.
+After deploying a GreptimeDB cluster using GreptimeDB Operator, by default, its components (Metasrv / Datanode / Frontend) expose a `/metrics` endpoint on their HTTP port (default `4000`) for [Prometheus metrics](/reference/http-endpoints.md#metrics).
 
 We provide two approaches to monitor the GreptimeDB cluster:
 
@@ -159,15 +159,6 @@ After configuring `prometheusMonitor`, GreptimeDB Operator will automatically cr
 kubectl get podmonitors.monitoring.coreos.com -n ${namespace}
 ```
 
-:::tip NOTE
-The configuration structure has changed between chart versions:
-
-- In older version: `meta.etcdEndpoints`
-- In newer version: `meta.backendStorage.etcd.endpoints`
-
-Always refer to the latest [values.yaml](https://github.com/GreptimeTeam/helm-charts/blob/main/charts/greptimedb-cluster/values.yaml) in the Helm chart repository for the most up-to-date configuration structure.
-:::
-
 :::note
 If not using Helm Chart, you can manually configure Prometheus monitoring in the `GreptimeDBCluster` YAML:
 

docs/user-guide/deployments-administration/monitoring/export-metrics.md

@@ -0,0 +1,62 @@
+---
+keywords: [standalone monitoring, GreptimeDB, metrics, Grafana]
+description: Guide to monitor GreptimeDB standalone instance using Prometheus metrics and Grafana.
+---
+
+# Standalone Monitoring
+
+GreptimeDB standalone provides a `/metrics` endpoint on the HTTP port (default `4000`) that exposes [Prometheus metrics](/reference/http-endpoints.md#metrics).
+
+## Monitoring configuration
+
+You can configure GreptimeDB to export metrics to GreptimeDB itself or to an external Prometheus instance.
+
+### Internal Metrics Storage
+
+Configuring GreptimeDB to store its own metrics internally is convenient and recommended for self-monitoring,
+it also enables SQL-based querying and analysis.
+
+To enable self-monitoring, configure the `export_metrics` section in your TOML configuration file:
+
+```toml
+[export_metrics]
+enable = true
+# Metrics collection interval
+write_interval = "30s"
+[export_metrics.self_import]
+db = "greptime_metrics"
+```
+
+This configuration:
+- Collects and writes metrics every 30 seconds.
+- Exports metrics to the `greptime_metrics` database within GreptimeDB. Ensure the `greptime_metrics` database [is created](/reference/sql/create.md#create-database) before exporting metrics.
+
+### Export metrics to Prometheus
+
+For environments with existing Prometheus infrastructure,
+GreptimeDB can export metrics via the Prometheus remote write protocol.
+
+To do this, configure the `export_metrics` section in your TOML configuration file with the `remote_write` option:
+
+```toml
+[export_metrics]
+enable=true
+write_interval = "30s"
+[export_metrics.remote_write]
+# URL specified by Prometheus Remote-Write protocol
+url = "https://your/remote_write/endpoint"
+# Some optional HTTP parameters, such as authentication information
+headers = { Authorization = {{Authorization}} }
+```
+
+This configuration:
+- Sets the export interval to 30 seconds
+- Specifies the Prometheus remote write URL, which should point to your Prometheus instance
+- Optionally includes HTTP headers for the remote write URL, such as authentication information
+
+## Grafana Dashboard Integration
+
+GreptimeDB provides pre-built Grafana dashboards for monitoring standalone deployments.
+You can access the dashboard JSON files from the [GreptimeDB repository](https://github.com/GreptimeTeam/greptimedb/tree/VAR::greptimedbVersion/grafana/dashboards/metrics/standalone).
+
+

docs/user-guide/deployments-administration/monitoring/standalone-monitoring.md

@@ -18,7 +18,7 @@ GreptimeDB 具备超轻量级的启动基准，
 - 数据保留策略
 - 硬件成本
 
-要监控 GreptimeDB 的各种指标，请参阅[监控](/user-guide/deployments-administration/monitoring/export-metrics.md)。
+要监控 GreptimeDB 的各种指标，请参阅[监控](/user-guide/deployments-administration/monitoring/overview.md)。
 
 ## CPU
 

i18n/zh/docusaurus-plugin-content-docs/current/user-guide/deployments-administration/capacity-plan.md

@@ -475,7 +475,7 @@ tcp_nodelay = true
 ### 指标监控选项
 
 这些选项用于将系统监控指标保存到 GreptimeDB 本身。
-有关如何使用此功能的说明，请参见 [监控](/user-guide/deployments-administration/monitoring/export-metrics.md) 指南。
+有关如何使用此功能的说明，请参见 [监控](/user-guide/deployments-administration/monitoring/overview.md) 指南。
 
 ```toml
 [export_metrics]

i18n/zh/docusaurus-plugin-content-docs/current/user-guide/deployments-administration/configuration.md

@@ -5,7 +5,7 @@ description: 在 Kubernetes 上部署 GreptimeDB 集群的监控指南，包括
 
 # 集群监控部署
 
-当你使用 GreptimeDB Operator 部署 GreptimeDB 集群后，默认其对应组件（如 Metasrv / Datanode / Frontend）的 HTTP 端口（默认为 `4000`）将会暴露 `/metrics` 端点用于暴露 Prometheus 指标。
+当你使用 GreptimeDB Operator 部署 GreptimeDB 集群后，默认其对应组件（如 Metasrv / Datanode / Frontend）的 HTTP 端口（默认为 `4000`）将会暴露 `/metrics` 端点用于暴露 [Prometheus 指标](/reference/http-endpoints.md#指标)。
 
 我们将提供两种方式来监控 GreptimeDB 集群：
 
@@ -159,15 +159,6 @@ prometheusMonitor:
 kubectl get podmonitors.monitoring.coreos.com -n ${namespace}
 ```
 
-:::tip NOTE
-chart 版本之间的配置结构已发生变化:
-
-- 旧版本: `meta.etcdEndpoints`
-- 新版本: `meta.backendStorage.etcd.endpoints`
-
-请参考 chart 仓库中配置 [values.yaml](https://github.com/GreptimeTeam/helm-charts/blob/main/charts/greptimedb-cluster/values.yaml) 以获取最新的结构。
-:::
-
 :::note
 如果你没有使用 Helm Chart 进行部署，你也可以通过如下 `GreptimeDBCluster` 的 YAML 来手动配置 Prometheus 监控，如下所示：