You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To skip downloading and installing ClickHouse, add the `-s` flag to the script. This is useful if you do not plan to collect metrics.
10
+
11
+
If you skip ClickHouse, make sure to [disable metrics collection]({{< ref "nim/system-configuration/configure-clickhouse.md#disable-metrics-collection" >}}) in the `/etc/nms/nms.conf` configuration file after installing NGINX Instance Manager.
| clickhouse.enable | true | Set to `false` to disable metrics collection and run NGINX Instance Manager in lightweight mode. Requires a service restart. |
13
+
| clickhouse.address | tcp://localhost:9000 | The address of the ClickHouse database. |
14
+
| clickhouse.username || The username NGINX Instance Manager uses to connect to ClickHouse, if authentication is enabled. |
15
+
| clickhouse.password || The password for the specified ClickHouse user. |
16
+
| clickhouse.tls_mode | false | Set to `true` to enable TLS for the ClickHouse connection. This setting will be deprecated in a future release. Use the `clickhouse.tls` section instead. |
17
+
| clickhouse.tls.address | tcp://localhost:9440 | The address NGINX Instance Manager uses to connect to ClickHouse over TLS. Format: `<ip-address>:<port>`. |
18
+
| clickhouse.tls.skip_verify | false | Set to `true` to skip TLS certificate verification. Use only for self-signed certificates in non-production environments. |
19
+
| clickhouse.tls.key_path || Path to the client TLS key file in PEM format. Required for client authentication. |
20
+
| clickhouse.tls.cert_path || Path to the client TLS certificate file in PEM format. Required for client authentication. |
21
+
| clickhouse.tls.ca_path | /etc/ssl/certs/ca-certificates.crt | Path to the system Certificate Authority used to verify the server certificate. The default path works for Ubuntu and Debian. Use a CA bundle appropriate to your system. See [TLS configuration](#tls) for details. |
If you install ClickHouse and choose to set a password (the default is an empty string), you must add it to the `clickhouse.password` setting in the `/etc/nms/nms.conf` file. If the password is missing or incorrect, NGINX Instance Manager will not start.
11
+
12
+
For instructions and additional configuration options, including TLS settings, see [Configure ClickHouse]({{< ref "nim/system-configuration/configure-clickhouse.md" >}}).
13
+
{{< /call-out >}}
14
+
15
+
{{< call-out "note" "ClickHouse version requirement" "" >}}NGINX Instance Manager requires ClickHouse version {{< clickhouse-version >}} or later.
16
+
{{< /call-out >}}
17
+
18
+
Follow these steps to install and enable ClickHouse on supported Linux distributions.
If you installed ClickHouse and set a password (the default is an empty string), you must add it to the `clickhouse.password` setting in the `/etc/nms/nms.conf` file after installing NGINX Instance Manager. If the password is missing or incorrect, NGINX Instance Manager will not start.
11
+
12
+
You can also configure additional ClickHouse settings in the same section:
13
+
14
+
-`clickhouse.username` – the username used to connect to ClickHouse
15
+
-`clickhouse.address` – the address of the ClickHouse server (default is `tcp://localhost:9000`)
16
+
-`clickhouse.tls_mode` – set to `true` to enable TLS
17
+
- TLS certificate settings, such as:
18
+
-`clickhouse.tls.cert_path`
19
+
-`clickhouse.tls.key_path`
20
+
-`clickhouse.tls.ca_path`
21
+
-`clickhouse.tls.skip_verify`
22
+
23
+
For more details, see [Configure ClickHouse]({{< ref "nim/system-configuration/configure-clickhouse.md" >}}).
SELinux helps secure your deployment by enforcing mandatory access control policies.
11
+
12
+
If you use SELinux, follow the steps in the [Configure SELinux]({{< ref "/nim/system-configuration/configure-selinux.md" >}}) guide to restore SELinux contexts (`restorecon`) for the files and directories related to NGINX Instance Manager.
If you are not collecting metrics—either because you did not install ClickHouse or no longer want to use it—you must disable metrics collection by editing the `/etc/nms/nms.conf` file.
10
+
11
+
For instructions, see [Disable metrics collection]({{< ref "nim/system-configuration/configure-clickhouse.md#disable-metrics-collection" >}}).
NGINX Instance Manager can use [Vault](https://www.vaultproject.io/) as a datastore for secrets.
11
+
12
+
To install and enable Vault, follow these steps:
13
+
14
+
- Follow Vault's instructions to [install Vault 1.8.8 or later](https://www.vaultproject.io/docs/install) for your distribution.
15
+
- Ensure you're running Vault in a [production-hardened environment](https://learn.hashicorp.com/tutorials/vault/production-hardening).
16
+
- After installing NGINX Instance Manager, follow the steps to [configure Vault for storing secrets]({{< ref "/nim/system-configuration/configure-vault.md" >}}).
@@ -83,113 +83,25 @@ Install NGINX Open Source or NGINX Plus on the host where you'll install NGINX I
83
83
84
84
---
85
85
86
-
## Install ClickHouse {#install-clickhouse}
86
+
## Configure metrics collection
87
87
88
-
{{<note>}}NGINX Instance Manager requires ClickHouse 22.3.15.33 or later.{{</note>}}
88
+
### Disable metrics collection
89
89
90
-
NGINX Instance Manager uses [ClickHouse](https://clickhouse.com) to store metrics, events, and alerts, as well as configuration settings.
90
+
NGINX Instance Manager uses ClickHouse to store metrics, events, alerts, and configuration data.
91
91
92
-
Select the tab for your Linux distribution, then follow the instructions to install ClickHouse.
92
+
If you do not need to store metrics, you can skip the installation steps in this section. Instead, you must disable metrics collection in the `/etc/nms/nms.conf` configuration file.
93
93
94
-
{{<tabsname="clickhouse">}}
94
+
For instructions, see [Disable metrics collection]({{< ref "nim/system-configuration/configure-clickhouse.md#disable-metrics-collection" >}}).
95
95
96
-
{{%tab name="CentOS, RHEL, RPM-Based"%}}
97
-
98
-
To install and enable ClickHouse CentOS, RHEL, and RPM-Based distributions, take the following steps:
><span style="color: #c20025;"><i class="fas fa-exclamation-triangle"></i>**IMPORTANT!**</span> When installing ClickHouse, you have the option to specify a password or leave the password blank (the default is an empty string). If you choose to specify a password for ClickHouse, you must also edit the `/etc/nms/nms.conf` file after installing NGINX Instance Manager and enter your ClickHouse password; otherwise, NGINX Instance Manager won't start.
114
-
>
115
-
> For more information on customizing ClickHouse settings, refer to the [Configure ClickHouse]({{< ref "nim/system-configuration/configure-clickhouse.md" >}}) topic.
116
-
117
-
1. Enable ClickHouse so that it starts automatically if the server is restarted:
118
-
119
-
```bash
120
-
sudo systemctl enable clickhouse-server
121
-
```
122
-
123
-
1. Start the ClickHouse server:
124
-
125
-
```bash
126
-
sudo systemctl start clickhouse-server
127
-
```
128
-
129
-
1. Verify ClickHouse is running:
130
-
131
-
```bash
132
-
sudo systemctl status clickhouse-server
133
-
```
134
-
135
-
{{%/tab%}}
136
-
137
-
{{%tab name="Debian, Ubuntu, Deb-Based"%}}
138
-
139
-
To install and enable ClickHouse on Debian, Ubuntu, and Deb-Based distributions, take the following steps:
> <span style="color: #c20025;"><i class="fas fa-exclamation-triangle"></i> **IMPORTANT!**</span> When installing ClickHouse, you have the option to specify a password or leave the password blank (the default is an empty string). If you choose to specify a password for ClickHouse, you must also edit the `/etc/nms/nms.conf` file after installing NGINX Instance Manager and enter your ClickHouse password; otherwise, NGINX Instance Manager won't start.
161
-
>
162
-
> For more information on customizing ClickHouse settings, refer to the [Configure ClickHouse]({{< ref "nim/system-configuration/configure-clickhouse.md">}}) topic.
100
+
#### ClickHouse Default Settings
163
101
164
-
1. Enable ClickHouse so that it starts automatically ifthe server is restarted:
102
+
NGINX Instance Manager uses the following default values for ClickHouse. To change these values, see the [Configure ClickHouse](nim/system-configuration/configure-clickhouse.md) guide.
165
103
166
-
```bash
167
-
sudo systemctl enable clickhouse-server
168
-
```
169
-
170
-
1. Start the ClickHouse server:
171
-
172
-
``` bash
173
-
sudo systemctl start clickhouse-server
174
-
```
175
-
176
-
1. Verify ClickHouse is running:
177
-
178
-
```bash
179
-
sudo systemctl status clickhouse-server
180
-
```
181
-
182
-
{{%/tab%}}
183
-
184
-
{{</tabs>}}
185
-
186
-
### ClickHouse Default Settings
187
-
188
-
NGINX Instance Manager uses the following default values for ClickHouse:
189
-
190
-
{{<important>}}You can customize these settings. However, if you use custom settings, make sure to follow the [Configure ClickHouse]({{< ref "nim/system-configuration/configure-clickhouse.md">}}) instructions to update the `nms.conf` file after you've installed NGINX Instance Manager; otherwise NGINX Instance Manager won't be able to connect to ClickHouse.{{</important>}}
191
-
192
-
{{< include "installation/clickhouse-defaults.md">}}
104
+
{{< include "nim/clickhouse/clickhouse-defaults.md" >}}
193
105
194
106
---
195
107
@@ -258,16 +170,27 @@ To install NGINX Instance Manager, you need to add the official repository to pu
258
170
sudo systemctl restart nginx
259
171
```
260
172
261
-
### Post-Installation Steps
173
+
## Optional post-installation steps
174
+
175
+
### Configure ClickHouse
176
+
177
+
{{< include "nim/installation/optional-steps/configure-clickhouse.md">}}
178
+
179
+
### Install and configure Vault {#install-vault}
180
+
181
+
{{< include "nim/installation/optional-steps/install-configure-vault.md">}}
182
+
183
+
184
+
### Configure SELinux
262
185
263
-
{{< include "installation/optional-installation-steps.md" >}}
186
+
{{< include "nim/installation/optional-steps/configure-selinux.md">}}
264
187
265
-
### Accessing the Web Interface
188
+
## Accessing the Web Interface
266
189
267
190
{{< include "installation/access-web-ui.md">}}
268
191
269
192
270
-
### Add License
193
+
## Add License
271
194
272
195
{{< include "nim/admin-guide/license/connected-install-license-note.md">}}
0 commit comments