Configuring Healthwatch

Page last updated:

This topic describes how to manually configure and deploy the Healthwatch for VMware Tanzu tile.

To install, configure, and deploy Healthwatch through an automated pipeline, see Installing, Configuring, and Deploying a Tile Through an Automated Pipeline.

Overview of Configuring and Deploying Healthwatch

The Healthwatch tile monitors metrics across one or more Ops Manager foundations by scraping metrics from Healthwatch Exporter tiles installed on each foundation. For more information about the architecture of the Healthwatch tile, see Healthwatch Tile in Healthwatch Architecture.

After installing Healthwatch, you configure Healthwatch component VMs, including the configuration files associated with them, through the tile UI. You can also configure errands and system logging, as well as scale VM instances up or down and configure load balancers for multiple VM instances.

To configure and deploy the Healthwatch tile:

Notes:
  • To quickly deploy the Healthwatch tile to ensure that it deploys successfully before you fully configure it, you only need to configure the Assign AZ and Networks pane.
  • If you are using Healthwatch to monitor Ops Manager foundations that are running Tanzu Kubernetes Grid Integrated Edition (TKGI), you must configure the TKGI Cluster Discovery pane.
  1. Navigate to the Healthwatch tile in the Ops Manager Installation Dashboard. For more information, see Navigate to the Healthwatch Tile below.

  2. Assign jobs to your Availability Zones (AZs) and networks. For more information, see Assign AZs and Networks below.

  3. Configure the Prometheus pane. For more information, see Configure Prometheus below.

  4. (Optional) Configure the Alertmanager pane. For more information, see (Optional) Configure Alertmanager below.

  5. (Optional) Configure the Grafana pane. For more information, see (Optional) Configure Grafana below.

  6. (Optional) Configure the Canary URLs pane. For more information, see (Optional) Configure Canary URLs below.

  7. (Optional) Configure the Remote Write pane. For more information, see (Optional) Configure Remote Write below.

  8. Configure the TKGI Cluster Discovery pane. For more information, see Configure TKGI Cluster Discovery below.

  9. (Optional) Configure the Errands pane. For more information, see (Optional) Configure Errands below.

  10. (Optional) Configure the Syslog pane. For more information, see (Optional) Configure Syslog below.

  11. (Optional) Configure the Resource Config pane. For more information, see (Optional) Configure Resources below.

  12. Deploy Healthwatch. For more information, see Deploy Healthwatch below.

After you have configured and deployed the Healthwatch tile, you can configure and deploy the Healthwatch Exporter tiles for the Ops Manager foundations you want to monitor. For more information, see Next Steps below.

Navigate to the Healthwatch Tile

To navigate to the Healthwatch tile:

  1. Navigate to the Ops Manager Installation Dashboard.

  2. Click the Healthwatch tile.

Assign AZs and Networks

In the Assign AZ and Networks pane, you assign jobs to your AZs and networks.

To configure the Assign AZ and Networks pane:

  1. Select Assign AZs and Networks.

  2. Under Place singleton jobs in, select the first AZ. Ops Manager runs any job with a single instance in this AZ.

  3. Under Balance other jobs in, select one or more other AZs. Ops Manager balances instances of jobs with more than one instance across the AZs that you specify.

  4. From the Network dropdown, select the runtime network that you created when configuring the BOSH Director tile.

  5. Click Save.

Configure Prometheus

In the Prometheus pane, you configure the Prometheus instance in the Healthwatch tile to scrape metrics from the Healthwatch Exporter tiles installed on each Ops Manager foundation, as well as any external services or databases from which you want to collect metrics.

The values that you configure in the Prometheus pane also configure their corresponding properties in the Prometheus configuration file. For more information, see Overview of Configuration Files in Healthwatch in Configuration File Reference Guide, Prometheus in Configuration File Reference Guide, and the Prometheus documentation.

