Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[#181627193]: Updated federation part of docs #464

Closed
wants to merge 1 commit into from
Closed

[#181627193]: Updated federation part of docs #464

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions configuring/multi-foundation-monitoring.html.md.erb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,10 +49,7 @@ foundation or the TKGI Control Plane. To add a scrape job for a Healthwatch Expo
1. Nagivate to the Ops Manager Installation Dashboard for the foundation you want to monitor.
1. Click the **Healthwatch Exporter for Tanzu Application Service** tile.
1. Select the **Status** tab.
1. Record the following IP addresses:
* In the **TAS Counter Exporter** row, record the IP address of the counter metric exporter VM from the **IPs** column.
* In the **TAS Gauge Exporter** row, record the IP address of the gauge metric exporter VM from the **IPs** column.
* In the **TAS Timer Exporter** row, record the IP address of the timer metric exporter VM from the **IPs** column.
1. Record the external IP addresses of the **TAS Counter Exporter**, **TAS Gauge Exporter** and **TAS Timer Exporter** from your cloud platform:
1. Select the **Credentials** tab.
1. In the row for **Healthwatch Exporter Client Mtls**, click **Link to Credential**.
1. Record the credentials for **Healthwatch Exporter Client Mtls**.
Expand Down
10 changes: 7 additions & 3 deletions configuring/optional-config/federation.html.md.erb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,8 @@ Tile Through an Automated Pipeline](../../installing/automated-pipeline.html).
1. Click the **Healthwatch** tile.
1. Select the **Credentials** tab.
1. In the **Promxy Client Mtls** row of the **TSDB** section, click **Link to Credential**.
1. Record the values of `private_key_pem` and `cert_pem`. These values are the private key and certificate for **Promxy Client mTLS**.
1. Record the values of `private_key_pem` and `cert_pem`. These values are the private key and certificate for **Promxy Client mTLS**. (**Note** this data is provided in json format
and contains `\n` which should be converted into newlines manually in text editor.)
1. Retrieve the certificate for the Ops Manager root certificate authority (CA) of the foundation you want to monitor. For more information, see the [Ops
Manager documentation](https://docs.pivotal.io/ops-manager/security/pcf-infrastructure/managing-certificates.html#root-certs).
1. Navigate to the Ops Manager Installation Dashboard for your monitoring foundation.
Expand All @@ -80,9 +81,9 @@ Tile Through an Automated Pipeline](../../installing/automated-pipeline.html).
your load balancer or DNS entry in each target listed under the <code>targets</code> property instead of the IP address for the Prometheus
instance.</p>
1. For **Certificate and private key for TLS**, enter the certificate and private key you recorded from the **Promxy Client mTLS** row in the
**Credentials** tab in the Healthwatch tile installed on the foundation you want to monitor in a previous step.
**Credentials** tab in the Healthwatch tile installed on the foundation you want to monitor in a previous step. (**Note** please make sure that `\n` symbols had been replaced with newlines.)
1. For **CA certificate for TLS**, enter the Ops Manager root CA certificate for the foundation you want to monitor that you recorded in a previous step.
1. For **Target server name**, enter `promxy`.
1. For **Target server name**, enter `hwexporter`.
1. Click **Save**.
<br>
<br>
Expand All @@ -92,6 +93,9 @@ Tile Through an Automated Pipeline](../../installing/automated-pipeline.html).
For more information, see [Configure and Deploy Your Tile Using the om CLI](../../installing/automated-pipeline.html#om) in _Installing, Configuring, and
Deploying a Tile Through an Automated Pipeline_.

To check if your configured federation is working, go to 'Grafana' UI and run an `up` query from 'Explore' tab. In the result look for `job` or `external_ip`
which was provided in 'Scrape job configuration parameters' in 'Ops Manager'.

For more information about configuring scrape jobs, see [Configure Prometheus](../configuring-healthwatch.html#prometheus) in _Configuring Healthwatch_ and
the [Prometheus documentation](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config).

Expand Down