One service call can generate four events: for example, a consumer is sending a request (REQ_OUT), the service receives the request (REQ_IN), the service sends a response (RESP_OUT) and the consumer receives the response (RESP_IN).
An Agent can be configured to collect all four events of this single service call, from both
the consumer and provider side. For further event processing, all of these events will
get the same flow id. For more detailed information, see Service Activity Monitoring architecture diagram.
|
Consumer side |
Provider side |
|---|---|
| REQ_OUT | REQ_IN |
| RESP_IN | RESP_OUT |
| FAULT_IN | FAULT_OUT |
Besides normal Event types, additional Lifecycle Events are also generated by SAM agent.
In the Talend Runtime Container, when the agent bundle is started or stopped, the SERVER_START/SERVER_STOP events will be generated. For Service or Data Service bundles, when they have been started/stopped, the SERVICE_START/SERVICE_STOP (for Provider) or CLIENT_CREATE/CLIENT_DESTROY (for Consumer) events will be generated.
collector.lifecycleEvent property must be set to true
in order to generate and store the lifecycle events.|
Lifecycle |
Event type |
|---|---|
| Talend Runtime Container | SERVER_START/SERVER_STOP |
| Service Provider/Consumer | SERVICE_START/SERVICE_STOP; CLIENT_CREATE/CLIENT_DESTROY |
| Data Service | SERVICE_START/SERVICE_STOP; CLIENT_CREATE/CLIENT_DESTROY |