To configure the Prometheus pane:

  1. Select Prometheus.

  2. For Scrape interval, specify the frequency at which you want the Prometheus instance to scrape Prometheus exposition endpoints for metrics. The Prometheus instance scrapes all Prometheus exposition endpoints at once through a global scrape. You can enter a value string that specifies ns, us, ┬Ás, ms, s, m, or h. To scrape detailed metrics without consuming too much storage, VMware recommends using the default value of 15s, or 15 seconds.

  3. (Optional) To configure the Prometheus instance to scrape metrics from the Healthwatch Exporter tiles installed on other Ops Manager foundations or from external services or databases, configure additional scrape jobs under Additional scrape jobs. You can configure scrape jobs for any app or service that exposes metrics using a Prometheus exposition format, such as Concourse CI. For more information about Prometheus exposition formats, see the Prometheus documentation.

    Note: The Prometheus instance automatically discovers and scrapes Healthwatch Exporter tiles that are installed on the same Ops Manager foundation as the Healthwatch tile. You do not need to configure scrape jobs for these Healthwatch Exporter tiles. You only need to configure scrape jobsbfor Healthwatch Exporter tiles that are installed on other Ops Manager foundations.

    1. Click Add.
    2. For Scrape job configuration parameters, provide the configuration YAML for the scrape job you want to configure. This job can use any of the properties defined by Prometheus except those in the tls_config section. Do not prefix the configuration YAML with a dash. For example:

      job_name: foundation-1
      metrics_path: /metrics
      scheme: https
      static_configs:
       - targets:
         - "1.2.3.4:9090"
         - "5.6.7.8:9090"
      

      For more information, see the Prometheus documentation.

      Warning: For the job_name property, do not use the following job names:
      • Healthwatch-view-pas-exporter
      • Healthwatch-view-pks-exporter
      • tsdb
      • grafana
      • pks-master-kube-scheduler
      • pks-master-kube-controller-manager

    3. (Optional) To allow the Prometheus instance to communicate with the server for your external service or database over TLS:

      1. For Certificate and private key for TLS, provide a certificate and private key for the Prometheus instance to use for TLS connections to the server for your external service or database.
      2. For CA certificate for TLS, provide a certificate for the certificate authority (CA) that the server for your external service or database uses to verify TLS certificates.
      3. For Target server name, enter the name of the server for your external service or database as it appears on the server’s TLS certificate.
      4. If the certificate you provided in Certificate and private key for TLS is signed by a self-signed CA certificate or a certificate that is signed by a self-signed CA certificate, activate the Skip TLS certificate verification checkbox. When this checkbox is activated, the Prometheus instance does not verify the identity of the server for your external service or database. This checkbox is deactivated by default.
  4. For Free disk chunk size, enter in MB the size that you want to specify for free chunks of disk. The default value is 6144. Healthwatch uses this free chunk size to calculate the available free disk chunks super value metric (SVM), which it then uses to calculate the Diego_AvailableFreeChunksDisk metric. If you configure Healthwatch Exporter for TAS for VMs to deploy the SVM Forwarder VM, the SVM Forwarder VM sends the Diego_AvailableFreeChunksDisk metric back into the Loggregator Firehose so third-party nozzles can send it to external destinations, such as a remote server or external aggregation service. For more information about SVMs, see SVM Forwarder VM - Platform Metrics and SVM Forwarder VM - Healthwatch Component Metrics in Healthwatch Metrics. For more information about deploying the SVM Forwarder VM, see (Optional) Configure Resources in Configuring Healthwatch Exporter for TAS for VMs.

  5. For Free memory chunk size, enter in MB the size that you want to specify for free chunks of memory. The default value is 4096. Healthwatch uses this free chunk size to calculate the available free memory chunks SVM, which it then uses to calculate the Diego_AvailableFreeChunksMemory metric. If you configure Healthwatch Exporter for TAS for VMs to deploy the SVM Forwarder VM, the SVM Forwarder VM sends the Diego_AvailableFreeChunksMemory metric back into the Loggregator Firehose so third-party nozzles can send it to external destinations, such as a remote server or external aggregation service. For more information about SVMs, see SVM Forwarder VM - Platform Metrics and SVM Forwarder VM - Healthwatch Component Metrics in Healthwatch Metrics. For more information about deploying the SVM Forwarder VM, see (Optional) Configure Resources in Configuring Healthwatch Exporter for TAS for VMs.

  6. (Optional) For Static IP addresses for Prometheus VMs, enter a comma-separated list of valid static IP addresses that you want to reserve for the Prometheus instance. You must enter a separate IP address for each VM in the Prometheus instance. These IP addresses must not be within the reserved IP ranges you configured in the BOSH Director tile. To find the IP addresses of the Prometheus VMs:

    1. Select the Status tab.
    2. In the TSDB row, record the IP addresses of each Prometheus VM from the IPs column.

      Note: The Prometheus instance includes two VMs by default. For more information about viewing or scaling your VMs, see Healthwatch Components and Resource Requirements.

  7. Click Save.

