# Docker and System Logs/Metrics from container-based Agent

**URL:** <https://discuss.elastic.co/t/docker-and-system-logs-metrics-from-container-based-agent/322679>\
**Category:** Elastic Agent\
**Created:** [January 8, 2023, 1:04pm UTC](https://discuss.elastic.co/t/docker-and-system-logs-metrics-from-container-based-agent/322679 "2023-01-08T13:04:03Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![Ayush\_Mathur](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ayush_mathur/32/77134_2.png) [@Ayush\_Mathur](https://discuss.elastic.co/u/Ayush_Mathur)\
**Post date:** [January 12, 2023, 10:27am UTC](https://discuss.elastic.co/t/docker-and-system-logs-metrics-from-container-based-agent/322679/14 "2023-01-12T10:27:52Z")

</div>

> [@litronics](#):
>
> `failed to parse date field [2022-12-18 06:23:30] with format [strict_date_optional_time||epoch_millis]`

Since this format is not supported implicitly by ES, guess you need to define your own format in your index template to avoid ingestion failure issues: [format | Elasticsearch Guide [8.6] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-date-format.html#mapping-date-format)  
About the other issue where metrics are not being polled, guess there was another issue opened without any responses: [Metricbeat error about scanning empty io.stat file - Elastic Stack / Beats - Discuss the Elastic Stack](https://discuss.elastic.co/t/metricbeat-error-about-scanning-empty-io-stat-file/308063)

And I see you have already commented on github issue for this 🙂

---

_[View the full topic](https://discuss.elastic.co/t/docker-and-system-logs-metrics-from-container-based-agent/322679)._