debian package of karaf: 1. Add the key of the unofficial debian archive containing karaf 2. Open /etc/apt/sources.list in a text editor and add the following lines: 3. Update the APT package index and and install the package The installed karaf will run as user karaf, group karaf, listening to the usual default karaf ports, be started with systemd, with KARAF_ETC in /etc/karaf and KARAF_DATA in /var/lib/karaf/data bugreport.cgi?bug=881297 [Debian Request For Package (RFP) of karaf] results in an official karaf package becoming available, the unofficial debian package will be discontinued. tar zxvf apache-karaf-4

name=org.apache.camel:context=*,type=routes,name=* # Several object names can also be specified. # What matters is that the property names begin with "object.name". #object.name.system=java.lang:* #object property contains the ObjectName filter to retrieve the attributes only to some MBeans. Several object names can be listed, provided the property prefix is object.name. . • any other values will be part of you're using unique names. # cluster.name: elasticsearch cluster.routing.schedule: 50ms #################################### Node ##################################### # Node names are generated dynamically

name=org.apache.camel:context=*,type=routes,name=* # Several object names can also be specified. # What matters is that the property names begin with "object.name". #object.name.system=java.lang:* #object property contains the ObjectName filter to retrieve the attributes only of some MBeans. Several object names can be listed, provided the property prefix is object.name.. • any other values will be part of dec(); } } Don’t forget to import io.prometheus* packages in your bundle MANIFEST.MF: Import-Package: io.prometheus.client;version="[0.8,1)" That’s the only thing you need: your metrics will be available

(y or n) *:config *:dev *:feature *:instance *:jaas *:kar *:log *:package *:region *:service *:shell *:ssh addbundle addfilter addregion alias cancel karaf@root()> * bundle cl config dev feature help instance jaas kar la ld lde log log:list man package region service shell ssh system karaf@root()> bundle karaf@root(bundle)> karaf@root(bundle)> region | 3.0.0 | x | standard-3.0.0 | Provide Region Support package | 3.0.0 | x | standard-3.0.0 | Package commands and mbeans kar | 3.0.0 | x | standard-3.0.0

enabled="false"/> Instead of using multicast, you can also explicitly define the host names (or IP addresses) of the different Cellar nodes: By default, it will bind to all interfaces on the ------ gemini-blueprint | 1.0.0.RELEASE | | cluster/local | package | 3.0.2 | x | cluster/local | jclouds-api-route53 management and discovery. Following the aforementioned concept will most likely change how you package and provision your Karaf based applications. For instance, you will eventually have to provide a

enabled="false"/> Instead of using multicast, you can also explicitly define the host names (or IP addresses) of the different Cellar nodes: By default, it will bind to all interfaces on the ------ gemini-blueprint | 1.0.0.RELEASE | | cluster/local | package | 3.0.2 | x | cluster/local | jclouds-api-route53 management and discovery. Following the aforementioned concept will most likely change how you package and provision your Karaf based applications. For instance, you will eventually have to provide a

Requires: package:(&(package=javax.naming)) package:(&(package=javax.naming.spi)) package:(&(package=javax.sql)) package:(&(package=javax.transaction)) package:(&(package=javax.transaction.xa)) package:(&(package=org pool)(version>=1.3.0)(!(version>=2.0.0))) package:(&(package=org.apache.commons.pool.impl)(version>=1.3.0)(!(version>=2.0.0))) package:(&(package=org.xml.sax)) package:(&(package=org.xml.sax.helpers)) Capabilities: commons-dbcp, presentationname=Apache ServiceMix :: Bundles :: commons-dbcp, version=1.4.0.3} package:{package=org.apache.commons.dbcp.cpdsadapter, uses:=org.apache.commons.dbcp,javax.naming,javax.sql,org