(Optional) Configure Alertmanager

In the Alertmanager pane, you configure alerting for Healthwatch. To configure alerting for Healthwatch, you configure the alerting rules that Alertmanager follows and the alert receivers to which Alertmanager sends alerts.

To configure the Alertmanager pane, see Configuring Alerting.

(Optional) Configure Grafana

In the Grafana pane, you configure how users access and authenticate with the Grafana UI, as well as which dashboards appear in the Grafana UI. For more information about the Grafana UI as it relates to Healthwatch, see Healthwatch.

The values that you configure in the Grafana pane also configure their corresponding properties in the Grafana configuration file. For more information, see Overview of Configuration Files in Healthwatch in Configuration File Reference Guide, Configuring the Grafana Configuration File in Configuration File Reference Guide, and the Grafana documentation.

To configure the Grafana pane:

  1. Select Grafana.

  2. (Optional) If you configured generic OAuth or UAA authentication for users to log in to the Grafana UI, or if you configured alerts through Alertmanager, enter a URL for the Grafana UI in Grafana root URL. You must configure this URL to allow a generic OAuth provider or UAA to redirect users to the Grafana UI. Alertmanager also uses this URL to generate links to the Grafana UI in alert messages.

    Note: Healthwatch v2.1 does not automatically assign a default root URL to the Grafana UI. You must manually configure a root URL for the Grafana UI in the Grafana root URL field.

    After you deploy the Healthwatch tile for the first time, you must use this root URL and the public IP address of either a single Grafana VM or the load balancer associated with your Grafana instance to configure a DNS entry for the Grafana instance in the console for your IaaS. Your Grafana instance listens on either port 443 or 80, depending on whether you provide a TLS certificate in the Certificate and private key for HTTPS fields below. For more information about configuring DNS for the Grafana instance, see Configuring DNS for the Grafana Instance.

  3. Under HTTP and HTTPS proxy request settings, choose whether to allow the Grafana instance to make HTTP and HTTPS requests through proxy servers:

    1. To allow the Grafana instance to make HTTP and HTTPS requests through a proxy server:
      1. Select Configure.
      2. For HTTP proxy URL, enter the URL for your HTTP proxy server. The Grafana instance sends all HTTP and HTTPS requests to this URL, except those from hosts you configure in the HTTPS proxy URL and Excluded hosts fields below.
      3. For HTTPS proxy URL, enter the URL for your HTTPS proxy server. The Grafana instance sends all HTTPS requests to this URL, except those from hosts you configure in the Excluded hosts field below.
      4. For Excluded hosts, enter a comma-separated list of the hosts you want to exclude from proxying. VMware recommends including *.bosh and the ange of your internal network IP addresses so the Grafana instance can still access the Prometheus instance without going though the proxy server. For example, *.bosh,10.0.0.0/8,*.example.com allows the Grafana instance to access all BOSH DNS addresses and all internal network IP addresses containing 10.0.0.0/8 or *.example.com directly, without going though the proxy server.

        Note: You only need to configure proxy settings if you are deploying Healthwatch in an air-gapped environment and want to configure alert channels to external addresses, such as the external Slack webhook.

    2. To disallow the Grafana instance from making HTTP and HTTPS requests through proxy servers, select Do not configure. HTTP and HTTPS proxy requests are disallowed by default.
  4. (Optional) For Static IP addresses for Grafana VMs, enter a comma-separated list of valid static IP addresses that you want to reserve for the Grafana instance. These IP addresses must not be within the reserved IP ranges you configured in the BOSH Director tile.

  5. (Optional) To prevent users from logging in to Grafana UI with basic authentication, including admin users, deactivate the Allow Grafana UI login with basic authentication checkbox. This checkbox is activated by default.

  6. Under Runtime discovery, select how you want the Grafana instance to discover the runtimes installed on your Ops Manager foundations:

    • Dynamic: The Grafana instance creates a dashboard in the Grafana UI for the versions of VMware Tanzu Application Service for VMs (TAS for VMs) and TKGI that are currently installed on your Ops Manager foundations. This option is selected by default.
    • Manual: The Grafana instance creates a dashboard in the Grafana UI for the versions of TAS for VMs and TKGI you specify in the TAS for VMs version and TKGI version fields.
    • Do not allow: The Grafana instance does not discover or create dashboards in the Grafana UI for TAS for VMs or TKGI.

      Note: If you are using Pivotal Application Service (PAS) v2.7, you must allow PAS v2.7 to forward system metrics to the Loggregator Firehose, or no metrics appear in the Router dashboard in the Grafana UI. For more information, see Troubleshooting Missing Router Metrics in Troubleshooting Healthwatch.

  7. (Optional) If you want the Grafana instance to create a dashboard for metrics from the VMware Tanzu SQL with MySQL for VMs (Tanzu SQL for VMs) tile, activate the Create Tanzu SQL for VMs dashboard checkbox. This checkbox is deactivated by default.

  8. (Optional) If you want the Grafana instance to create dashboards for metrics from the VMware Tanzu RabbitMQ for VMs (Tanzu RabbitMQ) tile, activate the Create Tanzu RabbitMQ dashboards checkbox. This checkbox is deactivated by default.

    Note: If you activate the Create Tanzu RabbitMQ dashboards checkbox, set the Metrics polling interval field in the Tanzu RabbitMQ tile to -1. This prevents the Tanzu RabbitMQ tile from sending duplicate metrics to the Loggregator Firehose. To configure this field, see the Tanzu RabbitMQ documentation.

  9. (Optional) To allow HTTPS connections to one or more Grafana instances, you must provide a certificate and private key for the Grafana instance to use for TLS connections in Certificate and private key for HTTPS.

    VMware recommends also providing a certificate signed by a third-party CA in CA certificate for HTTPS. You can generate a self-signed certificate using the Ops Manager root CA, but doing so causes your browser to warn you that your CA is invalid every time you access the Grafana UI.

    • To use a certificate signed by a third-party CA:
      1. For Certificate and private key for HTTPS, provide a certificate and private key for the Grafana instance to use for TLS connections.
      2. For CA certificate for HTTPS, provide the certificate of the third-party CA that signs the certificate you provided in the previous step.
    • To generate a self-signed certificate from the Ops Manager root CA:
      1. Under Certificate and private key for HTTPS, click Change.
      2. Click Generate RSA Certificate.
      3. In the Generate RSA Certificate pop-up window, enter *.DOMAIN, where DOMAIN is the domain of the DNS entry that you configured for the Grafana instance. For example, if the DNS entry you configured for the Grafana instance is grafana.example.com, enter *.example.com. For more information about configuring a DNS entry for the Grafana instance, see Configuring DNS for the Grafana Instance.
      4. Click Generate.
      5. Navigate to the Ops Manager Installation Dashboard.
      6. From the dropdown in the upper-right corner of the Ops Manager Installation Dashboard, click Settings.
      7. Select Advanced Options.
      8. Click DOWNLOAD ROOT CA CERT.
      9. Return to the Ops Manager Installation Dashboard.
      10. Click the Healthwatch tile.
      11. Select Grafana.
      12. For Certificate and private key for HTTPS, provide the Ops Manager root CA certificate that you downloaded in a previous step.
  10. (Optional) To configure an additional cipher suite for TLS connections to the Grafana instance, enter a comma-separated list of ciphers in Additional ciphers for TLS. For a list of supported cipher suites, see cipher_suites.go in the Go repository on GitHub.

  11. Under Grafana UI authentication method, select the user authentication method you want to configure for users to log in to the Grafana UI:

  12. Under Grafana email alerts, choose whether to allow email alerts from the Grafana UI.

    • To allow email alerts:
      1. Select Configure.
      2. For SMTP server host name, enter the host name of your SMTP server.
      3. For SMTP server port, enter the port of your SMTP server.
      4. For SMTP server username, enter your SMTP authentication username.
      5. For SMTP server password, enter your SMTP authentication password.
      6. (Optional) To allow the Grafana instance to skip TLS certificate verification when communicating with your SMTP server over TLS, activate the Skip TLS certificate verification checkbox. When this checkbox is activated, the Grafana instance does not verify the identity of your SMTP server. This checkbox is deactivated by default.
      7. For From address, enter the sender email address that appears on outgoing email alerts.
      8. For From name, enter the sender name that appears on outgoing email alerts.
      9. For EHLO client ID, enter the name for the client identity that your SMTP server uses when sending EHLO commands.
      10. For Certificate and private key for TLS, enter a certificate and private key for the Grafana instance to use for TLS connections to your SMTP server.
    • To disallow email alerts, select Do not configure. Email alerts are disallowed by default.

      For more information, see the Grafana documentation.
  13. Click Save.

