By the way...
...when i drop in a few files at the same time, each generating a message,
I only get one entry, too.
So it really seems the messages come to fast for the Monitoring Console to recognize them.
The monitoring console does scheduled collections of statistics from the nodes based on a configurable polling time - by default it is 10 minutes, but it can be easily adjusted downwards (see the jboss.esb:service=DataFilerScheduler MBean in jmx-console to adjust this), or you can force a collection manually. I think that is why you're only seeing two entries. You're not going to see an entry for each message you pass through, but you should see accurate counts for messages passing through your actions and services.
If you need higher-precision benchmarking times than what you are seeing - or instant results, I'd suggest adding benchmarking times to the action itself, or possibly surrounding the action you are interested in benchmarking in the action chain with a custom benchmarking action.
I would be very interested in hearing what your wishlist of benchmarking functions is - measurement and management is something we are actively working on and this is something we'd like to improve upon. Take a look at this blog entry to see the directions we're going with governance and tooling:
I knew that polling time, but thought that the data was still collected somewhere.
Well, what I want to do is compare different transformation methods.
Some of them using some kind of Smooks transformations, some don't.
For this I want feed the pipeline with lots of different messages,
so I can calculate good averages for processing times.
Of course I don't want to wait after each message I sent into the ESB,
just to get multiple values.
Since I already have a setup where my transforming actions are surrounded
with other actions, I started building my own benchmark stuff now.
Any suggestions on how to do this, perhaps using some of the ESB features would be welcome.