# Configuring root logger in task/actor

**URL:** <https://discuss.ray.io/t/configuring-root-logger-in-task-actor/6186>\
**Category:** Ray Core\
**Created:** [May 19, 2022, 8:32am UTC](https://discuss.ray.io/t/configuring-root-logger-in-task-actor/6186 "2022-05-19T08:32:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![shiranbi](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@shiranbi](https://discuss.ray.io/u/shiranbi)\
**Post date:** [May 19, 2022, 8:32am UTC](https://discuss.ray.io/t/configuring-root-logger-in-task-actor/6186/1 "2022-05-19T08:32:41Z")

</div>

- Low: It annoys or frustrates me for a moment.

In the documentation [Logging — Ray 1.12.1](https://docs.ray.io/en/latest/ray-observability/ray-logging.html#how-to-set-up-loggers) the root logger is being configured  
I am wondering if it is ok to change the root logger configuration for each actor / task as it affects the entire process including ray infra?  
Its not just changing the logging level but can be adding/removing handlers/filters.

---

<div class="post-metadata">

**Author:** ![ericl](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/ericl/32/133_2.png) [@ericl](https://discuss.ray.io/u/ericl)\
**Post date:** [May 19, 2022, 9:17pm UTC](https://discuss.ray.io/t/configuring-root-logger-in-task-actor/6186/2 "2022-05-19T21:17:07Z")

</div>

Hey @shiranbi , it may affect Ray’s internal logging if you change the root logger, but that in general should be fine (no different from changing the system log config)— nothing will break.

To be sure you aren’t changing the Ray logging, you could create a child logger and configure that explicitly.

---

<div class="post-metadata">

**Author:** ![shiranbi](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@shiranbi](https://discuss.ray.io/u/shiranbi)\
**Post date:** [May 20, 2022, 5:16am UTC](https://discuss.ray.io/t/configuring-root-logger-in-task-actor/6186/3 "2022-05-20T05:16:20Z")

</div>

Just as I planned to do (creating a child logger)  
my issue is more with the example in the documentation than anything else.  
it seems like the example suggests changing the root logger is the correct way to go (I wanted to check by posting this question that it isn’t necessary true and I wasn’t missing anything)  
Maybe for log level it isn’t that harmful but I think the example should reflect the preferred method to configure the logger in all cases