# \#log

**URL:** https://forum.elixirforum.com/tag/log/3825.md

[Latest](https://forum.elixirforum.com/latest.md) · [Categories](https://forum.elixirforum.com/categories.md) · [Tags](https://forum.elixirforum.com/tags.md)

---

## [What do we do with logging in libraries?](https://forum.elixirforum.com/t/what-do-we-do-with-logging-in-libraries/75914)

<div class="topic-metadata">

**Author:** [@martosaur](https://forum.elixirforum.com/u/martosaur)\
**Replies:** 14\
**Last updated:** [July 7, 2026, 4:23pm UTC](https://forum.elixirforum.com/t/what-do-we-do-with-logging-in-libraries/75914 "2026-07-07T16:23:03Z")

</div>

Seriously, what do we do with logs in Elixir? There is seemingly no way to make them good both in dev and prod. This is especially noticeable in libraries, which often choose to simply not log. In my new post I propose…

---

## [Accessing System-Level Logs for Debugging Spontaneous Shutdowns on Raspi Zero](https://forum.elixirforum.com/t/accessing-system-level-logs-for-debugging-spontaneous-shutdowns-on-raspi-zero/62655)

<div class="topic-metadata">

**Author:** [@fireindark707](https://forum.elixirforum.com/u/fireindark707)\
**Replies:** 4\
**Last updated:** [April 22, 2024, 6:22am UTC](https://forum.elixirforum.com/t/accessing-system-level-logs-for-debugging-spontaneous-shutdowns-on-raspi-zero/62655 "2024-04-22T06:22:53Z")

</div>

I’m currently working on a project with Nerves(Nerves Livebook) on a Raspberry Pi Zero, and I’ve encountered a recurring issue where the device spontaneously shuts down. To better understand what’s happening behind the s…

---

## [How to fix \*Bad argument in call to erlang:'++'(\<\<"xxx/crash.log"\>\>, ".3") in lager\_rotator\_default:rotate\_logfile/2 line 84\*](https://forum.elixirforum.com/t/how-to-fix-bad-argument-in-call-to-erlang-xxx-crash-log-3-in-lager-rotator-default-rotate-logfile-2-line-84/61727)

<div class="topic-metadata">

**Author:** [@senggen](https://forum.elixirforum.com/u/senggen)\
**Replies:** 2\
**Last updated:** [February 18, 2024, 1:22pm UTC](https://forum.elixirforum.com/t/how-to-fix-bad-argument-in-call-to-erlang-xxx-crash-log-3-in-lager-rotator-default-rotate-logfile-2-line-84/61727 "2024-02-18T13:22:44Z")

</div>

Erlang/OTP 25 \[erts-13.2.2\] \[source\] \[64-bit\] \[smp:8:8\] \[ds:8:8:10\] \[async-threads:1\] 15:22:35.803 \[error\] gen\_event {lager\_file\_backend,\<\<102,105,115,104,95,99,104,97,105,110,46,108,111,103\>\>} installed in lager\_event …

---

## [Livebook runtime logs?](https://forum.elixirforum.com/t/livebook-runtime-logs/57588)

<div class="topic-metadata">

**Author:** [@yolo007wizard](https://forum.elixirforum.com/u/yolo007wizard)\
**Replies:** 4\
**Last updated:** [August 12, 2023, 5:53pm UTC](https://forum.elixirforum.com/t/livebook-runtime-logs/57588 "2023-08-12T17:53:05Z")

</div>

Does Livebook have a way to create a runtime log file? I’m thinking of a flow where a job evaluates a livebook file in ‘background’ mode with no eyes on it. Lets say a specific livebook runtime encounters some errors and…
