@chrismichaelps / pudu-lang-log
Structured event logging for Pudu: message templates, enrichment, filtering, formatting, and sinks
0.1.0Apache-2.01
InstallClose
Use @chrismichaelps/pudu-lang-log
Install this release
From your project, run:
pudu install @chrismichaelps/pudu-lang-log@0.1.0An exact version can install a new release immediately. Without a version, pudu follows the 72-hour minimum release age for new resolutions.
pudu install @chrismichaelps/pudu-lang-logThen import it
import PuduLangLog as PuduLangLogTo contribute
git clone https://github.com/chrismichaelps/pudu-lang-log
ADR-0004-settings-through-a-registry.md
ADR-0004 — Settings name registered sinks and enrichers
type: decision status: accepted tags: [decision]
Context
Configuration text chooses sinks and enrichers by name. Pudu cannot look up functions by name at run time, and a configuration file should not reach code the program did not choose to expose.
Decision
[[src/PuduLangLog/Settings/Registry]] maps names to factories that receive the setting's arguments. The standard registry names the console, file, and HTTP sinks and the environment enrichers; a program adds its own with withSink and withEnricher. [[src/PuduLangLog/Domain/Settings]] reads keys into a pure plan first, so every key rule is tested without effects, and [[src/PuduLangLog/Settings]] refuses the whole configuration when any setting cannot be used.
Consequences
- An unknown sink name is an error at startup, never a silently missing sink.
- The registry lists exactly what configuration text can create.
Referenced by
[[CHANGELOG]] · [[decisions/_MOC]] · [[handoffs/2026-09-29-complete-api]] · [[subsystems/Configuration]]