Integrating Moesif Analytics with WSO2 API Manager 4.6

-

As API ecosystems grow in scale and complexity, traditional monitoring is no longer sufficient. Modern API platforms demand deep observability, real-time insights, and business-level analytics.

WSO2 API Manager 4.6 introduces native integration with Moesif, a powerful API analytics and observability platform that helps teams understand how APIs are used, who is using them, and where things go wrong — all in real time.

In this article, we’ll walk through a complete, end-to-end integration of Moesif Analytics with WSO2 API Manager 4.6, covering configuration, verification, and dashboard exploration.

What Is Moesif?

Moesif is an API analytics and observability platform designed specifically for API products. Unlike traditional metrics-only tools, Moesif focuses on:

  • API usage behavior
  • Latency and error patterns
  • Customer and consumer analytics
  • API monetization insights
  • Debugging failed or slow API calls

When combined with WSO2 API Manager, Moesif transforms raw API traffic into actionable intelligence.

Prerequisites

Before starting, ensure you have the following:

  • WSO2 API Manager 4.6.x installed and running
  • Access to the Gateway node (where analytics are published)
  • A Moesif account
  • Basic familiarity with WSO2 APIM configuration files

High-Level Architecture


Image Ref: WSO2 Docs

Step 1: Create a Moesif Account

  1. Visit the Moesif website
  2. Sign up for a free account
  3. After login, navigate to: Settings --> API Keys
  4. Copy the Application ID (API Key) This key uniquely identifies your WSO2 APIM instance in Moesif.

Step 2: Locate deployment.toml in WSO2 APIM

On your WSO2 API Manager Gateway node:

<APIM_HOME>/repository/conf/deployment.toml

This is the main configuration file where analytics integrations are enabled.

Step 3: Enable Moesif Analytics in WSO2 APIM

Add or update the following configuration in deployment.toml:

[apim.analytics.moesif]
enable = true
api_key = "<YOUR_MOESIF_API_KEY>"

Step 4: Restart WSO2 API Manager

api-manager.sh stop
api-manager.sh start

Step 5: Invoke an API

  1. Log in to API Publisher
  2. Create and publish a sample API (or use an existing one)
  3. Subscribe to the API via Developer Portal
  4. Generate an access token
  5. Invoke the API using curl / Postman
curl -X GET \
  https://<gateway-host>:8243/sample/1.0.0/resource \
  -H "Authorization: Bearer <ACCESS_TOKEN>"

Step 6: Verify Events in Moesif Dashboard

Within a few seconds of invoking the API:

  1. Log in to Moesif
  2. Navigate to: Live Events --> API Calls
  3. You should see:
    • API name & version
    • HTTP method
    • Response status
    • Latency
    • Client IP
    • Consumer application
Here is the end to end video tutorial-

This confirms successful integration!

Comments

Post a Comment

Popular posts from this blog

Oracle SOA Suite- Implementing Email Notification

-
Image
In this post, I am going to show how to implement email notifications in Oracle SOA Suite using BPEL process. So let's get started- Implementing email notification in Oracle SOA Suite consists of below steps: Environment- IDE- Oracle jDeveloper 11g Weblogic Server 12c Oracle SOA Suite 12c High Level Steps Keep ready email server settings. Configure & enable usermessagingdriver-email for target SOA servers via console. Setting up Email driver (usermessagingdriver-email )with email server settings via enterprise manager. Enable notifications for SOA workflows(make sure either All or EMail option is selected).. Create SOA composite application Deploy it on SOA server. Testing & done. 1. Keep ready email server settings. Keep ready your below email server settings: Outgoing Mail Server          : smtp.domain.com Outgoing Mail Server Port   : xxx Default From Address         : username@doamin...
Read more

Oracle SOA Suite 12c- PKIX path building failed & unable to find valid certification path to requested target

-
Image
Hi Everyone, in this blog I'll be writing one of the strange issue that has been encountered while working with a Oracle SOA composite running in Oracle IDAM environment and trying to invoke a SSL based remote service where SSL certification based exception has been thrown during the service invocation. Environment Oracle SOA Suite 12c  (HA Mode) Oracle IDAM 12c (HA Mode) Oracle Linux 7 External Web Service (SOAP Service) Problem Below is the exception thrown when trying to invoke an external webservice (SSL Based) via BPEL process- <bpelFault><faultType>0</faultType><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>oracle.fabric.common.FabricInvocationException: Unable to invoke endpoint URI "https://idam.uppclonline.com/soa-infra/services/default/DefaultOperationalApproval!5.12*soa_69e4734b-d8fe-4edf-b44e-e287f61c2ddf/SMSNotification%23ApprovalProcess/SMSNotification" succe...
Read more

Migration of Oracle SOA Suite Composite from 11g to 12c

-
Image
Recently I have came across a scenario where I have a business requirement of  migration of Oracle SOA Suite 11g(11.1.1.7.0) to 12c(12.1.3.0). Below are the different mechanisms I have tried to do, few of them failed and one succeeded. Working in Oracle SOA Suite 11g is completely different from 12c. In 11g, we need to install the jDeveloper(11.1.1.7) then SOA extension separately to be installed either via offline file  (download available at  https://www.oracle.com/ocom/groups/public/@otn/documents/webcontent/156082.xml ) or through jDeveloper top menu >>  Help >> Check for Updates >> SOA Extension.  While working with 12c doesn't involves such tedious job. Only single installer is required for jDeveloper/SOA/Weblogic and is available as QuickStart Installer(download available at https://www.oracle.com/technetwork/middleware/soasuite/downloads/index.html). Approach 1- Compress(Zip) SOA composite ...
Read more