Cloud Blog

Alerts on API performance and subscriber behavior

Do you want to be alerted when your API is down? Or when one of your subscribers starts behaving suspiciously invoking the API from a different IP address or in an unusual pattern?

All of this is now easy with WSO2 API Cloud!

Alerts can be configured on two levels: publisher and organization administrator.

The following alerts are available:

You can follow the links above for details on how each of them works.

To configure alerts on the publisher level:

  1. In API Cloud’s left-hand menu, click Manage Alert Types,
  2. Select the alerts that you want to receive,
  3. Specify the email addresses (press Enter after typing each address),
  4. Click Save:


To configure alerts on the organization admin level:

  1. In API Cloud’s Configure menu, click Admin Dashboard,
  2. In Admin Portal’s left-hand menu, click Analytics / Manage Alert Types,
  3. Select the alerts that you want to receive,
  4. Specify the recipient email addresses,
  5. Click Save:


ESB-as-a-Service now available in App Cloud

You can now host your proxy services and integration projects right within WSO2 Integration Cloud (formerly known as App Cloud).

To do that, simply:

1. Export your WSO2 ESB project as a CAR file from WSO2 Dev Studio.

2. In WSO2 App Cloud, click Create Application.

3. Select WSO2 ESB Composite Application as the type:


4. Give it a name and upload the CAR file.

See our documentation for details: Deploy a Sample Integration Application.

New API Cloud Reports

We have significantly expanded off-the-shelf reports available in API Cloud:

Statistics tab in the Publisher interface now has 16 reports including both new and revamped old ones:

  • Reports now have a nice date picker and give the ability to compare behavior between API versions: for example, you can see whether API performance improved or degraded with the rollout of the new version,
  • API Latency report shows where exactly your API processing time is spent: authentication, call transformation, backend response, or throttling,
  • API Usage Across Geolocations helps identify your global API consumption trends so you can fine-tune your global sales and marketing, or geographic locations of your API gateways,
  • API Usage Across User Agents shows which platforms are being used to invoke the APIs so you can ensure that your documentation, sales, and marketing are in line with your subscribers’ needs,
  • Created APIs over Time helps you see how your project is evolving,
  • Developer Signups and Subscriptions Created over Time reports help see the dynamics of new subscriber acquisition.

Watch the video above for details and try the new reports in API Cloud today!

Lock down access to services

WSO2 Integration Cloud (also formerly known as App Cloud) is frequently used in conjunction with API Cloud to provide backend microservices or integration proxy service implementation.

For such backend services, you need a way to cut off external traffic so that they are only accessible within WSO2 Integration Cloud and API Cloud but not to the public internet.

Today we are releasing an Integration Cloud feature that lets you selectively open or close public internet access to your applications.

To hide your application from the internet, simply:

1. Open the application in WSO2 Integration Cloud.

2. On the left-hand menu, click Settings.

3. On the Exposure Level tab, click Private:

Public private networking for applications

Once you click the Update button, the application will no longer be accessible from the internet. You will only be able to access it within WSO2 Integration Cloud and WSO2 API Cloud using the *.wso2apps.local URL.

Log Access in API Cloud

One of the most exciting features of the updated API Cloud is access to logs. Now when one of your APIs or prototypes is not working as expected you can check out the logs and see what is going on.

Now if you need to troubleshoot an API issue simply do the following:

1. In API Cloud’s Publisher interface, on the Configure menu, click Admin Dashboard:

Admin Dashboard menu

2. In Admin Dashboard’s left-hand menu, navigate to Log Analyzer / Live Log Viewer:

Admin Dashboard log viewer

3. Now invoke the API or prototype that you are troubleshooting.

4. Go back to the Log Viewer and see the errors that the log got (in my particular case on the screenshot below, it was API authentication failed):

API invocation error in Log Viewer

With this new feature, it has just become easier to troubleshoot your APIs and make them work flawlessly.

Happy API development!


Recent Posts

Most Popular Posts