From 794baa25ddaa84bb6c218847ea1f33273defa92e Mon Sep 17 00:00:00 2001 From: Ti Chi Robot Date: Mon, 8 Apr 2024 15:55:51 +0800 Subject: [PATCH] tiup: add additional_args (#16915) (#17015) --- tiup/tiup-cluster-topology-reference.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tiup/tiup-cluster-topology-reference.md b/tiup/tiup-cluster-topology-reference.md index 3290c7cd76f07..c74f8bc1a915c 100644 --- a/tiup/tiup-cluster-topology-reference.md +++ b/tiup/tiup-cluster-topology-reference.md @@ -710,6 +710,8 @@ tispark_workers: - `resource_control`: Resource control for the service. If this field is configured, the field content is merged with the `resource_control` content in `global` (if the two fields overlap, the content of this field takes effect). Then, a systemd configuration file is generated and sent to the machine specified in `host`. The configuration rules of `resource_control` are the same as the `resource_control` content in `global`. +- `additional_args`: Introduced in TiUP v1.15.0, this field configures additional parameters for running Prometheus. This field is an array, and each element of the array is a Prometheus running parameter. For example, to enable the Prometheus hot reload feature, you can set this field to `--web.enable-lifecycle`. + - `additional_scrape_conf`: Customized Prometheus scrape configuration. When you deploy, scale out, scale in, or reload a TiDB cluster, TiUP adds the content of the `additional_scrape_conf` field to the corresponding parameters of the Prometheus configuration file. For more information, see [Customize Prometheus scrape configuration](/tiup/customized-montior-in-tiup-environment.md#customize-prometheus-scrape-configuration). For the above fields, you cannot modify these configured fields after the deployment: @@ -728,6 +730,8 @@ A `monitoring_servers` configuration example is as follows: monitoring_servers: - host: 10.0.1.11 rule_dir: /local/rule/dir + additional_args: + - --web.enable-lifecycle remote_config: remote_write: - queue_config: