# Prevent remote worker STDOUT log to add the name/pid decorator

**URL:** <https://discuss.ray.io/t/prevent-remote-worker-stdout-log-to-add-the-name-pid-decorator/5711>\
**Category:** Ray Core\
**Created:** [April 6, 2022, 6:24pm UTC](https://discuss.ray.io/t/prevent-remote-worker-stdout-log-to-add-the-name-pid-decorator/5711 "2022-04-06T18:24:14Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jaimehrubiks](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/jaimehrubiks/32/2369_2.png) [@jaimehrubiks](https://discuss.ray.io/u/jaimehrubiks)\
**Post date:** [April 6, 2022, 6:24pm UTC](https://discuss.ray.io/t/prevent-remote-worker-stdout-log-to-add-the-name-pid-decorator/5711/1 "2022-04-06T18:24:14Z")

</div>

**How severe does this issue affect your experience of using Ray?**

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

**My issue**  
My software uses logging.getLogger(\_\_name\_\_).warning to log information to **stdout**.

My output is in JSON, and I grab it from kubernetes logging ELK stack (filebeat-\>ES).

Log example  
{ “error\_type”: 1, “message”: “…” }

**My issue is that** if I try to log from a **remote** function, I get this decorator:  
(remote\_function\_name pid=560) { “error\_type”: 2, “message”: “…” }

And because of this, my ELK stack is not able to parse this JSON… Any way to disable the worker STDOUT decorator?

---

<div class="post-metadata">

**Author:** ![Clark\_Zinzow](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/clark_zinzow/32/445_2.png) [@Clark\_Zinzow](https://discuss.ray.io/u/Clark_Zinzow)\
**Post date:** [April 22, 2022, 5:06pm UTC](https://discuss.ray.io/t/prevent-remote-worker-stdout-log-to-add-the-name-pid-decorator/5711/2 "2022-04-22T17:06:09Z")

</div>

Hi @jaimehrubiks, thank you for posting!

@sangcho Do you know if it’s possible to remove the task function name and PID prefix from these logs?

---

<div class="post-metadata">

**Author:** ![sangcho](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/sangcho/32/425_2.png) [@sangcho](https://discuss.ray.io/u/sangcho)\
**Post date:** [May 5, 2022, 2:24am UTC](https://discuss.ray.io/t/prevent-remote-worker-stdout-log-to-add-the-name-pid-decorator/5711/3 "2022-05-05T02:24:19Z")

</div>

No. There’s no way to remove this currently.

@jaimehrubiks can you create an issue to our Github to support this?

---

<div class="post-metadata">

**Author:** ![simenandresen](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/simenandresen/32/1066_2.png) [@simenandresen](https://discuss.ray.io/u/simenandresen)\
**Post date:** [August 22, 2024, 9:20am UTC](https://discuss.ray.io/t/prevent-remote-worker-stdout-log-to-add-the-name-pid-decorator/5711/4 "2024-08-22T09:20:33Z")

</div>

Any update on this? The fact that the ray logs cannot be output as proper JSON is quite a problem when searching through our logs in GCP.

---

<div class="post-metadata">

**Author:** ![Sam\_Chan](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/sam_chan/32/5011_2.png) [@Sam\_Chan](https://discuss.ray.io/u/Sam_Chan)\
**Post date:** [August 26, 2024, 5:36pm UTC](https://discuss.ray.io/t/prevent-remote-worker-stdout-log-to-add-the-name-pid-decorator/5711/5 "2024-08-26T17:36:35Z")

</div>

Hey @simenandresen! Unfortunately not yet - can you cut a GH feature request so we can add this to our backlog for next Sprint planning?

---

<div class="post-metadata">

**Author:** ![simenandresen](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/simenandresen/32/1066_2.png) [@simenandresen](https://discuss.ray.io/u/simenandresen)\
**Post date:** [August 27, 2024, 7:28am UTC](https://discuss.ray.io/t/prevent-remote-worker-stdout-log-to-add-the-name-pid-decorator/5711/6 "2024-08-27T07:28:25Z")

</div>

Sure @Sam_Chan , created an [issue](https://github.com/ray-project/ray/issues/47354) now.