[graylog2] Re: date being recognized as a string

2016-04-14 Thread mantica . msys
...An Update: Graylog created an error. Oh no, something went wrong! (You caused a org.graylog2.restclient.lib.APIException. API call failed POST http://@127.0.0.1:12900/system/deflector/cycle returned 500 Internal Server Error body: {"type":"ApiError","message":"mapping [properties]"}) With

[graylog2] Re: date being recognized as a string

2016-04-14 Thread mantica . msys
Hi Jochen, actually we already did this step. We tried this: curl -XPUT http://localhost:9200/_template/timestamp -d' { "template": "*", "mappings": { "_default_": { "@timestamp": { "type": "date", "format": "dateOptionalTime" } } } } ' Any clues how to

[graylog2] Re: date being recognized as a string

2016-04-14 Thread Jochen Schalanda
Hi, if you want to ensure that a document field has always the same type, you'll have to create a custom index mapping ( https://www.elastic.co/guide/en/elasticsearch/reference/1.7/mapping.html) and make sure it will be applied to new indices by creating an index template with your custom

[graylog2] Re: date being recognized as a string

2016-04-14 Thread mantica . msys
Hi all, I would like to give some details. We have a field @timestamp. But it is in the false format. It is recognized as string instead as beging recognized as date. We defined the input as being JSON. The extractor defnitions seemed to be clean. With this extractor we should have had as a