You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Oliver Wulff <ow...@talend.com> on 2016/04/04 08:58:49 UTC
Feedback for Canceling Decanter 1.1.0
Hi there
I'd like to give some feedback regarding the discussion in the vote for Decanter 1.1.0.
It's a nice feature to install kibana and the elasticsearch node within the same JVM as Karaf, but really only for demo purposes. Elastic doesn't recommend and support to bundle elasticsearch node within another JVM. Further, elastic recommends to run elasticsearch node isolated on a dedicated machine (!) where even nothing else is running to benefit of the low level features used by elasticsearch.
https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html
[https://www.elastic.co/static/img/elastic-logo-200.png]<https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html>
Configuration - Elastic<https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html>
www.elastic.co
Environment Variablesedit. Within the scripts, Elasticsearch comes with built in JAVA_OPTS passed to the JVM started. The most important setting for that is the -Xmx ...
Same applies for Kibana 4 dashboards. Usually, you have an elasticsearch cluster and server hosting the kibana application.
What I wanted to say is that whether kibana 4 works in Karaf or not is not really relevant for a production deployment.
Finally, yes, we were very keen on the release 1.1.0 as it brings kafka with SSL support. We successfully tested this already with the snapshot version.
Do you have a rough idea when the next vote is planned?
I'd recommend to use Kibana 4.5 as it brings support for custom labels and colour customization (already in 4.4). The pre-condition is ES 2.3.
Thanks
Oli
Re: AW: Feedback for Canceling Decanter 1.1.0
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi,
sorry, but since we already have all objects in the grasp of the jvm I
still regard it faster and safer to go the transport-client way of using
the one
embedded elasticsearch node. Even if it's only 4% "faster" I still think
it's better to use the embedded one. And you didn't see the last benefit of
using the embedded node for the internal setup of the kibana dashboard,
wherever the Kibana server resides.
regards, Achim
2016-04-04 10:48 GMT+02:00 Oliver Wulff <ow...@talend.com>:
> Hi
>
> The performance gain of node/client is only 4% (see section "Elasticsearch
> Output now Defaults to HTTP"):
> https://www.elastic.co/blog/logstash-2-0-0-beta1-released
>
> Thanks
> Oli
>
>
> ________________________________________
> Von: Achim Nierbeck <bc...@googlemail.com>
> Gesendet: Montag, 4. April 2016 10:34
> An: dev@karaf.apache.org
> Betreff: Re: AW: Feedback for Canceling Decanter 1.1.0
>
> Hi,
>
> Sorry for being late to the party.
> But I think you missed some important parts. First of all, cancelling.
> With a 1.1.0 we should really show something fancy in the part you see
> upfront.
> Second about embedding elasticsearch, you missed something very important.
> Running embedded is very good to run with an elastic cluster because you
> can use your embedded node as a client node. And this client node should
> always be favored instead of using an REST API.
> Third, if you run in this scenario weather with our without embedded
> kibana, it's an valuable improvement to have the dashboards installed right
> away.
>
> Regards, Achim
>
> sent from mobile device
> Am 04.04.2016 10:23 vorm. schrieb "Jean-Baptiste Onofré" <jb@nanthrax.net
> >:
>
> > IMHO, it's a perfect approach when you don't care about elasticsearch and
> > just want a monitoring solution embedded in Karaf. Some Decanter users
> > don't know that they actually use elasticsearch and kibana (they just see
> > the name in the browser ;)).
> >
> > If you want more advanced settings, then, you are free to create your own
> > infrastructure and let Decanter uses it.
> >
> > Anyway, I will add a note in the documentation.
> >
> > Regards
> > JB
> >
> > On 04/04/2016 10:13 AM, Oliver Wulff wrote:
> >
> >> Hi JB
> >>
> >>
> >>>>> What you bring is right but users may have different standpoint: lot
> of
> >> people just wants to use decanter as a blackbox solution with
> >> elasticsearch and kibana embedded.
> >>
> >>>
> >>>>> I understand this point but we should at least mention in the
> >> documentation that it's not the recommended approach to emebed an
> >> elasticsearch node within a JVM.
> >>
> >> Thanks
> >> Oli
> >> ________________________________________
> >> Von: Jean-Baptiste Onofré <jb...@nanthrax.net>
> >> Gesendet: Montag, 4. April 2016 09:34
> >> An: dev@karaf.apache.org
> >> Betreff: Re: Feedback for Canceling Decanter 1.1.0
> >>
> >> Hi Oli,
> >>
> >> The vote will stand Wednesday.
> >>
> >> What you bring is right but users may have different standpoint: lot of
> >> people just wants to use decanter as a blackbox solution with
> >> elasticsearch and kibana embedded.
> >>
> >> So, even if your need is different, we have to address both.
> >>
> >> Kibana 4.5 is not a viable solution as it's related to node.js: Decanter
> >> Kibana is not a standard Kibana version: I changed to remove node.js and
> >> use pure HTML/js client frontend.
> >>
> >> Regards
> >> JB
> >>
> >> On 04/04/2016 08:58 AM, Oliver Wulff wrote:
> >>
> >>> Hi there
> >>>
> >>>
> >>> I'd like to give some feedback regarding the discussion in the vote for
> >>> Decanter 1.1.0.
> >>>
> >>>
> >>> It's a nice feature to install kibana and the elasticsearch node within
> >>> the same JVM as Karaf, but really only for demo purposes. Elastic
> doesn't
> >>> recommend and support to bundle elasticsearch node within another JVM.
> >>> Further, elastic recommends to run elasticsearch node isolated on a
> >>> dedicated machine (!) where even nothing else is running to benefit of
> the
> >>> low level features used by elasticsearch.
> >>>
> >>>
> >>>
> >>>
> https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html
> >>>
> >>> [https://www.elastic.co/static/img/elastic-logo-200.png]<
> >>>
> https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html
> >>> >
> >>>
> >>> Configuration - Elastic<
> >>>
> https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html
> >>> >
> >>> www.elastic.co
> >>> Environment Variablesedit. Within the scripts, Elasticsearch comes with
> >>> built in JAVA_OPTS passed to the JVM started. The most important
> setting
> >>> for that is the -Xmx ...
> >>>
> >>>
> >>> Same applies for Kibana 4 dashboards. Usually, you have an
> elasticsearch
> >>> cluster and server hosting the kibana application.
> >>>
> >>>
> >>> What I wanted to say is that whether kibana 4 works in Karaf or not is
> >>> not really relevant for a production deployment.
> >>>
> >>>
> >>> Finally, yes, we were very keen on the release 1.1.0 as it brings kafka
> >>> with SSL support. We successfully tested this already with the snapshot
> >>> version.
> >>>
> >>>
> >>> Do you have a rough idea when the next vote is planned?
> >>>
> >>>
> >>> I'd recommend to use Kibana 4.5 as it brings support for custom labels
> >>> and colour customization (already in 4.4). The pre-condition is ES 2.3.
> >>>
> >>>
> >>> Thanks
> >>>
> >>> Oli
> >>>
> >>>
> >>>
> >> --
> >> Jean-Baptiste Onofré
> >> jbonofre@apache.org
> >> http://blog.nanthrax.net
> >> Talend - http://www.talend.com
> >>
> >>
> > --
> > Jean-Baptiste Onofré
> > jbonofre@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
AW: AW: Feedback for Canceling Decanter 1.1.0
Posted by Oliver Wulff <ow...@talend.com>.
Hi
The performance gain of node/client is only 4% (see section "Elasticsearch Output now Defaults to HTTP"):
https://www.elastic.co/blog/logstash-2-0-0-beta1-released
Thanks
Oli
________________________________________
Von: Achim Nierbeck <bc...@googlemail.com>
Gesendet: Montag, 4. April 2016 10:34
An: dev@karaf.apache.org
Betreff: Re: AW: Feedback for Canceling Decanter 1.1.0
Hi,
Sorry for being late to the party.
But I think you missed some important parts. First of all, cancelling.
With a 1.1.0 we should really show something fancy in the part you see
upfront.
Second about embedding elasticsearch, you missed something very important.
Running embedded is very good to run with an elastic cluster because you
can use your embedded node as a client node. And this client node should
always be favored instead of using an REST API.
Third, if you run in this scenario weather with our without embedded
kibana, it's an valuable improvement to have the dashboards installed right
away.
Regards, Achim
sent from mobile device
Am 04.04.2016 10:23 vorm. schrieb "Jean-Baptiste Onofré" <jb...@nanthrax.net>:
> IMHO, it's a perfect approach when you don't care about elasticsearch and
> just want a monitoring solution embedded in Karaf. Some Decanter users
> don't know that they actually use elasticsearch and kibana (they just see
> the name in the browser ;)).
>
> If you want more advanced settings, then, you are free to create your own
> infrastructure and let Decanter uses it.
>
> Anyway, I will add a note in the documentation.
>
> Regards
> JB
>
> On 04/04/2016 10:13 AM, Oliver Wulff wrote:
>
>> Hi JB
>>
>>
>>>>> What you bring is right but users may have different standpoint: lot of
>> people just wants to use decanter as a blackbox solution with
>> elasticsearch and kibana embedded.
>>
>>>
>>>>> I understand this point but we should at least mention in the
>> documentation that it's not the recommended approach to emebed an
>> elasticsearch node within a JVM.
>>
>> Thanks
>> Oli
>> ________________________________________
>> Von: Jean-Baptiste Onofré <jb...@nanthrax.net>
>> Gesendet: Montag, 4. April 2016 09:34
>> An: dev@karaf.apache.org
>> Betreff: Re: Feedback for Canceling Decanter 1.1.0
>>
>> Hi Oli,
>>
>> The vote will stand Wednesday.
>>
>> What you bring is right but users may have different standpoint: lot of
>> people just wants to use decanter as a blackbox solution with
>> elasticsearch and kibana embedded.
>>
>> So, even if your need is different, we have to address both.
>>
>> Kibana 4.5 is not a viable solution as it's related to node.js: Decanter
>> Kibana is not a standard Kibana version: I changed to remove node.js and
>> use pure HTML/js client frontend.
>>
>> Regards
>> JB
>>
>> On 04/04/2016 08:58 AM, Oliver Wulff wrote:
>>
>>> Hi there
>>>
>>>
>>> I'd like to give some feedback regarding the discussion in the vote for
>>> Decanter 1.1.0.
>>>
>>>
>>> It's a nice feature to install kibana and the elasticsearch node within
>>> the same JVM as Karaf, but really only for demo purposes. Elastic doesn't
>>> recommend and support to bundle elasticsearch node within another JVM.
>>> Further, elastic recommends to run elasticsearch node isolated on a
>>> dedicated machine (!) where even nothing else is running to benefit of the
>>> low level features used by elasticsearch.
>>>
>>>
>>>
>>> https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html
>>>
>>> [https://www.elastic.co/static/img/elastic-logo-200.png]<
>>> https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html
>>> >
>>>
>>> Configuration - Elastic<
>>> https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html
>>> >
>>> www.elastic.co
>>> Environment Variablesedit. Within the scripts, Elasticsearch comes with
>>> built in JAVA_OPTS passed to the JVM started. The most important setting
>>> for that is the -Xmx ...
>>>
>>>
>>> Same applies for Kibana 4 dashboards. Usually, you have an elasticsearch
>>> cluster and server hosting the kibana application.
>>>
>>>
>>> What I wanted to say is that whether kibana 4 works in Karaf or not is
>>> not really relevant for a production deployment.
>>>
>>>
>>> Finally, yes, we were very keen on the release 1.1.0 as it brings kafka
>>> with SSL support. We successfully tested this already with the snapshot
>>> version.
>>>
>>>
>>> Do you have a rough idea when the next vote is planned?
>>>
>>>
>>> I'd recommend to use Kibana 4.5 as it brings support for custom labels
>>> and colour customization (already in 4.4). The pre-condition is ES 2.3.
>>>
>>>
>>> Thanks
>>>
>>> Oli
>>>
>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: AW: Feedback for Canceling Decanter 1.1.0
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi,
Sorry for being late to the party.
But I think you missed some important parts. First of all, cancelling.
With a 1.1.0 we should really show something fancy in the part you see
upfront.
Second about embedding elasticsearch, you missed something very important.
Running embedded is very good to run with an elastic cluster because you
can use your embedded node as a client node. And this client node should
always be favored instead of using an REST API.
Third, if you run in this scenario weather with our without embedded
kibana, it's an valuable improvement to have the dashboards installed right
away.
Regards, Achim
sent from mobile device
Am 04.04.2016 10:23 vorm. schrieb "Jean-Baptiste Onofré" <jb...@nanthrax.net>:
> IMHO, it's a perfect approach when you don't care about elasticsearch and
> just want a monitoring solution embedded in Karaf. Some Decanter users
> don't know that they actually use elasticsearch and kibana (they just see
> the name in the browser ;)).
>
> If you want more advanced settings, then, you are free to create your own
> infrastructure and let Decanter uses it.
>
> Anyway, I will add a note in the documentation.
>
> Regards
> JB
>
> On 04/04/2016 10:13 AM, Oliver Wulff wrote:
>
>> Hi JB
>>
>>
>>>>> What you bring is right but users may have different standpoint: lot of
>> people just wants to use decanter as a blackbox solution with
>> elasticsearch and kibana embedded.
>>
>>>
>>>>> I understand this point but we should at least mention in the
>> documentation that it's not the recommended approach to emebed an
>> elasticsearch node within a JVM.
>>
>> Thanks
>> Oli
>> ________________________________________
>> Von: Jean-Baptiste Onofré <jb...@nanthrax.net>
>> Gesendet: Montag, 4. April 2016 09:34
>> An: dev@karaf.apache.org
>> Betreff: Re: Feedback for Canceling Decanter 1.1.0
>>
>> Hi Oli,
>>
>> The vote will stand Wednesday.
>>
>> What you bring is right but users may have different standpoint: lot of
>> people just wants to use decanter as a blackbox solution with
>> elasticsearch and kibana embedded.
>>
>> So, even if your need is different, we have to address both.
>>
>> Kibana 4.5 is not a viable solution as it's related to node.js: Decanter
>> Kibana is not a standard Kibana version: I changed to remove node.js and
>> use pure HTML/js client frontend.
>>
>> Regards
>> JB
>>
>> On 04/04/2016 08:58 AM, Oliver Wulff wrote:
>>
>>> Hi there
>>>
>>>
>>> I'd like to give some feedback regarding the discussion in the vote for
>>> Decanter 1.1.0.
>>>
>>>
>>> It's a nice feature to install kibana and the elasticsearch node within
>>> the same JVM as Karaf, but really only for demo purposes. Elastic doesn't
>>> recommend and support to bundle elasticsearch node within another JVM.
>>> Further, elastic recommends to run elasticsearch node isolated on a
>>> dedicated machine (!) where even nothing else is running to benefit of the
>>> low level features used by elasticsearch.
>>>
>>>
>>>
>>> https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html
>>>
>>> [https://www.elastic.co/static/img/elastic-logo-200.png]<
>>> https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html
>>> >
>>>
>>> Configuration - Elastic<
>>> https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html
>>> >
>>> www.elastic.co
>>> Environment Variablesedit. Within the scripts, Elasticsearch comes with
>>> built in JAVA_OPTS passed to the JVM started. The most important setting
>>> for that is the -Xmx ...
>>>
>>>
>>> Same applies for Kibana 4 dashboards. Usually, you have an elasticsearch
>>> cluster and server hosting the kibana application.
>>>
>>>
>>> What I wanted to say is that whether kibana 4 works in Karaf or not is
>>> not really relevant for a production deployment.
>>>
>>>
>>> Finally, yes, we were very keen on the release 1.1.0 as it brings kafka
>>> with SSL support. We successfully tested this already with the snapshot
>>> version.
>>>
>>>
>>> Do you have a rough idea when the next vote is planned?
>>>
>>>
>>> I'd recommend to use Kibana 4.5 as it brings support for custom labels
>>> and colour customization (already in 4.4). The pre-condition is ES 2.3.
>>>
>>>
>>> Thanks
>>>
>>> Oli
>>>
>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: AW: Feedback for Canceling Decanter 1.1.0
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
IMHO, it's a perfect approach when you don't care about elasticsearch
and just want a monitoring solution embedded in Karaf. Some Decanter
users don't know that they actually use elasticsearch and kibana (they
just see the name in the browser ;)).
If you want more advanced settings, then, you are free to create your
own infrastructure and let Decanter uses it.
Anyway, I will add a note in the documentation.
Regards
JB
On 04/04/2016 10:13 AM, Oliver Wulff wrote:
> Hi JB
>
>>>>
> What you bring is right but users may have different standpoint: lot of
> people just wants to use decanter as a blackbox solution with
> elasticsearch and kibana embedded.
>>>>
> I understand this point but we should at least mention in the documentation that it's not the recommended approach to emebed an elasticsearch node within a JVM.
>
> Thanks
> Oli
> ________________________________________
> Von: Jean-Baptiste Onofré <jb...@nanthrax.net>
> Gesendet: Montag, 4. April 2016 09:34
> An: dev@karaf.apache.org
> Betreff: Re: Feedback for Canceling Decanter 1.1.0
>
> Hi Oli,
>
> The vote will stand Wednesday.
>
> What you bring is right but users may have different standpoint: lot of
> people just wants to use decanter as a blackbox solution with
> elasticsearch and kibana embedded.
>
> So, even if your need is different, we have to address both.
>
> Kibana 4.5 is not a viable solution as it's related to node.js: Decanter
> Kibana is not a standard Kibana version: I changed to remove node.js and
> use pure HTML/js client frontend.
>
> Regards
> JB
>
> On 04/04/2016 08:58 AM, Oliver Wulff wrote:
>> Hi there
>>
>>
>> I'd like to give some feedback regarding the discussion in the vote for Decanter 1.1.0.
>>
>>
>> It's a nice feature to install kibana and the elasticsearch node within the same JVM as Karaf, but really only for demo purposes. Elastic doesn't recommend and support to bundle elasticsearch node within another JVM. Further, elastic recommends to run elasticsearch node isolated on a dedicated machine (!) where even nothing else is running to benefit of the low level features used by elasticsearch.
>>
>>
>> https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html
>>
>> [https://www.elastic.co/static/img/elastic-logo-200.png]<https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html>
>>
>> Configuration - Elastic<https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html>
>> www.elastic.co
>> Environment Variablesedit. Within the scripts, Elasticsearch comes with built in JAVA_OPTS passed to the JVM started. The most important setting for that is the -Xmx ...
>>
>>
>> Same applies for Kibana 4 dashboards. Usually, you have an elasticsearch cluster and server hosting the kibana application.
>>
>>
>> What I wanted to say is that whether kibana 4 works in Karaf or not is not really relevant for a production deployment.
>>
>>
>> Finally, yes, we were very keen on the release 1.1.0 as it brings kafka with SSL support. We successfully tested this already with the snapshot version.
>>
>>
>> Do you have a rough idea when the next vote is planned?
>>
>>
>> I'd recommend to use Kibana 4.5 as it brings support for custom labels and colour customization (already in 4.4). The pre-condition is ES 2.3.
>>
>>
>> Thanks
>>
>> Oli
>>
>>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: AW: Feedback for Canceling Decanter 1.1.0
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
I will add a note for sure.
As I said to Oli, all depends which kind of production we are talking
about ;)
A large scale production, sharing elasticsearch and kibana with
different middleware, I fully agree.
A medium scale production, or only monitoring solution for Karaf itself,
I think people don't care: they want something easy, straight forward,
all in Karaf.
So, maybe we have a biased see on production regarding our experience
with this layer ;)
The good point with Decanter is that we address both ;)
Regards
JB
On 04/04/2016 05:15 PM, Christian Schneider wrote:
> On 04.04.2016 10:13, Oliver Wulff wrote:
>> Hi JB
>>
>> What you bring is right but users may have different standpoint: lot of
>> people just wants to use decanter as a blackbox solution with
>> elasticsearch and kibana embedded.
>> I understand this point but we should at least mention in the
>> documentation that it's not the recommended approach to emebed an
>> elasticsearch node within a JVM.
>>
>> Thanks
>> Oli
>
> I fully agree to add a warning. For demos it makes sense to embed es and
> kibana but for production it is not a good idea.
> I think for production it might make sense to co locate an elastic
> search node on the same machine but I would not do it in the same vm.
>
> Christian
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: AW: Feedback for Canceling Decanter 1.1.0
Posted by Christian Schneider <ch...@die-schneider.net>.
On 04.04.2016 10:13, Oliver Wulff wrote:
> Hi JB
>
> What you bring is right but users may have different standpoint: lot of
> people just wants to use decanter as a blackbox solution with
> elasticsearch and kibana embedded.
> I understand this point but we should at least mention in the documentation that it's not the recommended approach to emebed an elasticsearch node within a JVM.
>
> Thanks
> Oli
I fully agree to add a warning. For demos it makes sense to embed es and
kibana but for production it is not a good idea.
I think for production it might make sense to co locate an elastic
search node on the same machine but I would not do it in the same vm.
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
AW: Feedback for Canceling Decanter 1.1.0
Posted by Oliver Wulff <ow...@talend.com>.
Hi JB
>>>
What you bring is right but users may have different standpoint: lot of
people just wants to use decanter as a blackbox solution with
elasticsearch and kibana embedded.
>>>
I understand this point but we should at least mention in the documentation that it's not the recommended approach to emebed an elasticsearch node within a JVM.
Thanks
Oli
________________________________________
Von: Jean-Baptiste Onofré <jb...@nanthrax.net>
Gesendet: Montag, 4. April 2016 09:34
An: dev@karaf.apache.org
Betreff: Re: Feedback for Canceling Decanter 1.1.0
Hi Oli,
The vote will stand Wednesday.
What you bring is right but users may have different standpoint: lot of
people just wants to use decanter as a blackbox solution with
elasticsearch and kibana embedded.
So, even if your need is different, we have to address both.
Kibana 4.5 is not a viable solution as it's related to node.js: Decanter
Kibana is not a standard Kibana version: I changed to remove node.js and
use pure HTML/js client frontend.
Regards
JB
On 04/04/2016 08:58 AM, Oliver Wulff wrote:
> Hi there
>
>
> I'd like to give some feedback regarding the discussion in the vote for Decanter 1.1.0.
>
>
> It's a nice feature to install kibana and the elasticsearch node within the same JVM as Karaf, but really only for demo purposes. Elastic doesn't recommend and support to bundle elasticsearch node within another JVM. Further, elastic recommends to run elasticsearch node isolated on a dedicated machine (!) where even nothing else is running to benefit of the low level features used by elasticsearch.
>
>
> https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html
>
> [https://www.elastic.co/static/img/elastic-logo-200.png]<https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html>
>
> Configuration - Elastic<https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html>
> www.elastic.co
> Environment Variablesedit. Within the scripts, Elasticsearch comes with built in JAVA_OPTS passed to the JVM started. The most important setting for that is the -Xmx ...
>
>
> Same applies for Kibana 4 dashboards. Usually, you have an elasticsearch cluster and server hosting the kibana application.
>
>
> What I wanted to say is that whether kibana 4 works in Karaf or not is not really relevant for a production deployment.
>
>
> Finally, yes, we were very keen on the release 1.1.0 as it brings kafka with SSL support. We successfully tested this already with the snapshot version.
>
>
> Do you have a rough idea when the next vote is planned?
>
>
> I'd recommend to use Kibana 4.5 as it brings support for custom labels and colour customization (already in 4.4). The pre-condition is ES 2.3.
>
>
> Thanks
>
> Oli
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Feedback for Canceling Decanter 1.1.0
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Oli,
The vote will stand Wednesday.
What you bring is right but users may have different standpoint: lot of
people just wants to use decanter as a blackbox solution with
elasticsearch and kibana embedded.
So, even if your need is different, we have to address both.
Kibana 4.5 is not a viable solution as it's related to node.js: Decanter
Kibana is not a standard Kibana version: I changed to remove node.js and
use pure HTML/js client frontend.
Regards
JB
On 04/04/2016 08:58 AM, Oliver Wulff wrote:
> Hi there
>
>
> I'd like to give some feedback regarding the discussion in the vote for Decanter 1.1.0.
>
>
> It's a nice feature to install kibana and the elasticsearch node within the same JVM as Karaf, but really only for demo purposes. Elastic doesn't recommend and support to bundle elasticsearch node within another JVM. Further, elastic recommends to run elasticsearch node isolated on a dedicated machine (!) where even nothing else is running to benefit of the low level features used by elasticsearch.
>
>
> https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html
>
> [https://www.elastic.co/static/img/elastic-logo-200.png]<https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html>
>
> Configuration - Elastic<https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html>
> www.elastic.co
> Environment Variablesedit. Within the scripts, Elasticsearch comes with built in JAVA_OPTS passed to the JVM started. The most important setting for that is the -Xmx ...
>
>
> Same applies for Kibana 4 dashboards. Usually, you have an elasticsearch cluster and server hosting the kibana application.
>
>
> What I wanted to say is that whether kibana 4 works in Karaf or not is not really relevant for a production deployment.
>
>
> Finally, yes, we were very keen on the release 1.1.0 as it brings kafka with SSL support. We successfully tested this already with the snapshot version.
>
>
> Do you have a rough idea when the next vote is planned?
>
>
> I'd recommend to use Kibana 4.5 as it brings support for custom labels and colour customization (already in 4.4). The pre-condition is ES 2.3.
>
>
> Thanks
>
> Oli
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com