I know what you mean! The next (and most probably last) preview
version will have almost none of those warnings left. :)

On Thu, Jan 2, 2014 at 10:30 PM, Miguel Cruz <[email protected]> wrote:
> I had setup graylog2 before and loved it. Now im in a new place and im
> trying to introduce it (to keep away from splunk).
> I have setup 20.0 currenlty BUT the fact that I can't disable all the huge
> warnings about not being production ready keeps me from showing it off now.
>
> I can always email my folks saying its not production ready and stuff but
> its another thing when they login and 1st thing they see in red is "Not
> production ready" :)
> I do understand you have to protect yourself from liabilities. I just wish
> there was a way to suppress them.
>
>
> Cheers,
> -Miguel
>
>
> On Thursday, January 2, 2014 4:21:47 PM UTC-5, lennart wrote:
>>
>> The version *must* be exactly v0.90.2 - The ElasticSearch
>> communication format changes between minor versions from time to time
>> and causes incompatibility.
>>
>> Unfortunately <v0.20.0 is not compatible to v0.20.0 at all. The
>> configuration itself did not change too much (a lot of config
>> variables gone and/or now in the web interface frontend) but
>> everything else changed so much that we do not provide a complete
>> upgrade path. Coming versions will have a documented way to upgrade
>> but v0.20.0 is such a huge step forward that we cannot provide a
>> complete upgrade path.
>>
>> If you are just starting with Graylog2 I recommend starting with
>> v0.20.0 right away. The first RC version will be available really
>> soon.
>
> --
> You received this message because you are subscribed to the Google Groups
> "graylog2" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"graylog2" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to