the following commands in the console: karaf@root()> bundle:list --help DESCRIPTION bundle:list Lists all installed bundles. SYNTAX bundle:list [options] [ids] ARGUMENTS ids The list of bundle (identified 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

(y or n) *:config *:dev *:feature *:instance *:jaas *:kar *:log *:package *:region *:service *:shell *:ssh addbundle addfilter addregion alias cancel using the --help option for this command: karaf@root()> bundle:list --help DESCRIPTION bundle:list Lists all installed bundles. SYNTAX bundle:list [options] OPTIONS -u Shows the update locations --help 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)>

accomplish and the consequences. # # The primary way of configuring a node is via this file. This template lists # the most important settings you may want to configure for a production cluster. # # Please see the topic. We just need an Activator in the collector bundle to start our BundleCollector listener: package org.apache.karaf.decanter.sample.collector; import org.osgi.framework.SynchronousBundleListener; eventAdmin.postEvent(event); } } Now, we just need a Maven pom.xml to package the bundle with the correct OSGi headers: package org.apache.karaf.decanter.sample.collector; import org.osgi.framework

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

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 (https://lucene.apache.org/core/8_5_0/queryparser/org/apache/ lucene/queryparser/classic/package-summary.html#package.description). For instance: ◦ message:foo* selects all events with message containing implementing SynchronousBundleListener interface: Apache Karaf Decanter 2.x - Documentation - 48 package org.apache.karaf.decanter.sample.collector; import org.osgi.framework.SynchronousBundleListener;

------ 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

------ 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