WSO2 API Manager helps you to secure, govern, and analyze incoming and outgoing API request types. For more information, see WSO2 API Manager product page.
Go to Hosts, find your WSO2 host, select it to open Host overview page, and select the Tomcat process responsible for running WSOA2 API Manager.
Collected metrics
You'll find all the collected metrics in the WSO2 API Manager process group page.
Overall Carbon Health
- Carbon Faulty Services [Count]
- Carbon Response Time [ms] - Average Carbon Response Time
- Carbon Max Response Time [ms]
- Carbon EMB Database Read Time [ms] - 75th Percentile of read time
- Carbon EMB Database Read Rate in 15 minute [Count/sec]
- Carbon EMB Database Write Time [ms] - 75th Percentile of write time
- Carbon EMB Database Read Write in 15 minute [Count/sec]
These metrics are retrieved from the org.wso2.carbon
Java MBeans path.
Connectivity Health
- HTTP Listener Active Connections [Count]
- HTTP Sender Active Connections [Count]
- HTTP Latency [ms] - Average
- Backend HTTP Latency [ms] - Average
- HTTP Request Mediation Latency [ms] - Average
- HTTP Response Mediation Latency [ms] - Average
- HTTP Backend to ESB Response Read Time [ms] - Average
- HTTP Client to ESB Request Read Time [ms] - Average
- HTTP ESB to Backend Request Write Time [ms] - Average
- HTTP ESB to Client Response Write Time [ms] - Average
- HTTPS Listener Active Connections [Count]
- HTTPS Sender Active Connections [Count]
- HTTPS Latency [ms] - Average
- Backend HTTPS Latency [ms] - Average
- HTTPS Request Mediation Latency [ms] - Average
- HTTPS Response Mediation Latency [ms] - Average
- HTTPS Backend to ESB Response Read Time [ms] - Average
- HTTPS Client to ESB Request Read Time [ms] - Average
- HTTPS ESB to Backend Request Write Time [ms] - Average
- HTTPS ESB to Client Response Write Time [ms] - Average
- HTTPS Client Worker Queued Time [ms] - Average
- HTTPS Server Worker Queued Time [ms] - Average
These metrics come from the org.apache.synapse
path.
Alerts
The following alerts are enabled by default. Each alert is triggered after 5 consecutive reads.
- Carbon faulty services - At least one faulty Carbon service
- Carbon high response time - Carbon response time is 1 minute or more
- Carbon ESB high read time - Carbon ESB read time is 30 seconds or more
- Carbon ESB high write time - Carbon ESB write time is 30 seconds or more
- High HTTP latency - HTTP latency is 1 minute or more
- High HTTP backend latency - HTTP backend latency is 1 minute or more
- High HTTPS latency - HTTPS latency is 1 minute or more
- High HTTPS backend latency - HTTPs backend latency 1 minute