...
When an @Monitor annotation is encountered, the Fabric3 runtime will generate a monitor proxy and inject it based on the monitor interface. Depending on the current monitor level, events may be recorded or ignored. In the above example, if the monitor level is set to severe, the receivedRequest() event will be dropped.
Configuration
Ring Buffer Support
Monitor events are sent to a destination. A destination has one or more appenders that act as sinks for monitor events. It is possible to create a custom appender (detailed below) or use one of the provided appenders such as the file or console appenders. An application (or service) can send events to a custom destination or use the default runtime destination. Sending events to a custom destinations allows traffic for a particular application, subsystem or service to be segmented from other events.
Configuring the Runtime Destination
The default runtime destination is where Fabric3 runtime events (and application events if not specified) are sent. The default destination can be configured in systemConfig.xml , for example, to record events to a log file instead of outputting to the console. The monitor element is used to add appenders
- <monitor>
- <appenders>
- <appender.file file="fabric3.log"/>
- <appender.console/>
- </appenders>
- </monitor>
Configuring Custom Destinations
Ring Buffer Destinations
Custom Appenders
...
Configuration Reference
Performance Considerations
...