Release Notes for Pivotal Event Alerts

Page last updated:

Note: Pivotal has renamed Pivotal Cloud Foundry Event Alerts to Pivotal Event Alerts.

Note: Pivotal has renamed Pivotal Cloud Foundry to Pivotal Platform.

v1.2.10

Release Date: January 17, 2020

Features

New features and changes in this release:

  • Removes the requirement that Slack webhook URLs contain slack.com. This enables admins to create Slack targets with webhooks from other messaging platforms. For instructions for creating Slack targets, see Create Slack Targets.
  • Adds support for Metric Registrar. This enables Pivotal Event Alerts to emit custom app metrics in a structured log format. To use this service, you must install the plugin and register the event-alerts app as a JSON metrics source. For instructions, see Install the Plugin and Register a Structured Log Format in Using Metric Registrar.

Fixed Issues

This release fixes the following issue:

  • Pivotal Event Alerts no longer fails to emit from App Metrics and Metric Forwarder on Pivotal Application Service v2.5 and later.
  • Pivotal Event Alerts no longer fails to connect to an external MySQL database when the username or password for the database contains special characters.

Known Issues

This release has the following issues:

  • If you have binary logging enabled, the Deploy Pivotal Event Alerts errand fails when log_bin_trust_function_creators is not set to 1. If you do not resolve this issue, Event Alerts is not deployed. For instructions on solving this issue, see Deploy Event Alerts Errand Fails.
  • When saving the MySQL settings page with Azure-style usernames, for example, userId@serverName, you might see an error message saying use of the @ character is not supported. Disregard this message. You are still able to authenticate.

v1.2.9

Release Date: November 5, 2019

Features

New features and changes in this release:

  • This release updates the product name from Pivotal Cloud Foundry Event Alerts to Pivotal Event Alerts in the tile.

Known Issues

This release has the following issues:

  • If you have binary logging enabled, the Deploy Pivotal Event Alerts errand fails when log_bin_trust_function_creators is not set to 1. If you do not resolve this issue, Event Alerts is not deployed. For instructions on solving this issue, see Deploy Event Alerts Errand Fails.
  • When saving the MySQL settings page with Azure-style usernames, for example, userId@serverName, you might see an error message saying use of the @ character is not supported. Disregard this message. You are still able to authenticate.
  • Pivotal Event Alerts fails to emit custom metrics on Pivotal Application Service v2.5 and later.
  • Pivotal Event Alerts cannot connect to an external MySQL database when a username or password for the database contains special characters.

v1.2.8

Release Date: July 2, 2019

Features

New features and changes in this release:

  • cf CLI is now v6.45.0
  • Go is now v1.12

Known Issues

This release has the following issues:

  • If you have binary logging enabled, the Deploy Pivotal Event Alerts errand fails when log_bin_trust_function_creators is not set to 1. If you do not resolve this issue, Event Alerts is not deployed. For instructions on solving this issue, see Deploy Event Alerts Errand Fails.
  • When saving the MySQL settings page with Azure-style usernames, for example, userId@serverName, you might see an error message saying use of the @ character is not supported. Disregard this message. You are still able to authenticate.
  • Pivotal Event Alerts fails to emit custom metrics on Pivotal Application Service v2.5 and later.
  • Pivotal Event Alerts cannot connect to an external MySQL database when a username or password for the database contains special characters.

v1.2.7

Release Date: May 30, 2019

Features

New features and changes in this release:

  • Adds support for proxy settings. For more information about configuring proxy settings, see Configuring Proxy Settings for All Applications .
  • Improves log error messages when alerts fail to send.
  • Adds option to disable Pivotal Metrics Forwarder integration.
  • Adds support for disabling SMTP TLS. For more information, see Configure Email Notifications
  • If you subscribed to -all topics, you can selectively unsubscribe from individual topics. You can also selectively subscribe to individual topics. For more information, see Unsubscribe from Alert Topics and Subscribe to Alert Topics.
  • Maintenance update of the following product dependencies:
    • cf CLI is now v6.44.1

Known Issues

This release has the following issues:

  • If you have binary logging enabled, the Deploy Pivotal Event Alerts errand fails when log_bin_trust_function_creators is not set to 1. If you do not resolve this issue, Event Alerts is not deployed. For instructions on solving this issue, see Deploy Event Alerts Errand Fails.
  • When saving the MySQL settings page with Azure-style usernames, for example, userId@serverName, you might see an error message saying use of the @ character is not supported. Disregard this message. You are still able to authenticate.
  • Pivotal Event Alerts fails to emit custom metrics on Pivotal Application Service v2.5 and later.
  • Pivotal Event Alerts cannot connect to an external MySQL database when a username or password for the database contains special characters.

v1.2.6

