Skip to content
Kamon metrics and traces for Apache Camel routes, processors
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
project Upgrades: Kamon & Camel Nov 11, 2016
src Initial commit Sep 27, 2015
.gitignore Initial commit Sep 27, 2015
.travis.yml Java 8 in TravisCI Nov 11, 2016
LICENSE.txt Initial commit Sep 27, 2015 fixed mistype Sep 28, 2015
build.sbt Camel 1.18; Kamon 0.6.5; cross-build of Scala 2.11 & 2.12 Jan 9, 2017
version.sbt Initial commit Sep 27, 2015

Kamon metrics for Apache Camel



libraryDependencies += "com.osinka.camel" %% "camel-kamon" % "1.0.0-SNAPSHOT"

Usage in Camel

Unlike Kamon modules, this is a library that needs explicit configuration.

In Spring configuration:

<bean id="kamonRoutePolicyFactory" class="com.osinka.camel.kamon.KamonRoutePolicyFactory"/>

or programmatically:

import com.osinka.camel.kamon.KamonRoutePolicyFactory

camelContext.addRoutePolicyFactory(new KamonRoutePolicyFactory)


Only routes and processors with custom ID will be measured. Routes provide completion ("total", "success", "failure") metrics and trace contexts as well. Processors provide completion metrics and segments within the route's trace context.

Kamon startup

Kamon needs to be started before Camel creates its routes. Use the provided KamonService to make sure Kamon is up if you don't use other mechanisms.

In Spring configuration:

<bean id="kamonService" class="com.osinka.camel.kamon.KamonService"/>

or programmatically:

import com.osinka.camel.kamon.KamonService

camelContext.addService(new KamonService)
You can’t perform that action at this time.