The Baseline capability in JazzMon was designed to provide a reference snapshot from a single server with multiple applications for comparison purposes (a baseline "set"). It figures out which application baseline within the set to use based on the server URL (using the application name at the end of the server URL, i.e. ccm or jazz, matches the jazz baseline in the set, etc). A fix was made in JazzMon 1.3.0 to do a better job matching application names that aren't exact matches (i.e. having jazz2 and jazz4 match the "jazz" application within a baseline set).

That baseline set can be changed per JazzMon analysis run but there isn't yet a way of having it track multiple servers and then use different baseline sets for each one in the same analysis run. That would require a change in JazzMon to reference a collection of available baselines and figure out which "set" to use for a given server. The only workaround currently would be to use separate JazzMon sessions to track the different servers and have each use the baseline property to select the appropriate baseline.

It would be interesting to hear if other users might find this capability useful. Baselines are more valuable when they represent an earlier well-performing snapshot of the same server.

we haven't got as far as creating our own ccm level baselines yet, but I can see where this would be a problem given the current jazzmon operations.  I would support an enhancement to allow us to configure the baseline explicitly like we specify the servers monitored. (rather than have jazzmon attempt to figure it out)

Sam