Versions:
- Filebeat v7.9.1
- Elastisearch v 7.9.1
- Kibana v7.9.1
On windows.
I have a pipeline.json file that describes the ingest part of my module
{
"description": "Pipeline for parsing aaa server logs.",
"processors": [
{
"grok": {
"field": "message",
"patterns": [
"^%{NUMBER:aaa.server.processid}%{SPACE}%{TIMESTAMP_ISO8601:aaa.server.timestamp}%{SPACE}%{LOGLEVEL:aaa.server.severity}%{SPACE}:%{SPACE}(?:\\[%{IPORHOST:aaa.server.shortcategory}\\])?%{SPACE}(?:\\[%{DATA:aaa.server.threadid}\\])?%{GREEDYDATA:aaa.server.message}"
]
},
"date": {
"field": "aaa.server.timestamp",
"formats": ["yyyy-MM-dd HH:mm:ss,SSS","ISO8601"],
"on_failure": [{"append": {"field": "date.error.message", "value": "{{ _ingest.on_failure_message }}"}}]
}
}
],
"on_failure": [{
"set": {
"field" : "error.message",
"value" : "{{ _ingest.on_failure_message }}"
}
}
]
}
When i start filebeat this is transferred to elastisearch/kibana and if i click the link filebeat-7.9.1-aaa-server-pipeline on "Ingest Node Pipelines" i see the correct json on the right handside of the screen. But when i press edit on the pipeline, the whole date part is gone. The data ingested is not handled correctly with regards to the date part. @timestamp is not updated as described in the json.
manually adding a date processor, as described in the json file fixes the parsing problem.