LATEST VERSION: 1.2 - CHANGELOG
PCF Healthwatch v1.1

PCF Healthwatch Resources

This topic describes resource requirements for Pivotal Cloud Foundry (PCF) Healthwatch.

PCF Healthwatch Tile

You can configure PCF Healthwatch resources in the Resource Config section of the PCF Healthwatch tile. By default, PCF Healthwatch automatically selects the instance type that is best suited for each job.

Note: The automatically selected values that you see in the Resource Config section of the PCF Healthwatch tile depend on the available resources for your PCF deployment.

The following table provides the default resource and IP requirements for installing the PCF Healthwatch tile.

Resource Instances CPU RAM Ephemeral Disk Persistent Disk Static IP Dynamic IP
Healthwatch Forwarder 1 (not configurable) 4 16 GB 32 GB 100 GB 1 0
MySQL Server 3 8 16 GB 32 GB 100 GB 3 0
MySQL Proxy 2 2 4 GB 32 GB n/a 2 0

PCF Healthwatch Functional Apps

The following table provides the default memory usage and instance count for the PCF-pushed applications in a highly available configuration. If you do not need high-availability, you can scaled down these instance counts.

Application Instances RAM Disk
bosh-health-check 1 64 MB 1 GB
bosh-task-check 2 64 MB 1 GB
canary-health-check 2 64 MB 1 GB
cf-health-check 2 500 MB 1 GB
healthwatch 2 4 GB 1 GB
healthwatch 2 4 GB 1 GB
healthwatch-aggregator 1 1 GB 1 GB
healthwatch-ingestor 4 256 MB 1 GB
healthwatch-meta-monitor 1 64 MB 1 GB
opsmanager-health-check 2 64 MB 1 GB
ui-health-check 1 64 MB 1 GB

Note: This table lists application resource usages for steady-state. During blue-green deployments, resource usage can potentially double.

If you want to scale the functional apps created by PCF Healthwatch, see the following recommendations:

  • BOSH Director health check (the bosh-health-check app). Only 1 BOSH Director Health Check can run at a time. This should be considered a hard limit.
  • BOSH deployment task check (the bosh-task-check app). By default, this is scaled to 2. It is recommended not to exceed 3-5 runners at once.
  • CLI command health check (the cf-health-check app). By default, this is scaled to 2. It is recommended not to exceed 3-5 runners at once.
  • Canary app uptime and response check (the canaryapp-health-check app). By default, this is scaled to 2. It is recommended not to exceed 3-5 runners at once.
  • Ops Manager uptime check (the opsmanager-health-check app). By default, this is scaled to 2. It is recommended not to exceed 3-5 runners at once.
  • PCF Healthwatch self-monitor and reporting (the healthwatch-meta-monitor app). This application should not need to be scaled.
Create a pull request or raise an issue on the source for this page in GitHub