Could you post your xml here and we'll review it?

I am trying the following:

. I have configured the ERMA in a xml file using the steps given on the link: http://erma.wikidot.com/configuring-erma-using-spring
. I have a simple Java application in the same project that uses the ERMA monitor APIs. But when I called MonitoringEngine.getInstance().startup() in my application, it was giving the error: processorFactory is null. Is there anything else that I need to do in my application?

Do I need to run the MonitorProcessor in a separate project.

Do let me know if you need any other information related to my code. I will appreciate that.

Thanks

The above code was an example of how to configure the processor factory programatically, if you don't use Spring for dependency injection.

MonitorProcessors are passed into the ProcessGroups and are designed to consume Monitors and process them in some way. An example would be the LoggingMonitorProcessor which as it receives Monitors from the MonitoringEngine it will log them out.

Am I missing something on the documentation page, as I didn't find the above code. One more thing: how to initialize "someMonitorProcessor" above? Its an error when I create an instance of MonitorProcessor.

What else do I need to do to observe the captured events? I have the following:
1) Test application alongwith monitors
2) In the same project, I have configured ERMA
3) I assume I need to run the MonitorProcessor in a different project right?

Thank you very much

 ProcessGroup pg = new ProcessGroup(someMonitorProcessor); SimpleMonitorProcessorFactory factory = new SimpleMonitorProcessorFactory(new ProcessGroup[] {pg}); MonitoringEngine.getInstance().setProcessorFactory(factory); 

If it helps, you may want to look at the unit tests for these classes to get a clearer picture for how they work together. Think of a ProcessGroup as a way to route Monitors to a set of MonitorProcessors.

But, I am not completely clear from the documentation. So, when I ran the application, I got this exception:

Exception in thread "main" java.lang.IllegalStateException: processorFactory is null
at com.orbitz.monitoring.api.MonitoringEngine.startup(MonitoringEngine.java:89)
at ErmaTest.main(ErmaTest.java:24)
ErmaTest.java: 24 has MonitoringEngine.getInstance().startup();

Can you please help me in using the monitor functionality and viewing the captured events at the processor side. Do I need to hook some additional code in the application besides calling the monitoringEngine startup/shutdown and monitor APIs.

Thanks

I think the general issue here isn't just whether code is "generic" enough, but whether we expect others to perceive value in something vs. it just having the appearance of cruft.

hostname can be initialized correctly in the MonitoringEngine so we might as well keep it. vmid should be defaulted to something sensical like "not set" and we should drop the initialization from Orbitz specific environment properties. That code initialization code can live in your codebase.

I don't see any harm in keeping those attributes. The only case were they wouldn't be applicable would be in a non-distributed environment. But then, there's a lot of stuff in ERMA that could go away if we assumed we aren't distributed.

1. EventPatternMonitorProcessor
2. EventPatternMonitorRenderer
3. EventPatternLoggingMonitorProcessor
4. XmlMonitorRenderer

These classes rely heavily on specific attributes that Orbitz uses.