(Optional) Configure Canary URLs

In the Canary URLs pane, you configure target URLs to which the Blackbox Exporters in the Prometheus instance sends canary tests. Testing a canary target URL allows you to gauge the overall health and accessibility of an app, runtime, or deployment.

The Canary URLs pane configures the Blackbox Exporters in the Prometheus instance. For more information, see the Blackbox exporter repository on GitHub.

To configure the Canary URLs pane:

  1. Select Canary URLs.

  2. For Port, specify the port that the Blackbox Exporter exposes to the Prometheus instance. The default port is 9115. You do not need to specify a different port unless port 9115 is already in use on the Prometheus instance.

  3. (Optional) For Ops Manager FQDN, enter https://OPS-MANAGER-FQDN/api/v0/info, where OPS-MANAGER-FQDN is the fully-qualified domain name (FQDN) of your Ops Manager deployment. This creates a canary target URL that allows the Blackbox Exporter to test whether the Ops Manager Installation Dashboard is accessible. The results from these canary tests appear in the Ops Manager Health dashboard in the Grafana UI.

  4. (Optional) If your Ops Manager deployment uses self-signed certificates, activate the Skip TLS certificate verification checkbox. When this checkbox is activated, the Prometheus instance does not verify the identity of your Ops Manager deployment. This checkbox is deactivated by default.

  5. (Optional) Under Target URLs, you can configure canary target URLs. The Prometheus instance runs continuous canary tests to these URLs and records the results. To configure canary target URLs:

    1. Click Add.
    2. For URL, enter the URL to which you want the Prometheus instance to send canary tests. VMware recommends including apps.sys.FOUNDATION-URL if you have TAS for VMs installed, or api.pks.FOUNDATION-URL:8443 if you have TKGI installed, where FOUNDATION-URL is the root URL of your Ops Manager foundation.

      Note: The Prometheus instance automatically creates scrape jobs for these URLs. You do not need to create additional scrape jobs for them in the Prometheus pane.

  6. Click Save.

