@timestamp field is 0001-01-01T00:00:00.000Z for containers which have the status anything other than "Up...", when I send the data straight to, or through Logstash, into Elasticsearch.
The stats belonging to containers, which are UP, end up in an index named dockbeat-YYYY.MM.DD (where YYYY.MM.DD is today's date); all the stats belonging the other containers end up in an index named dockbeat-0001.01.01 regardless today's date.
Did anyone encountered this behavior? Thanks
@timestamp field is
0001-01-01T00:00:00.000Zfor containers which have the status anything other than "Up...", when I send the data straight to, or through Logstash, into Elasticsearch.The stats belonging to containers, which are UP, end up in an index named
dockbeat-YYYY.MM.DD(where YYYY.MM.DD is today's date); all the stats belonging the other containers end up in an index nameddockbeat-0001.01.01regardless today's date.Did anyone encountered this behavior? Thanks