Hi, About Decanter in a cluster environment, what we usually do is:
1. decanter-collectors are installed on each node of the cluster (log, jmx) 2. you install a decanter appender that send data on a central backend (jdbc, elasticsearch, etc) Then, all logs and metrics and centralized in the backend, where you can query. For instance, with elasticsearch, you can use grafana/kibana to easily request and create dashboards. Regards JB On 24/05/2019 14:43, cooshal wrote: > Hi JB: > > thank you very much for these information. > > I managed to run decanter now. It's collecting logs now, and the logs are in > data/decanter. I will see how can I make use of it in the context of cellar > a centralized way (and ofcourse without Elasticsearch at the moment). > > Previously, I had all my camel bundles installed (that required both JMS and > JDBC). Trying to install Decanter after those bundles resulted in > installation failure (I do not know if that was the real cause, but that's > what I have observed after multiple attempts). The other thing I did was > install event admin before decanter. And, things got installed without any > trouble. > > Regarding the bootFeatures, yes, they look completely different. I have not > added all the features from standard distro and rather included the > components that we need at the moment, like broker ds, database ds, etc. > But, thanks for pointing out these as well. I will look at these things to > see if I can improve those things. > > Regards, > Cooshal. > > > > -- > Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
