Thanks for the responses. I agree that this isn't really something to
expect from a message server. At first I was looking at the metrics
component but it didn't quite match our requirements (e.g. the counter
doesn't persist on restarts afaik). Unfortunately we have a number of
constraints about
Similar to Quinn's response, but instead of splunk, we stood up a statsd +
graphite server (pretty quick via docker). We're using Spring Boot, so it
was natural to use its metric support with a statsd client to push metrics
to the server over UDP -- very, very little impact to app performance.
Not
We do this by posting an auditing message to Splunk over HTTP. By doing that,
we can not only get counts over a particular timeframe, but we can derive
message rates as well.
> On Jan 25, 2018, at 2:56 PM, Olivier Eymere wrote:
>
> I am looking for a way to keep running counts of all of the
I am looking for a way to keep running counts of all of the processed
messages. The last part of the camel application is a route that posts the
message to a web service, we need to keep counts of the various responses
so that when the entire process is complete and the application is exiting
it w
