docs: update setup instructions for CHT Watchdog on CHT Sync to clari…

…fy target naming (#1630) * docs: update setup instructions for CHT Watchdog on CHT Sync to clarify target naming * Update content/en/hosting/monitoring/setup.md Co-authored-by: Andra Blaj <[email protected]> --------- Co-authored-by: Andra Blaj <[email protected]>
medic · Oct 18, 2024 · 80c6c98 · 80c6c98
1 parent 7779bf9
commit 80c6c98
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/content/en/hosting/monitoring/setup.md b/content/en/hosting/monitoring/setup.md
@@ -131,7 +131,7 @@ With the [release of 1.1.0](https://github.com/medic/cht-watchdog/releases/tag/1
    - targets:
       "db-example-com": 'postgres://db_user:[email protected]:5432/cht?sslmode=disable' # //NOSONAR - password is safe to commit
    ```
-   You may add as many targets as you would like here - one for each CHT Core instance in your `cht-instances.yml` file. Be sure to give each entry a unique name based of the Postgres server (eg `db-example-com` as shown).
+   You may add as many targets as you would like here - one for each CHT Core instance in your `cht-instances.yml` file. Be sure to match the key (`db-example-com` in this example) to the exact value defined in your `cht-instances.yml` file while ensuring the entry is unique.
 4. Start your instance up, being sure to include both the existing `docker-compose.yml` and the `docker-compose.postgres-exporter.yml` file:
 
    ```shell