Introduction to Service Activity Monitoring
The Service Activity Monitoring
component allows for logging and monitoring service calls made with the Apache CXF
framework. Typical use cases are collecting usage statistics and fault
monitoring.
The Service Activity Monitoring consists of two parts:
- Agents (sam-agent) which gather and send monitoring data.
- A server (sam-server) which processes and stores the data.
The sequence of how these are used is as follows:
- The Agent creates events out of requests and replies from both the service consumer and provider side.
- The events are first collected locally and then sent to the Service Activity Monitoring Server periodically (so as not to disturb normal message flow).
- When the server receives events from the Agent, it optionally uses filters and/or handlers on those events and stores them in a database.
The Service Activity Monitoring Agent and Server are made available as follows:
- The Service Activity Monitoring Server is available in the Talend Runtime (via the command tesb:start-sam).
- Alternatively, the Service Activity Monitoring Server can be deployed as a WAR in a servlet container with database access information configured.
- The Agent is automatically enabled for Data Services deployed on Talend Runtime with the Use Service Activity Monitor option selected in the Talend Studio.
- The Agent is also available as a JAR that needs to be on the classpath of the service consumer and provider.