# Logging off-device

**URL:** <https://forums.balena.io/t/logging-off-device/80769>\
**Category:** Product support\
**Created:** [March 17, 2020, 8:41pm UTC](https://forums.balena.io/t/logging-off-device/80769 "2020-03-17T20:41:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pde](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/pde/32/3324_2.png) [@pde](https://forums.balena.io/u/pde)\
**Post date:** [March 17, 2020, 8:41pm UTC](https://forums.balena.io/t/logging-off-device/80769/1 "2020-03-17T20:41:12Z")

</div>

Folks:

I am about to start deploying balena devices in the field. For regulatory compliance purposes, I need to be able to keep a permanent, long term record of my application’s log events. The balena console is not an adequate solution here.

I thought that I would do what I do in other docker environments: colocate a fluentd container with my application container, and use a logging: statement in docker-compose to send my application’s logs to fluentd and from there on to my central log store in S3.

I see that docker-compose logging: is explicitly not supported in balena, and googling has really not turned up much in terms of people addressing this problem.

I can’t be the first one, can I?

If I say that balena console logging and schemes around periodically calling journalctl are non-starters, how can I get stdout/stderr from my application off of a balena device and into S3?

Thanks

-Pete

---

<div class="post-metadata">

**Author:** ![anujdeshpande](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/anujdeshpande/32/3155_2.png) [@anujdeshpande](https://forums.balena.io/u/anujdeshpande)\
**Post date:** [March 18, 2020, 8:49am UTC](https://forums.balena.io/t/logging-off-device/80769/3 "2020-03-18T08:49:53Z")

</div>

Hi

You can use the Balena SDK to subscribe to device logs - for example, see [this](https://www.balena.io/docs/reference/sdk/node-sdk/#balenalogs--codeobjectcode)  
Would that work for you?