LATEST VERSION: 1.4 - RELEASE NOTES
PCF Metrics v1.2

PCF Metrics Release Notes and Known Issues

v1.2.11

Release Date: July 12, 2017

Notes

The following list describes what’s new in PCF Metrics v1.2.11:

  • MySQL Upgrade: PCF Metrics v1.2.11 now uses v32.9 of the MySQL release.

Known Issues

See the Known Issues section for the previous release.

v1.2.10

Release Date: June 6, 2017

Notes

The following list describes what’s new in PCF Metrics v1.2.10:

  • Stemcell Bump: PCF Metrics v1.2.10 includes a major stemcell bump from 3263.x to 3363.x.

Known Issues

See the Known Issues section for the previous release.

v1.2.9

Release Date: April 14, 2017

Notes

The following list describes what’s new in PCF Metrics v1.2.9:

  • Internetless Installations: PCF Metrics v1.2.9 removes multiple unnecessary dependencies that prevented the tile from being installed in an internetless environment.
  • Reduced MySQL Disk Usage: Raw data in MySQL is now pruned after 2 days, greatly reducing the amount of disk space required to store metrics in MySQL.

Known Issues

See the Known Issues section for the previous release.

v1.2.8

Release Date: April 7, 2017

Note: You may run into smoke test failures when installing this tile. Consider upgrading to our newest patch, v1.2.9, which is more stable

Notes

The following list describes what’s new in PCF Metrics v1.2.8:

  • Elasticsearch Resource Reduction: PCF Metrics v1.2.8 reduces VMs used by removing the Elasticsearch Coordinator job and allowing configuration of Elasticsearch Master node count.
  • Simplified Tile Configuration: Removed redundant Elasticsearch Heap Size property from OpsMan tile config.
  • Internetless Installations: Removed multiple unnecessary dependencies that prevented the tile from being installed in an internetless environment.
  • Reduced MySQL Disk Usage: Raw data in MySQL is now pruned after 2 days, greatly reducing the amount of disk space required to store metrics in MySQL.

Known Issues

See the Known Issues section for the previous release.

v1.2.7

Release Date: Feb 09 2017

Notes

  • Metrics works in PCF environment with certificates signed by custom CA

Known Issues

See the Known Issues section for the previous release.

v1.2.6

Release Date: January 27 2017

Notes

  • Includes a cli patch that resolves tile install failure due to resorce matching timeouts
  • Enabled the rejoin-unsafe errand for MySQL

Known Issues

See the Known Issues section for the previous release.

v1.2.5

Release Date: January 13 2017

Notes

  • Addresses conflict between mysql and metrics which caused mysql monitoring to fail intermittently
  • Upgraded to new mysql release which stabilizes metrics tile upgrades

Known Issues

See the Known Issues section for the previous release.

v1.2.4

Release Date: January 10 2017

Notes

  • Addresses a redis alpha version dependency bug

Known Issues

See the Known Issues section for the previous release.

v1.2.3

Release Date: December 16 2016

Notes

  • Enables installs for internetless environments
  • Optimize MySQL disk usage by reducing bin log retention
  • Added MySQL and ES configuration changes to improve the stability of cluster during restarts
  • Fixed an integration issue with Apps manager that restores link to metrics

Known Issues

See the Known Issues section for the previous release.

v1.2.1

Release Date: November 29 2016

Notes

The following sections describe what’s new in PCF Metrics v1.2.1.

New Requirements and Configurations

PCF Metrics v1.2.1 requires the Redis tile v1.6 or later.

Consider the following updates when configuring and deploying PCF Metrics v1.2.1:

  • MySQL Alerts: You can now specify an email address that receives alerts from PCF Metrics about MySQL storage issues. See the MySQL Alerts section of the Installing PCF Metrics topic for more information.
  • Data Store: You can now configure additional properties in the Data Store pane. See the Data Store section of the Installing PCF Metrics topic for more information.
  • Errands: The tile includes new errands. See the Errands section of the Installing PCF Metrics topic for more information.
  • Resource Config: See the Increased Data Persistence section below to learn about updates affecting this configuration pane.
  • Stemcell: This release uses stemcell v3263.

Increased Data Persistence

PCF Metrics v1.2.1 increases the retention period for log, metric, and event data to two weeks. To support this increase, PCF Metrics v1.2.1 includes the following component updates:

  • Log datastore: The default size of the Elasticsearch cluster is now nine VMs instead of three.
  • Metrics datastore: The tile stores metrics data in MySQL instead of IMDS and increases the default number of metrics storage VMs to seven instead of five to support higher capacity and introduce high availability.
  • All VMs: The default persistent disk usage is ten times greater than in v1.1.x.

See the Sizing PCF Metrics for Your System topic for updated guidance and the PCF Metrics Product Architecture topic for an updated explanation of the components.

Improved UI

PCF Metrics v1.2.1 improves the user experience by removing the Dashboard screen and replacing it with an enhanced Explore screen. The following list describes how PCF Metrics v1.2.1 further refines its UI. To view the UI and understand the new functionality, see the Using PCF Metrics topic.

  • Viewing historical data: You can now view data for the past two weeks.
  • Monitoring app events: The new Events view displays all start, stop, crash, and update events.
  • Searching Logs: The Logs view now includes a histogram that displays log frequency for the current time frame. The histogram updates based on your search results. You can also download your logs.
  • Setting the time frame: PCF Metrics v1.2.1 improves time frame selection.

Known Issues

The following sections describe the known issues in PCF Metrics v1.2.1.

Compatibility with Elastic Runtime

PCF Metrics v1.2.x requires Elastic Runtime v1.8.9 or later.

Data Loss when Upgrading from v1.1 to v1.2

The upgrade process from v1.1 to v1.2 acts in the following sequence:

  1. Removes the data storage components of v1.1
  2. Deploys v1.2 data storage and ingestion components

The upgrade process does not save any v1.1 data and the new components do not begin ingesting and storing log or metrics data until they successfully deploy.

Data Loss during Stemcell Upgrades

The Elasticsearch cluster updates when PCF Metrics applies a new stemcell, which causes decreased log ingestion and, consequently, the loss of logs. Some storage occurs during this time because canary deployed nodes can intake some of the load from firehose. Ingestion reduction may vary depending on deployment size, but you can expect some loss.

In testing, the Elasticsearch cluster took approximately five minutes to update and experienced between a 40% and 60% reduction in logs ingested and stored.

Smoke Test Failure

The PCF Metrics Smoke Test errand may fail if your deployment authenticates user sign-ons with an external SAML identity provider or an external LDAP server. In some cases, these external user stores have an additional login procedure that prevents the errand from authenticating with the deployment and validating against the Metrics API.

If you experience this issue, disable the Smoke Test errand in the PCF Metrics tile and click Apply Changes to run the install again.

See the Configure Authentication and Enterprise SSO section of the Configuring Elastic Runtime topic for more information on what configurations can lead to this failure.

For Operators who Deploy PCF Metrics using BOSH

If both of the following are true, you may experience issues while using PCF Metrics:

  • You deploy PCF Metrics using BOSH instead of using the PCF Metrics tile in Ops Manager.
  • You use self-signed certificates.

Pivotal recommends using certificates issued by a Certificate Authority for BOSH deployments of this product.

Past Minor v1.1.x

Release Notes for v1.1.x releases can be found here

Past Minor v1.0.x

Release Notes for v1.0.x releases can be found here

Create a pull request or raise an issue on the source for this page in GitHub