- 2 minutes to read

WSO2 Enterprise Integrator - Monitoring - Common Questions

Use this Troubleshooting Overview to find quick answers about proxy services, Carbon Console access, JMX connectivity, the monitoring agent, Docker, Kubernetes, Remote Actions, service status, alert detection, and the polling interval.

Question Quick Answer
FAQ1 Yes. Monitor Views give business users a read-only dashboard with business labels and clear service status.
FAQ2 Yes. Webhooks, alerting, and the Web API support ServiceNow, Jira, and other ticketing systems.
FAQ3 Yes. One monitoring agent can monitor Dev, Test, UAT, and Production when network access is available.
FAQ4 Yes. Docker and Kubernetes are supported when JMX or the Management API is exposed.
FAQ5 Yes. Remote Actions let authorized users restart proxy services from the Web Client.
FAQ6 No. Read-only JMX or Management API access is enough for monitoring; admin credentials are only needed for Remote Actions.
FAQ7 No. Licensing is based on agent instances, not on the number of monitored services.
FAQ8 Usually within 2 minutes. With the default 30-second polling interval, alerts often arrive in about 45 seconds.
FAQ9 WSO2 keeps running, but monitoring and alerting pause until the monitoring agent restarts.
FAQ10 Only network access plus JMX or Management API permissions are required; no OS account, SSH, or database access is needed.
FAQ11 WSO2 EI uses JMX and Carbon Console APIs, while Micro Integrator uses the Management API and a lighter runtime model.
FAQ12 WSO2 EI 6.x and 7.x plus WSO2 Micro Integrator 1.x and 4.x are supported.

Next Steps

  • Overview — Review the monitoring scope, supported resources, and architecture.
  • POC — Start a proof of concept for WSO2 monitoring.
  • Monitor Views — Build business-friendly dashboards for WSO2 service status.
  • Alarm Plugins — Route alerts to email, Teams, PagerDuty, or a webhook.