LibraryPrintFeedback

Fuse Mediation Router Metrics Reference

Version 4.4

April 2011
Legal Notices

Updated: 03 Aug 2011

Table of Contents

1. Accessing and Using Collected Router Metrics
2. Fuse Mediation Router Routing Metrics
3. Fuse Mediation Router Processor Metrics

List of Figures

1.1. Setting the metric collection interval
1.2. Setting the metric refresh rate
1.3. Resource's Control tab
1.4. Control Action Properties and Schedule portlet
1.5. Control Action Schedule section
1.6. Resource's Alert tab
1.7. New Alert Definition portlet:Condition Set section
1.8. Alert Response tabs
1.9. Control Action portlet
2.1. route1
2.2. Availability Statistics Icons
3.1. bean1 Processor

The main service entries, which collect the required metrics, are listed in the server's and each agent's fuse-routing-services.xml file. This file is located in:

[Note]Note

When a deployment consists of multiple agents, each agent's fuse-routing-services.xml file must remain in sync with the Server's fuse-routing-services.xml file so that data is collected properly. If, for example, you changed a property of a metric in the Server's fuse-routing-services.xml file, but not in the agent's, not only would the metric not display as expected, it might not even be collected.

The main service entries are:

  • Router

  • Router Component

  • Router Endpoint

  • Route

  • Processors



[1] The path to the server's or the agents' fuse-routing-services.xml file is version-specific.

The Route service collects metrics related to Camel routes that run inside CamelContexts. For example, route1 identifies the following route:

Jane-Murpheys-MacBook-Pro.local ServiceMix 4.4.0-fuse "route1" new-host-2.home/217-camel-3 Route


Supported metrics are:

The following metrics are of category Throughput and collection type Trends Up:

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.

The following metrics are of category Performance and collection type Dynamic:

Route control actions enable you to control routes and to retrieve performance and statistics data from them.

Supported control actions are:



[2] On some screens, you may see the term Value Type instead of Collection Type.

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:

The following metrics are of category Throughput and collection type Trends Up:

  • ExchangesCompleted

    Indicates 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 reset operation.

  • ExchangesFailed

    Indicates 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 reset operation.

  • ExchangesTotal

    Indicates 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 reset operation.

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 Minute

    Indicates the number of exchanges the processor has successfully processed per minute, since route start-up or the last reset operation.

  • ExchangesFailed per Minute

    Indicates the number of exchanges that the processor has failed to process per minute, since route start-up or the last reset operation.

  • ExchangesTotal per Minute

    Indicates the number of exchanges, passed or failed, that the processor has processed per minute, since route start-up or the last reset operation.

The following metrics are of category Performance and collection type Dynamic:

  • MinProcessingTime

    Indicates the shortest time, in milliseconds, to process an exchange since processor start-up or the last reset operation.

  • MeanProcessingTime

    Indicates the average processing time, in milliseconds, for all exchanges processed since processor start-up or the last reset operation.

  • MaxProcessingTime

    Indicates the longest time, in milliseconds, to process an exchange since processor start-up or the last reset operation.

  • TotalProcessingTime

    Indicates the total processing time, in milliseconds, of all exchanges processed since processor start-up or the last reset operation.

  • LastProcessingTime

    Indicates the time, in milliseconds, it took the selected processor to process the last exchange.