PCF Healthwatch Resources
Warning: PCF Healthwatch v1.6 is no longer supported or available for download. PCF Healthwatch v1.6 has reached the End of General Support (EOGS) phase as defined by the Support Lifecycle Policy. To stay up to date with the latest software and security updates, upgrade to a supported version.
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 apps pushed to your deployment by PCF Healthwatch. PCF Healthwatch is highly available by default. If you do not require high availability, you can scale down these instance counts.
Note: The data in this table assumes PCF Healthwatch is in a steady-state. During deployments, resource usage can potentially double because PCF Healthwatch deploys the apps using the blue-green method.
| 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 | 1 | 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 |
If you want to scale the functional apps created by PCF Healthwatch, see the following recommendations:
- BOSH Director health check (the
bosh-health-checkapp). 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-checkapp). 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-checkapp). 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-checkapp). 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-checkapp). 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-monitorapp). This application should not need to be scaled.