# Change Log Levels for Standalone Elastic Agent

**URL:** <https://discuss.elastic.co/t/change-log-levels-for-standalone-elastic-agent/324243>\
**Category:** Elastic Agent\
**Created:** [January 30, 2023, 3:27pm UTC](https://discuss.elastic.co/t/change-log-levels-for-standalone-elastic-agent/324243 "2023-01-30T15:27:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DougR](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dougr/32/48095_2.png) [@DougR](https://discuss.elastic.co/u/DougR)\
**Post date:** [January 30, 2023, 3:27pm UTC](https://discuss.elastic.co/t/change-log-levels-for-standalone-elastic-agent/324243/1 "2023-01-30T15:27:23Z")

</div>

I am deploying Elastic Agent to my Kubernetes cluster as a standalone agent. Default log level is info. I would like to change the log level for the agent and ALL beats to `warning`. I've updated my agent.yml to:

```auto
agent.logging.level: 'warning`

```

per the documentation. This appears to update the log level for the agent itself, but not for the beats running inside the container, as they still start up with `-E logging.level=info`.

How can I update this?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 27, 2023, 3:28pm UTC](https://discuss.elastic.co/t/change-log-levels-for-standalone-elastic-agent/324243/2 "2023-02-27T15:28:18Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.