Release Date: December 7, 2018

Features

New features and changes in this release:

  • Maintenance update of the following product dependencies:
    • Flyway Command-line is now v5.2.1
    • Go is now v1.11
    • cf CLI is now v6.40.1

Known Issues

This release has the following issues:

  • When saving the MySQL settings page with Azure-style usernames, for example, userId@serverName, you might see an error message saying use of the @ character is not supported. Disregard this message. You are still able to authenticate.
  • Pivotal Event Alerts fails to emit custom metrics on Pivotal Application Service v2.5 and later.
  • Pivotal Event Alerts cannot connect to an external MySQL database when a username or password for the database contains special characters.

v1.2.5

Release Date: October 4, 2018

Features

Change in this release:

  • Event Alerts now uses cflinuxfs3 as the default stack when available.

    cflinuxfs2 is used when Event Alerts is installed on an environment that does not have cflinuxfs3, for example, a PCF v2.2 environment.

Fixed Issues

This release fixes the following issues:

  • In earlier versions of Event Alerts, the tile version in the tile metadata did not match the version of Event Alerts. The version numbers now match.

  • This version of Event Alerts supports using BOSH DNS in conjunction with the IPsec Add-on for PCF when using an internal database.

Known Issues

This release has the following issues:

  • When saving the MySQL settings page with Azure-style usernames, for example, userId@serverName, you might see an error message saying use of the @ character is not supported. Disregard this message. You are still able to authenticate.
  • Pivotal Event Alerts fails to emit custom metrics on Pivotal Application Service v2.5 and later.
  • Pivotal Event Alerts cannot connect to an external MySQL database when a username or password for the database contains special characters.

v1.2.3

Release Date: September 6, 2018

Features

New features and changes in this release:

  • Added support for SMTP servers without authentication. Credentials are no longer required when configuring SMTP server settings. To connect to a SMTP server without authentication, leave the SMTP username and password fields empty.

  • Escape characters are no longer required in configuration passwords.

  • Maintenance update of the following product dependencies:

    • Flyway Command-line is now v5.1.4
    • Go is now v1.10.3
    • Product stemcell is now Ubuntu Xenial v97.x
  • Before using Event Alerts v1.2.3, you must update any BOSH add-ons to support Xenial stemcells. For more information, see Prerequisites.

    Breaking Change: Event Alerts v1.2.3 and later require a Xenial stemcell. You must manually download and import a new stemcell into the Pivotal Ops Manager Stemcell Library before deploying Event Alerts. Any automation you have set up to update your Event Alerts deployments using Trusty stemcells might break.

Fixed Issues

This release fixes the following issue:

  • External Azure MySQL databases and other cases where usernames contain the @ symbol are now supported.

Known Issues

This release has the following issues:

  • When saving the MySQL settings page with Azure-style usernames, for example, userId@serverName, you might see an error message saying use of the @ character is not supported. Disregard this message. You are still able to authenticate.
  • When using Event Alerts and BOSH DNS in conjunction with IPSec Add-On for PCF and an internal database, Event Alerts do not function. This issue is fixed in Event Alerts v1.2.5.
  • The tile version in the tile metadata might not match the version of Event Alerts. These version numbers are aligned as of Event Alerts v1.2.5.
  • Pivotal Event Alerts fails to emit custom metrics on Pivotal Application Service v2.5 and later.
  • Pivotal Event Alerts cannot connect to an external MySQL database when a username or password for the database contains special characters.

v1.2.1

Release Date: July 17, 2018

Features

New features and changes in this release:

  • To view Healthwatch topics, you must have Pivotal Healthwatch v1.3 installed.

  • Dependence on notifications has been removed.

  • Email configuration is now an option.

    Note: Specifying email configuration settings is required if you want notifications sent by email.

    For more information, see Configure Email Notifications.

  • All destination email addresses now receive validation messages. Before v1.2.1, if the notification email address was the same as the account creating the target, the email address was verified automatically.

Known Issues

This release has the following issues:

  • Users of Event Alerts v1.2.1 are required to use escape characters in configuration passwords. This is no longer required in Event Alerts v1.2.3 and later releases.
  • When saving the MySQL settings page with Azure-style usernames, for example, userId@serverName, you might see an error message saying use of the @ character is not supported. Disregard this message. You are still able to authenticate.
  • The tile version in the tile metadata might not match the version of Event Alerts. These version numbers are aligned as of Event Alerts v1.2.5.
  • Pivotal Event Alerts fails to emit custom metrics on Pivotal Application Service v2.5 and later.
  • Pivotal Event Alerts cannot connect to an external MySQL database when a username or password for the database contains special characters.

View Release Notes for Another Version

To view the release notes for another product version, select the version from the dropdown at the top of this page.