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
* `[instancename]` : you can configure multiple connections within one `.mdbservice`-file. This config section name corresponds with the `--instance`-argument of the plugin
42
-
* `hostname` : optional, defaults to `localhost`
43
-
* `port` : optional, defaults to `27017`
44
-
* `user` : optional
45
-
* `pw` : optional
46
-
* `authdb` : optional, defaults to `admin`
47
-
* `tls` : `true`/`false`, defaults to `true`
47
+
48
+
- `[instancename]` : you can configure multiple connections within one `.mdbservice`\-file. This config section name corresponds with the `--instance`\-argument of the plugin
49
+
- `hostname` : optional, defaults to `localhost`
50
+
- `port` : optional, defaults to `27017`
51
+
- `user` : optional
52
+
- `pw` : optional
53
+
- `authdb` : optional, defaults to `admin`
54
+
- `tls` : `true`/`false`, defaults to `true`
55
+
- `tlscafile` : Path to cacerts file for TLS certificate validation
56
+
- `tls_allow_invalid_hostnames` : `true`/`false`, connect to MongoDB via TLS even if the CommonName/SubjectAlternativeName of the Cert does not match our Servername. Defaults to `false`
57
+
- `tls_allow_invalid_certificates`: `true`/`false`, connect to MongoDB via TLS even if the TLS-Certificate is invalid (i.e. expired). Defaults to `false`
48
58
49
59
#### Configuring database use
50
-
* Open a MongoDB DB shell, create a dedicated monitoring user and assign the `clusterMonitor` role
60
+
61
+
- Open a MongoDB DB shell, create a dedicated monitoring user and assign the `clusterMonitor` role
0 commit comments