For those of you having this issue the steps for fixing are below, most
steps are directly from the link Jochen provided:
Create a new file on the ES server named graylog-custom-mapping.json
Put this information in that file
{
"template": "graylog_*",
"mappings" : {
"message" : {
Did you ever find a solution to this? I am having the same issue on a
graylog 2.0 server.
On Monday, May 2, 2016 at 5:03:48 AM UTC-4, oliv@gmail.com wrote:
>
> And I also upgraded to graylog 2.0GA
>
> Le lundi 2 mai 2016 11:01:10 UTC+2, oliv@gmail.com a écrit :
>>
>> I've just upgraded
