...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
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
Hi there,
did you find a solution for this meanwhile? I have the same problem here.
Any help is very welcomed?
Thanks - cheers
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it,
Hi,
I have the exact problem.
Did you find a soution to this?
cheers
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to graylog2+unsubscr...@googlegroups.com.
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
Hi there,
we have incoming events where a date field is being recognized as a string
instead of being recogniized as a date.
With the extractor we tried a conversion.
In Kibana we still see the incoming events the date being recognized as a
string.
Does someone has a hint how to fix this?
