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 2 4 8 GB 30 GB 100 GB 0 1
MySQL Server 1 8 15 GB 30 GB 100 GB 0 1
Redis 1 4 15 GB 30 GB 100 GB 0 1

PCF Healthwatch Functional Apps

The following table provides the default memory usage and instance count for the CF pushed applications in a highly available configuration. If not striving for HA, these instance counts can be scaled down.

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-api 2 1 GB 1 GB
healthwatch-worker 4 1 GB 1 GB
healthwatch-alerts 1 1 GB 1 GB
healthwatch-aggregator 1 1 GB 1 GB
healthwatch-ingestor 2 1 GB 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: These are the application resource usages for steady-state. During deployments the resource usage can potentially double when doing blue-green deployments.

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. For more information, see Monitoring PCF Healthwatch.
  • Redis worker (the healthwatch-worker app). By default, this is scaled to 4. To install the Healthwatch tile, see the Configure the PCF Healthwatch Tile section of the Installing and Configuring PCF Healthwatch topic.
  • Ingestor (the healthwatch-ingestor app). By default, this is scaled to 2. To install the Healthwatch tile, see the Configure the PCF Healthwatch Tile section of the Installing and Configuring PCF Healthwatch topic.