This chapter describes the Fuse Mediation Router metrics collected for each processor in a route and supported control actions.
The Processors service collects metrics related to each processor in a Camel route. For
example, bean1 identifies the following processor:
Jane-Murpheys-MacBook-Pro.local ServiceMix 4.4.0-fuse "bean1" Jane-Murpheys-MacBook-Pro.local/217-camel-3 Processors
Supported metrics are:
Availability.This metric is of category Availability and collection type Dynamic.
Indicates the percentage of time the selected processor was available during a given time slice.
See Figure 2.2 for the key to the availability status icons
The following metrics are of category Throughput and collection type Trends Up:
ExchangesCompletedIndicates the total number of exchanges the selected processor has processed successfully.
By default, Fuse HQ displays the absolute number of completed exchanges since processor start-up or the last
resetoperation.ExchangesFailedIndicates the total number of exchanges the selected processor has failed to process.
By default, Fuse HQ displays the absolute number of failed exchanges since processor start-up or the last
resetoperation.ExchangesTotalIndicates the total number of exchanges, passed or failed, the selected processor has processed.
By default, Fuse HQ displays the absolute number of exchanges that have occurred since processor start-up or the last
resetoperation.
The following metrics are of category Throughput and collection type Dynamic.
Because Trends Up metrics continuously increase, the rate of change becomes more important to track. So Fuse HQ automatically calculates and creates a secondary per Minute metric for each Trends Up metric. By default, the per Minute Throughput metrics are enabled and charted.
ExchangesCompleted per MinuteIndicates the number of exchanges the processor has successfully processed per minute, since route start-up or the last
resetoperation.ExchangesFailed per MinuteIndicates the number of exchanges that the processor has failed to process per minute, since route start-up or the last
resetoperation.ExchangesTotal per MinuteIndicates the number of exchanges, passed or failed, that the processor has processed per minute, since route start-up or the last
resetoperation.
The following metrics are of category Performance and collection type Dynamic:
MinProcessingTimeIndicates the shortest time, in milliseconds, to process an exchange since processor start-up or the last
resetoperation.MeanProcessingTimeIndicates the average processing time, in milliseconds, for all exchanges processed since processor start-up or the last
resetoperation.MaxProcessingTimeIndicates the longest time, in milliseconds, to process an exchange since processor start-up or the last
resetoperation.TotalProcessingTimeIndicates the total processing time, in milliseconds, of all exchanges processed since processor start-up or the last
resetoperation.LastProcessingTimeIndicates the time, in milliseconds, it took the selected processor to process the last exchange.
Processor control actions enable you to control individual processors in a route and to retrieve performance and statistics data from them.
Supported control actions are:
startThe
startoperation starts up the selected processor immediately.stopThe
stopoperation stops the selected processor immediately.This operation is useful when you need to load updates made to the processor's configuration.
reset![[Warning]](imagesdb/warning.gif)
Warning The reset operation clears all counters, thus all statistics, for the selected processor.
getCamelIDThe getCamelID operation returns the ID of the
CamelContextin which the selected processor is running; for example,217-camel-3getRouteIdThe getRouteId operation returns the ID of the route in which the selected processor is running; for example,
route1getProcessorIdThe getProcessorId operation returns the selected processor's
ID; for example,bean1