(Optional) Configure Remote Write

In the Remote Write pane, you can configure the Prometheus instance to write to remote storage, in addition to its local time series database (TSDB). Healthwatch stores monitoring data for six weeks before deleting it. Configuring remote write allows Healthwatch to store data that is older than six weeks in a remote database or storage endpoint. For a list of compatible remote databases and storage endpoints, see the Prometheus documentation.

The values that you configure in the Remote Write pane also configure their corresponding properties in the Prometheus configuration file. For more information, see Overview of Configuration Files in Healthwatch in Configuration File Reference Guide, Remote Write in Configuration File Reference Guide, and the Prometheus documentation.

To configure the Remote Write pane:

  1. Select Remote Write.

  2. Under Remote write destinations, click Add.

  3. For Remote storage URL, enter the URL for your remote storage endpoint. For example, https://REMOTE-STORAGE-FQDN, where REMOTE-STORAGE-FQDN is the FQDN of your remote storage endpoint.

  4. In Remote timeout, enter in seconds the amount of time that the Prometheus VM tries to make a request to your remote storage endpoint before the request fails.

  5. If your remote storage endpoint requires a username and password to log in to it, configure the following fields:

    1. For Remote storage username, enter the username that the Prometheus instance uses to log in to your remote storage endpoint.
    2. For Remote storage password, enter the password that the Prometheus instance uses to log in to your remote storage endpoint.
  6. (Optional) To allow the Prometheus instance to communicate with the server for your remote storage endpoint over TLS:

    1. For Certificate and private key for TLS, provide a certificate and private key for the Prometheus instance to use for TLS connections to your remote storage endpoint.
    2. For CA certificate for TLS, provide the certificate for the CA that the server for your remote storage endpoint uses to verify TLS certificates.
    3. For Remote storage server name, enter the name of the server for your remote storage endpoint as it appears on the server’s TLS certificate.
    4. If the certificate you provided in Certificate and private key for TLS is signed by a self-signed CA certificate or a certificate that is signed by a self-signed CA certificate, activate the Skip TLS certificate verification checkbox. When this checkbox is activated, the Prometheus instance does not verify the identity of the server for your remote storage endpoint. This checkbox is deactivated by default.
  7. (Optional) To allow the Prometheus instance to make HTTP or HTTPS requests to your remote storage endpoint through a proxy server, enter the URL for your proxy server in Proxy URL.

  8. You can configure more granular settings for writing to your remote storage endpoint by specifying additional parameters for the shards containing in-memory queues that read from the write-ahead log in the Prometheus instance. To configure additional parameters for these shards:

    1. For Queue capacity, enter how many samples your remote storage endpoint can queue in memory per shard before the Prometheus instance blocks the queue from reading from the write-ahead log.
    2. For Minimum shards per queue, enter the minimum number of shards the Prometheus instance can use for each remote write queue. This number is also the number of shards the Prometheus instance uses when remote write begins after each deployment of the Healthwatch tile.
    3. For Maximum shards per queue, enter the maximum number of shards the Prometheus instance can use for each remote write queue.
    4. For Maximum samples per send, enter the maximum number of samples the Prometheus instance can send to a shard at a time.
    5. For Maximum batch wait time, enter in seconds the maximum amount of time the Prometheus instance can wait before sending a batch of samples to a shard, whether that shard has reached the limit configured in Maximum samples per send or not.
    6. For Minimum backoff time, enter in milliseconds the minimum amount of time the Prometheus instance can wait before retrying a failed request to your remote storage endpoint.
    7. For Maximum backoff time, enter in milliseconds the maximum amount of time the Prometheus instance can wait before retrying a failed request to your remote storage endpoint.

      For more information about configuring these queue parameters, see the Prometheus documentation.
  9. Click Save.

