# stderr appears at info level in logs

**URL:** <https://community.fly.io/t/stderr-appears-at-info-level-in-logs/10065>\
**Category:** Questions / Help\
**Tags:** logs\
**Created:** [January 15, 2023, 1:53pm UTC](https://community.fly.io/t/stderr-appears-at-info-level-in-logs/10065 "2023-01-15T13:53:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pan](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/pan/32/16505_2.png) [@pan](https://community.fly.io/u/pan)\
**Post date:** [January 15, 2023, 1:53pm UTC](https://community.fly.io/t/stderr-appears-at-info-level-in-logs/10065/1 "2023-01-15T13:53:13Z")

</div>

I have noticed that stderr output from my apps shows in the monitoring view at ‘info’ level. Tested with nodejs console.error and process.stderr.write. The only error level logs I can see are from the Fly proxy.

I have a vector/loki/grafana setup in Fly and would like to alert and query based on log level, but since the correct level is not applied this is impossible without attaching additional information to the logs.

Is this something I’ve got wrong or is it a current platform limitation?

Thanks

---

<div class="post-metadata">

**Author:** ![Caperious](https://avatars.discourse-cdn.com/v4/letter/c/ee59a6/32.png) [@Caperious](https://community.fly.io/u/Caperious)\
**Post date:** [May 5, 2026, 1:33pm UTC](https://community.fly.io/t/stderr-appears-at-info-level-in-logs/10065/2 "2026-05-05T13:33:39Z")

</div>

Was this ever resolved / how did u get around it?

---

<div class="post-metadata">

**Author:** ![mayailurus](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/mayailurus/32/17593_2.png) [@mayailurus](https://community.fly.io/u/mayailurus)\
**Post date:** [May 5, 2026, 4:26pm UTC](https://community.fly.io/t/stderr-appears-at-info-level-in-logs/10065/3 "2026-05-05T16:26:13Z")

</div>

This is a platform limitation, like @pan guessed; everything is `[info]`. The only workaround is “attaching additional information”, along the lines that were alluded to up above.

JSON is one widely used way to accomplish that: people change their app to emit single-line JSON blobs and then configure their [self-managed Vector instances](https://fly.io/docs/monitoring/exporting-logs/) to transform those into the correct log level, message, etc.

(People who are serious about logs generally do want their own Vector instance…)