The metron-docker project isn’t really intended for a proper deployment. It’s 
basically a dev tool for working on the front end pieces and quick 
experimentation to be honest, the versions aren’t always updated that 

Specifically on the elastic and kibana versions, those are a little behind on 
the project in general but there are some discussions about updating them. If 
you’re interesting in contributing around some of the updates I’m sure it would 
be much appreciated in the community.

For a ‘proper' platform by the way, I would strongly recommend not using the 
docker versions at all, but sticking to the ambari based deployment method, 
which far more tested at scale. 

Hope that helps, and great to hear you’re using Metron,

> On 13 Jul 2017, at 15:29, Antonio Pérez Bautista <> wrote:
> Hi,
> I am working with metron-docker and i see that versions of ElasticSearch and 
> Kibana are old versions.
> Is there any reason for this? Do you think there could be a problem if I 
> upgrade to newer versions both components?
> Thanks!
> P Please consider the environment before printing this e-mail.
> ______________________
> This message including any attachments may contain confidential 
> information, according to our Information Security Management System,
> and intended solely for a specific individual to whom they are addressed.
> Any unauthorised copy, disclosure or distribution of this message
> is strictly forbidden. If you have received this transmission in error,
> please notify the sender immediately and delete it.
> ______________________
> Este mensaje, y en su caso, cualquier fichero anexo al mismo,
> puede contener informacion clasificada por su emisor como confidencial
> en el marco de su Sistema de Gestion de Seguridad de la 
> Informacion siendo para uso exclusivo del destinatario, quedando 
> prohibida su divulgacion copia o distribucion a terceros sin la 
> autorizacion expresa del remitente. Si Vd. ha recibido este mensaje 
> erroneamente, se ruega lo notifique al remitente y proceda a su borrado. 
> Gracias por su colaboracion.
> ______________________

Reply via email to