Configure TKGI Cluster Discovery

In the TKGI Cluster Discovery pane, you configure TKGI cluster discovery for Healthwatch. You only need to configure this pane if you have Ops Manager foundations with TKGI installed.

To configure TKGI cluster discovery, see Configuring TKGI Cluster Discovery.

(Optional) Configure Errands

Errands are scripts that Ops Manager runs automatically when it installs or uninstalls a product, such as a new version of Healthwatch. There are two types of errands: post-deploy errands run after the product is installed, and pre-delete errands run before the product is uninstalled. However, there are no pre-delete errands for Healthwatch.

By default, Ops Manager always runs all errands.

In the Errands pane, you can select On to always run an errand or Off to never run it.

For more information about how Ops Manager manages errands, see the Ops Manager documentation.

To configure the Errands pane:

  1. Select Errands.

  2. (Optional) Choose whether to always run or never run the following errands:

    • Smoke Test Errand: Verifies that the Grafana and Prometheus instances are running.
    • Update Grafana Admin Password: Updates the admin password for the Grafana UI.
  3. Click Save.

(Optional) Configure Syslog

In the Syslog pane, you can configure system logging in Healthwatch to forward log messages from Healthwatch component VMs to an external destination for troubleshooting, such as a remote server or external syslog aggregation service.

