Release Notes for Event Alerts

Page last updated:

For product versions and upgrade paths, see Upgrade Planner.

v1.2.12

Release Date: May 14, 2021

Resolved Issues

This release has the following fix:

  • The Deploy Event Alerts errand runs successfully for all TLS settings: Event Alerts no longer fails to connect to its provisioned backing database when TLS Options is set to any value other than Not Configured in the Security pane of the Tanzu SQL for VMs v2.10 tile.

Known Issues

This release has the following issues:

  • If you have binary logging enabled, the Deploy 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.
    To resolve this issue, see Deploy Event Alerts Errand Fails Due to Binary Logging in Monitoring and Troubleshooting Event Alerts.
  • 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.11

Release Date: December 7, 2020

Features

Change in this release:

  • Maintenance update: Product stemcell updated to Ubuntu Xenial v621.x.

Known Issues

This release has the following issues:

  • If you have VMware Tanzu™ SQL with MySQL for VMs (Tanzu SQL for VMs) v2.10 installed and TLS Options is set to any value other than Not Configured in the Security pane of the Tanzu SQL for VMs tile, then the Deploy Event Alerts errand fails with an error similar to the following example:

    ERROR:
    Unable to obtain connection from database (jdbc://example.com) for user 'migrations_user': Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    SQL State  : 08S01
    Error Code : 0
    Message    : Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    

    To resolve this issue, see Deploy Event Alerts Errand Fails Due to Communications Link Failure.

  • If you have binary logging enabled, the Deploy 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.
    To resolve this issue, see Deploy Event Alerts Errand Fails Due to Binary Logging in Monitoring and Troubleshooting Event Alerts.
  • 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.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 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.

Resolved Issues

This release fixes the following issue:

  • no longer fails to emit from App Metrics and Metric Forwarder on VMware Tanzu Application Service for VMs v2.5 and later.
  • 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 VMware Tanzu™ SQL with MySQL for VMs (Tanzu SQL for VMs) v2.10 installed and TLS Options is set to any value other than Not Configured in the Security pane of the Tanzu SQL for VMs tile, then the Deploy Event Alerts errand fails with an error similar to the following example:

    ERROR:
    Unable to obtain connection from database (jdbc://example.com) for user 'migrations_user': Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    SQL State  : 08S01
    Error Code : 0
    Message    : Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    

    To resolve this issue, see Deploy Event Alerts Errand Fails Due to Communications Link Failure.

  • If you have binary logging enabled, the Deploy 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.
    To resolve this issue, see Deploy Event Alerts Errand Fails Due to Binary Logging in Monitoring and Troubleshooting Event Alerts.
  • 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 Event Alerts for Pivotal Cloud Foundry to Event Alerts in the tile.

Known Issues

This release has the following issues:

  • If you have VMware Tanzu™ SQL with MySQL for VMs (Tanzu SQL for VMs) v2.10 installed and TLS Options is set to any value other than Not Configured in the Security pane of the Tanzu SQL for VMs tile, then the Deploy Event Alerts errand fails with an error similar to the following example:

    ERROR:
    Unable to obtain connection from database (jdbc://example.com) for user 'migrations_user': Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    SQL State  : 08S01
    Error Code : 0
    Message    : Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    

    To resolve this issue, see Deploy Event Alerts Errand Fails Due to Communications Link Failure.

  • If you have binary logging enabled, the Deploy 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.
    To resolve this issue, see Deploy Event Alerts Errand Fails Due to Binary Logging in Monitoring and Troubleshooting Event Alerts.
  • 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.
  • Event Alerts fails to emit custom metrics on VMware Tanzu Application Service for VMs v2.5 and later.
  • 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 VMware Tanzu™ SQL with MySQL for VMs (Tanzu SQL for VMs) v2.10 installed and TLS Options is set to any value other than Not Configured in the Security pane of the Tanzu SQL for VMs tile, then the Deploy Event Alerts errand fails with an error similar to the following example:

    ERROR:
    Unable to obtain connection from database (jdbc://example.com) for user 'migrations_user': Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    SQL State  : 08S01
    Error Code : 0
    Message    : Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    

    To resolve this issue, see Deploy Event Alerts Errand Fails Due to Communications Link Failure.

  • If you have binary logging enabled, the Deploy 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.
    To resolve this issue, see Deploy Event Alerts Errand Fails Due to Binary Logging in Monitoring and Troubleshooting Event Alerts.
  • 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.
  • Event Alerts fails to emit custom metrics on VMware Tanzu Application Service for VMs v2.5 and later.
  • 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 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 VMware Tanzu™ SQL with MySQL for VMs (Tanzu SQL for VMs) v2.10 installed and TLS Options is set to any value other than Not Configured in the Security pane of the Tanzu SQL for VMs tile, then the Deploy Event Alerts errand fails with an error similar to the following example:

    ERROR:
    Unable to obtain connection from database (jdbc://example.com) for user 'migrations_user': Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    SQL State  : 08S01
    Error Code : 0
    Message    : Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    

    To resolve this issue, see Deploy Event Alerts Errand Fails Due to Communications Link Failure.

  • If you have binary logging enabled, the Deploy 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.
    To resolve this issue, see Deploy Event Alerts Errand Fails Due to Binary Logging in Monitoring and Troubleshooting Event Alerts.
  • 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.
  • Event Alerts fails to emit custom metrics on VMware Tanzu Application Service for VMs v2.5 and later.
  • 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:

  • If you have VMware Tanzu™ SQL with MySQL for VMs (Tanzu SQL for VMs) v2.10 installed and TLS Options is set to any value other than Not Configured in the Security pane of the Tanzu SQL for VMs tile, then the Deploy Event Alerts errand fails with an error similar to the following example:

    ERROR:
    Unable to obtain connection from database (jdbc://example.com) for user 'migrations_user': Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    SQL State  : 08S01
    Error Code : 0
    Message    : Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    

    To resolve this issue, see Deploy Event Alerts Errand Fails Due to Communications Link Failure.

  • 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.
  • Event Alerts fails to emit custom metrics on VMware Tanzu Application Service for VMs v2.5 and later.
  • 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.

Resolved 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:

  • If you have VMware Tanzu™ SQL with MySQL for VMs (Tanzu SQL for VMs) v2.10 installed and TLS Options is set to any value other than Not Configured in the Security pane of the Tanzu SQL for VMs tile, then the Deploy Event Alerts errand fails with an error similar to the following example:

    ERROR:
    Unable to obtain connection from database (jdbc://example.com) for user 'migrations_user': Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    SQL State  : 08S01
    Error Code : 0
    Message    : Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    

    To resolve this issue, see Deploy Event Alerts Errand Fails Due to Communications Link Failure.

  • 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.
  • Event Alerts fails to emit custom metrics on VMware Tanzu Application Service for VMs v2.5 and later.
  • 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 Stemcell Library before deploying Event Alerts. Any automation you have set up to update your Event Alerts deployments using Trusty stemcells might break.

Resolved 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:

  • If you have VMware Tanzu™ SQL with MySQL for VMs (Tanzu SQL for VMs) v2.10 installed and TLS Options is set to any value other than Not Configured in the Security pane of the Tanzu SQL for VMs tile, then the Deploy Event Alerts errand fails with an error similar to the following example:

    ERROR:
    Unable to obtain connection from database (jdbc://example.com) for user 'migrations_user': Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    SQL State  : 08S01
    Error Code : 0
    Message    : Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    

    To resolve this issue, see Deploy Event Alerts Errand Fails Due to Communications Link Failure.

  • 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.
  • Event Alerts fails to emit custom metrics on VMware Tanzu Application Service for VMs v2.5 and later.
  • 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 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:

  • If you have VMware Tanzu™ SQL with MySQL for VMs (Tanzu SQL for VMs) v2.10 installed and TLS Options is set to any value other than Not Configured in the Security pane of the Tanzu SQL for VMs tile, then the Deploy Event Alerts errand fails with an error similar to the following example:

    ERROR:
    Unable to obtain connection from database (jdbc://example.com) for user 'migrations_user': Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    SQL State  : 08S01
    Error Code : 0
    Message    : Communications link failure
    
    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    

    To resolve this issue, see Deploy Event Alerts Errand Fails Due to Communications Link Failure.

  • 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.
  • Event Alerts fails to emit custom metrics on VMware Tanzu Application Service for VMs v2.5 and later.
  • 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.