# Intercepting worker stdout/stderr and loggers

**URL:** <https://discuss.ray.io/t/intercepting-worker-stdout-stderr-and-loggers/11749>\
**Category:** Ray Core\
**Created:** [August 10, 2023, 5:15pm UTC](https://discuss.ray.io/t/intercepting-worker-stdout-stderr-and-loggers/11749 "2023-08-10T17:15:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mil.ad](https://avatars.discourse-cdn.com/v4/letter/m/82dd89/32.png) [@mil.ad](https://discuss.ray.io/u/mil.ad)\
**Post date:** [August 10, 2023, 5:15pm UTC](https://discuss.ray.io/t/intercepting-worker-stdout-stderr-and-loggers/11749/1 "2023-08-10T17:15:33Z")

</div>

Are there any low (ish) level hooks in ray to intercept what workers print to stdout/stdout or log via an actual logger? Let’s say some of my workers are printing things that I’d like to filter out in the driver side, if everything from a worker was sent to driver through a python loggger’s log functions then I could simply attach a filter to it but I think they’re passed at a lower level?

---

<div class="post-metadata">

**Author:** ![yic](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/yic/32/437_2.png) [@yic](https://discuss.ray.io/u/yic)\
**Post date:** [August 17, 2023, 7:56pm UTC](https://discuss.ray.io/t/intercepting-worker-stdout-stderr-and-loggers/11749/2 "2023-08-17T19:56:50Z")

</div>

Here are the docs for ray log [Configuring Logging — Ray 2.6.1](https://docs.ray.io/en/latest/ray-observability/user-guides/configure-logging.html)

The logs work in this way, each node, we have a monitor check whether there is anything new or not. Then it’s streaming from the node to the driver. So streaming happens inside, and logging is something that can be configured