# Issue while parsing the kubernetes container logs message to individual fields to root document

**URL:** <https://discuss.elastic.co/t/issue-while-parsing-the-kubernetes-container-logs-message-to-individual-fields-to-root-document/371009>\
**Category:** Logs\
**Created:** [November 25, 2024, 8:28am UTC](https://discuss.elastic.co/t/issue-while-parsing-the-kubernetes-container-logs-message-to-individual-fields-to-root-document/371009 "2024-11-25T08:28:04Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Kay\_Khan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kay_khan/32/45028_2.png) [@Kay\_Khan](https://discuss.elastic.co/u/Kay_Khan)\
**Post date:** [November 26, 2024, 4:29pm UTC](https://discuss.elastic.co/t/issue-while-parsing-the-kubernetes-container-logs-message-to-individual-fields-to-root-document/371009/2 "2024-11-26T16:29:07Z")

</div>

Hello

> [@Nginx ingress controller integration is not working](https://discuss.elastic.co/t/nginx-ingress-controller-integration-is-not-working/352592):
>
> Hi, we have enabled the kubernetes and nginx ingress controller integration on the elastic agent [managed with fleet] but the access & error logs are not coming and getting the below errors. 04:19.949 elastic\_agent [elastic\_agent][error] Unit state changed filestream-default-filestream-container-logs-9ddb18cb-f703-42b1-8593-e78dd99e6134-kubernetes-08d5e576-8558-4339-84a9-0e9891aba20d.speaker (HEALTHY-\>FAILED): Failed: pid '2393669' exited with code '-1' 14:04:19.949 elastic\_agent [elastic…

How did you resolve this issue? In the above thread?

---

_[View the full topic](https://discuss.elastic.co/t/issue-while-parsing-the-kubernetes-container-logs-message-to-individual-fields-to-root-document/371009)._
