vkryukov
Hi, I’ve created an SQL logger backend using LoggerBackends: GitHub - vkryukov/logger_backends_sql · GitHub.
It safely stores all metadata and can be configured to use an existing Repo and/or Schema.
The simplest setup uses an SQLite3 database for logs:
# config/config.exs
config :logger, LoggerBackends.SQL,
level: :debug,
path: "./logs.sqlite"
Logs will be written to the logs table. You can also use an existing repo and customize the table name:
# config/config.exs
config :logger, LoggerBackends.SQL,
repo: MyApp.Repo,
table_name: "log_messages"
You can use your own Schema for log messages - just ensure the schema module defines a changeset/1 function that accepts time, message, and meta arguments.
Feedback welcome!
Trending in Announcing
Flop is an Elixir library that applies filtering, ordering and pagination parameters to your Ecto queries.
offset-based pagination with...
New
I needed to reuse React components from my Chrome extension in my Phoenix/LiveView backend. I noticed that for Svelte/Vue, there are live...
New
I released Doggo, a collection of unstyled Phoenix components.
https://github.com/woylie/doggo
Features
Unstyled Phoenix components....
New
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hello
Published a new library - ProcessHub!
ProcessHub is a library designed to manage process distribution within the Elixir cluster. ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
It’s not that it’s vocabulary is too advanced. It’s something worse.
I get lost trying to follow even a paragraph written by Claude. It’...
New
This showed up on my feed.. anyone heard of it? Just hype?
Ox Alpha is a reasoning model designed for coding, sustained ag...
New
Hey folks,
I just published a post about Hologram’s funding and where the project goes next - the short version:
Curiosum as Main Spons...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security










Showing Posts 1 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
vkryukov
While we are here, I would like people’s thoughts on the best way to configure the backend during the runtime.
LoggerBackendsoffersconfigure/2, which can be called like this:and will send a
:configureevent to the backend that it can capture. The reference implementation forLoggerBackend.Consoleis here. This call will only succeed after a backend has already been added withLoggerBackend.add(LoggerBackends.SQL)(as someone needs to listen to these events).However, you definitely want to set the path to a SQLite log database before adding the backend to perform all the initialization in the backend’s
initfunction.Something like this would be nice
However,
LoggerBackends.add/2only processes the:flushoption and ignores everything else.So my current solution is to expose my own
configure/1to do the runtime config:The previous option with
LoggerBackend.add/2is IMHO cleaner, but requires changing the existing contract.Thoughts?