Welcome to ERMA's Wiki

ERMA (Extremely Reusable Monitoring API) is an instrumentation API that has been designed to be applicable for all monitoring needs. The design goal is "to make instrumentation as simple as logging." Lowering the effort needed to add instrumentation will encourage developers to add monitoring code where ever it makes sense.

Standardizing the instrumentation API allows greater reuse of the data collected. Events captured in today's log messages, for example, might be better expressed using ERMA as this allows the data to be routed to an analysis tool in the future without grepping log files.

ERMA is part of a Complex Event Processing platform developed at Orbitz Worldwide. ERMA has been open sourced along with another component of the system, Graphite. To learn more about how these projects can be used, check out the JavaOne presentation.

ERMA Architecture

• Main Features
• Attribute Inheritance Hierarchy
• Future Improvements

ERMA Cookbook

Working with Monitors:

• Using An EventMonitor
• Using A TransactionMonitor
• Writing Your Own Monitor

Working with MonitorProcessors:

• Using LoggingMonitorProcessor
• Using ResultCodeAnnotatingMonitorProcessor
• Writing Your Own MonitorProcessor

Working with MonitorProcessorFactories:

• Using SimpleMonitorProcessorFactory

Integrating ERMA with your codebase:

• Instrumenting Your API With ERMA
• Unit Testing ERMA Instrumentation
• Adding ERMA Support To Your Application
• Suggested ERMA usage patterns
• Configuring ERMA using Spring
• ERMA Simplified: Avoiding cancer

Viewing output of ERMA instrumentation:

• Send ERMA events to application logs, see Using EventPatternLoggingMonitorProcessor

Troubleshooting ERMA problems:

• Enable debug logging
• Nothing Is Being Processed
• Errors About Double Processing

Support:

• Forum
• Recent posts