Installing PCF Metrics
This document describes how to install and configure Pivotal Cloud Foundry (PCF) Metrics.
For information about the components deployed as part of this install procedure, see the PCF Metrics Product Architecture topic.
- Ensure that you have installed the Elastic Runtime Tile.
- Ensure that you have installed v1.6 or later of the Redis tile.
- If you are running PCF on AWS, then ensure that, in Elastic Runtime, you have changed the Loggregator Port to
4443from its value of
- If you are running PCF on Google Cloud Platform (GCP), then do the following to configure the DNS entries to
accommodate web sockets:
- Log in to the GCP console.
- In the menu, navigate to the Networking tab and click Load Balancing.
- Find the load balancer that corresponds to
- Record the IP address.
- Click Cloud DNS, then click ENVIRONMENT-zone.
- Click Add Record Set.
- Enter a DNS name for mysql-logqueue. The DNS name should be
mysql-logqueue.SYSTEM_DOMAIN. Refer to your ERT Tile’s configuration of the System Domain under the Domains configuration section.
- In the IPv4 address field, enter the IP address of the load balancer that you recorded in Step 4.
- Leave the other fields as default.
- Repeat Steps 6–9 twice to create DNS records for elasticsearch-logqueue (
elasticsearch-logqueue.SYSTEM_DOMAIN) and metrics (
Note: PCF Metrics should be installed on the same network as the Elastic Runtime Tile.
- Download the PCF Metrics file from Pivotal Network.
- Upload the PCF Metrics file to your Ops Manager installation.
- Click Add next to the uploaded product description in the Available Products view to add PCF Metrics to your Installation Dashboard.
Note: The following procedures offer a standard configuration. To customize PCF Metrics for high capacity, see the Sizing PCF Metrics For Your System topic.
From the Installation Dashboard, click the PCF Metrics tile.
Assign Availability Zones (AZs) and Networks.
- Click Assign AZs and Networks.
- Select an Availability Zone under Place singleton jobs.
Ops Manager runs Metrics jobs with a single instance in this Availability Zone.
- Select one or more Availability Zones under Balance other jobs.
Ops Manager balances instances of Metrics jobs with more than one instance across the Availability Zones that you specify.
- Use the drop-down menu to select a network.
- Click Save.
Data Services Ports
For reference, the following table shows the port associated with each data service.
- Click MySQL Alerts.
- Set the Email value. Alerts for issues storing metrics into the MySQL cluster will be sent to this email address.
- Click Data Store.
- Review the Elastic Search Heap Size value. Elastic Search memory allocation for Heap use. Set to 50% of the memory allocated to the smallest of the Elasticsearch instances in Resource Config or 31GB, whichever is smaller. Use a unit of M for megabytes or G for gigabytes.
- Review the MySQL InnoDB Buffer Size value. Number of bytes for MySQL to use with memory allocation of InnoDB buffer. Set to 80% of the memory allocated to the MySQL instances in Resource Config. This does not take a unit, please provide the value in bytes.
- Review the MySQL Logqueue Count value. You can increase this instance count at any time to accommodate higher levels of inbound metrics traffic.
- Review the Elasticsearch Logqueue Count value. You can increase this instance count at any time to accommodate higher levels of inbound log traffic.
- Review the Ingestor Count value. You can increase this instance count at any time to accommodate higher levels of Loggregator Firehose traffic.
- Click Save.
- Click Errands.
Note: The PCF Metrics tile selects all Post-Deploy Errands by default. Pivotal recommends that you do not deselect any errands as doing so can cause issues with the deployment of the tile. However, you can deselect the Remove Legacy PCF Metrics CF Resources errand after deploying v1.2 of the tile.
- Review the Post-Deploy Errands and Pre-Delete Errands:
- If this is the first deployment of the tile, all Post-Deploy Errands must be selected.
- If you deselect the Remove PCF Metrics 1.2 CF Resources checkbox, artifacts may remain after the PCF Metrics tile uninstalls.
- The following list describes what the Smoke tests errand does. See the Smoke Test Errors section of the Troubleshooting PCF Metrics topic for information on resolving errors discovered by this errand.
- Confirms that MySQL ingests metrics
- Confirms that Elasticsearch ingests logs
- Confirms that the APIs return metrics and logs
- Click Resource Config.
Review the resource configurations. By default, the settings match the instance types that are best suited for each job. For reference, the following table shows the default resource and IP requirements for installing the PCF Metrics tile:
Resource Instances Persistent CPU RAM Ephemeral Static IP Dynamic IP Elasticsearch Master 3 10 GB 4 16 GB 32 GB 3 0 Elasticsearch Coordinator 2 1 GB 2 16 GB 32 GB 1 0 Elasticsearch Data 4 100 GB 2 16 GB 32 GB 4 0 MySQL Server 2 100 GB 2 16 GB 32 GB 3 0 MySQL Proxy 2 n/a 2 16 GB 32 GB 2 0 MySQL Monitor 1 (not configurable) n/a 2 16 GB 32 GB 0 1 Metron 1 (not configurable) n/a 2 4 GB 32 GB 1 0
If you expect a high level of use, you may need to increase the disk resources available to your instances.
Note: There have been issues with the Ops Manager Bosh Director correctly partitioning persistent disks larger than 2 TB.
- Navigate to Pivotal Network and click Stemcells.
- Download the appropriate stemcell version for your IaaS.
Note: On AWS make sure to use a HVM stemcell if you are using the default instance sizes.
- Click Import Stemcell and select the stemcell file you downloaded.
Click Apply Changes to install the service. If the smoke tests fail, see the Troubleshoot Smoke Test Errors section of the Troubleshooting PCF Metrics topic.
Review the Using PCF Metrics topic for more information on how to log in, use, and interpret data from PCF Metrics.