To configure the Syslog pane:

  1. Select Syslog.

  2. Under Do you want to configure Syslog forwarding?, select one of the following options:

    • No, do not forward Syslog: Disallows syslog forwarding.
    • Yes: Allows syslog forwarding and allows you to edit the configuration fields described below.
  3. For Address, enter the IP address or DNS domain name of your external destination.

  4. For Port, enter a port on which your external destination listens.

  5. For Transport Protocol, select TCP or UDP from the dropdown. This determines which transport protocol Healthwatch uses to forward system logs to your external destination.

  6. (Optional) To transmit logs over TLS:

    1. Activate the Enable TLS checkbox. This checkbox is deactivated by default.
    2. For Permitted Peer, enter either the name or SHA1 fingerprint of the remote peer.
    3. For SSL Certificate, enter the TLS certificate for your external destination.
  7. (Optional) For Queue Size, specify the number of log messages Healthwatch can hold in a buffer at a time before sending them to your external destination. The default value is 100000.

  8. (Optional) To forward debug logs to your external destination, activate the Forward Debug Logs checkbox. This checkbox is deactivated by default.

  9. (Optional) To specify a custom syslog rule, enter it in Custom rsyslog configuration in RainerScript syntax. For more information about custom syslog rules, see the TAS for VMs documentation. For more information about RainerScript syntax, see the rsyslog documentation.

  10. Click Save Syslog Settings.

(Optional) Configure Resources

In the Resource Config pane, you can scale Healthwatch component VMs up or down according to the needs of your deployment, as well as associate load balancers with a group of VMs. For example, you can scale the persistent disk size of the Prometheus instance to allow longer data retention.

To configure the Resource Config pane:

  1. Select Resource Config.

  2. (Optional) To scale a job, select an option from the dropdown for the resource you want to modify:

    • Instances: Configures the number of instances each job has.
    • VM Type: Configures the type of VM used in each instance.
    • Persistent Disk Type: Configures the amount of persistent disk space to allocate to the job.
  3. (Optional) To add a load balancer to a job:

    1. Click the icon next to the job name.
    2. For Load Balancers, enter the name of your load balancer.
    3. Ensure that the Internet Connected checkbox is deactivated. Activating this checkbox gives VMs a public IP address that allows outbound Internet access.
  4. Click Save.

Deploy Healthwatch

To complete your installation of the Healthwatch tile:

  1. Return to the Ops Manager Installation Dashboard.

  2. Click Review Pending Changes.

  3. Click Apply Changes.

For more information, see the Ops Manager documentation.

Next Steps

After you have successfully installed the Healthwatch tile, continue to one of the following topics to configure and deploy the Healthwatch Exporter tiles for the Ops Manager foundations you want to monitor: