Remove export_metrics configuration from main docs

Co-authored-by: fengjiachun <[email protected]>

Author: Copilot

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

@@ -508,59 +508,6 @@ The `meta_client` configures the Metasrv client, including:
 - `ddl_timeout`, DDL execution timeout, `10s` by default.
 - `tcp_nodelay`, `TCP_NODELAY` option for accepted connections, true by default.
 
-### 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/overview.md) guide.
-
-```toml
-[export_metrics]
-# Whether to enable export_metrics
-enable=true
-# Export time interval
-write_interval = "30s"
-```
-
-- `enable`: Whether to enable export_metrics, `false` by default.
-- `write_interval`: Export time interval.
-
-#### `self_import` method
-
-If you are using `standalone`, you can use the `self_import` method to export metrics to GreptimeDB itself.
-
-```toml
-[export_metrics]
-# Whether to enable export_metrics
-enable=true
-# Export time interval
-write_interval = "30s"
-[export_metrics.self_import]
-db = "information_schema"
-```
-
-- `db`: The default database used by `self_import` is `information_schema`. You can also create another database for saving system metrics.
-
-#### `remote_write` method
-
-The `remote_write` method is supported by `datanode`, `frontend`, `metasrv`, and `standalone`.
-It sends metrics to a receiver compatible with the [Prometheus Remote-Write protocol](https://prometheus.io/docs/concepts/remote_write_spec/).
-
-```toml
-[export_metrics]
-# Whether to enable export_metrics
-enable=true
-# Export time interval
-write_interval = "30s"
-[export_metrics.remote_write]
-# URL specified by Prometheus Remote-Write protocol
-url = "http://127.0.0.1:4000/v1/prometheus/write?db=information_schema"
-# Some optional HTTP parameters, such as authentication information
-headers = { Authorization = "Basic Z3JlcHRpbWVfdXNlcjpncmVwdGltZV9wd2Q=" }
-```
-
-- `url`: URL specified by Prometheus Remote-Write protocol.
-- `headers`: Some optional HTTP parameters, such as authentication information.
-
 ### Heartbeat configuration
 Heartbeat configuration is available in `frontend` and `datanode`.
 ```toml

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

@@ -7,52 +7,7 @@ description: Guide to monitor GreptimeDB standalone instance using Prometheus me
 
 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
+You can use Prometheus to scrape these metrics and Grafana to visualize them.
 
 ## Grafana Dashboard Integration