Monitoring AS4 Microservice system events
The AS4 Microservice system is monitored with Java™ Management Extensions (JMX) technology, a heartbeat process, message queue monitoring, and cache memory messages.
System activities monitoring
There are several
ways to monitor AS4 Microservice system
activities.
- System Monitoring with JMX
- By default AS4 Microservice nodes are enabled to use JMX technology. You can use the JMX capabilities to view information about the members on the node. You can use JMX tools to view the same information you would see if you used the AS4 Microservice member list command.
- Heartbeat Process
- The heartbeat process monitors the AS4 Microservice members, checking on the members one time each minute to see whether the members are still running. AS4 Microservice components use the information from the heartbeat process to adjust their operations based on the availability of the members. The heartbeat process starts when you start at least one member and stops when you stop all members. Use the member list command or the JMX tools to monitor the heartbeat process.
- Monitor message queues
- Use the WebSphere MQ administrative console to monitor the message queues used when running AS4 Microservice.
- Cache memory
- The cache memory is part of the AS4 Microservice container member. If the memory usage is too high, performance is affected. There are two watermarks that you can set to receive warning messages about cache memory usage.