Contact Free trial Login

API Functional Monitoring (AFM) Release Notes

These release notes cover the following versions of this product:

1.21

May 30, 2020

This release includes these enhancements:

Enhancements to the Slack reporter

  • The look and feel of notifications are improved.

  • Each notification now includes the name of the configuration used for the test execution.

  • The three following options are added to the Slack reporter:

    SEND_NOTIFICATION_IF_PASSED

    Setting this option to true causes a notification to be sent if a test passes.

    AT_HERE_ENABLED

    Setting this option to true adds @here to a notification if a test fails.

    DISABLED_FOR_CONFIGS

    Disables the reporter for one or more configurations. The value is the name of one configuration or multiple names that are separated by commas. Names do not include the .dwl file extension.

Enhancements to the Email reporter

The two following options are added to the Email reporter:

SEND_NOTIFICATION_IF_PASSED

Setting this option to true causes the email to be sent if the tests pass

DISABLED_FOR_CONFIGS

Disables the reporter for one or more configurations. The value is the name of one configuration or multiple names that are separated by commas. Names do not include the .dwl file extension.

Enhancement to the New Relic reporter

The following option are added to the New Relic reporter:

DISABLED_FOR_CONFIGS

Disables the reporter for one or more configurations. The value is the name of one configuration or multiple names that are separated by commas. Names do not include the .dwl file extension.

Enhancement to the Sumo Logic reporter

The following option are added to the Sumo Logic reporter:

DISABLED_FOR_CONFIGS

Disables the reporter for one or more configurations. The value is the name of one configuration or multiple names that are separated by commas. Names do not include the .dwl file extension.

Enhancement to the PagerDuty reporter

The following option are added to the PagerDuty reporter:

DISABLED_FOR_CONFIGS

Disables the reporter for one or more configurations. The value is the name of one configuration or multiple names that are separated by commas. Names do not include the .dwl file extension.

Enhancements to private locations

  • Updated to use Mule Runtime 4.3.0.

  • Updated Mule app dependencies.

  • Fixed an issue that generated infinite bat test executables in Mule-app filesystems.

  • Added log appenders to enable troubleshooting in CloudHub.

1.20

February 8, 2020

This release introduces one enhancement: If you run a monitor online in Anypoint Platform (instead of through the BAT CLI), and you specify an email address for an email reporter to notify you of failed tests, each emailed report contains a link. The link opens the result of the failed test in the Functional Monitoring section of Anypoint Monitoring.

1.19

December 7, 2019

This release introduces the following two new features:

  • Integration with Anypoint Secrets Manager

    When you write tests manually and run them with the BAT CLI, you can access shared secrets in Anypoint Secrets Manager within those tests, which enables you to securely store sensitive information, such as a password, authentication token, endpoint URL, or webhook URL. You must run the tests from a private location when you use shared secrets.

  • Support for creating monitors for endpoints that use self-signed certificates

    When you create a monitor in the Anypoint Functional Monitoring section of Anypoint Monitoring, you can toggle the SSL Certificate Validation switch to off if the endpoints that your monitor will test use self-signed certificates. If they do use self-signed certificates and you do not toggle this switch off, tests against those endpoints fail.

    • If the toggle is on, all endpoints that use SSL certificates must have certificates that are signed by a trusted authority.

    • If the toggle is off, all endpoints that use SSL certificates must be self-signed.

      To test a combination of endpoints that use trusted SSL certificates and endpoints that use self-signed certificates, create two separate monitors: one for testing the first group of endpoints, the other for testing the second group of endpoints.

1.17

October 5, 2019

This release introduces private locations, which enable you to monitor private (system and process) APIs without whitelisting IP addresses. Private locations are namespaces in an instance of Anypoint Virtual Private Cloud (VPC) that is configured to allow workers to access your private network. AFM can create workers within that namespace that can run tests against APIs that are accessible only within the network that VPC is configured for. You can create multiple private locations in a single VPC.

For more information, see Monitoring the Endpoints of Private APIs.

1.16

July 27, 2019

This release introduces one new feature in the interface for Anypoint Monitoring: you can now create new tests that are based on existing tests for monitors in Anypoint Monitoring. For details, see Create a New Test from an Existing One.

1.15

June 15, 2019

This release introduces one new feature: you can now get notifications of failed tests through email. Select Email as the reporter in API Functional Monitoring in Anypoint Monitoring, or set up email as a reporter in the BAT CLI.

See Create a Monitor for instructions about using API Functional Monitoring in Anypoint Monitoring, and see To Configure and View Test Reports for details about creating reporters in the BAT CLI.

1.1

July 12, 2018

This release introduces an enhancement and a new feature.

Enhancement

When you create a monitor in the Functional Monitoring section of Anypoint Monitoring, you can now specify more than one endpoint to test and more than one assertion per endpoint.

New Feature

You can write and run BAT tests in IntelliJ IDEA with the support of the DataWeave 2.0 IntelliJ plugin. For details, see Write and Run BAT Tests in IntelliJ IDEA.

1.0

This release introduces a new user interface that is incorporated into Anypoint Monitoring. To access this user interface, select Functional Monitoring after opening Anypoint Monitoring.

For documentation about this new user interface, see API Functional Monitoring in Anypoint Monitoring.

You can still create tests and schedule them using the BDD Test-Writing Language and the Blackbox Automated Testing (BAT) CLI. The documentation for doing that is located at API Functional Monitoring with the Blackbox Automated Testing (BAT) CLI.

Was this article helpful?

💙 Thanks for your feedback!