create-evlog-enricher

To add a built-in enricher to evlog, you introduce a factory function utilizing EnricherOptions to safely merge derived context from request headers and deployment metadata into a single event field across code, tests, and documentation.

An evlog enricher must enforce single event field usage, factory function creation, EnricherOptions configuration, safe merging of context data, case-insensitive header lookup, and maintain no side effects during the event enrichment process.

Yes, you can attach deployment metadata to logging events by creating an evlog enricher that reads context data directly from request headers using case-insensitive lookup and safely merges this information into the event structure.

The best way to expand evlog with new enrichers is following a concrete pattern that updates source code, tests, and documentation simultaneously, ensuring EnricherOptions and safe merging utilities are consistently applied across the package.

An evlog enricher needs a factory function and EnricherOptions to enforce architecture rules, ensuring derived context is safely merged into a single event field without side effects, providing a consistent pattern for adding new enrichers.

Yes, adding an enricher to evlog requires updating tests and documentation end-to-end, as the workflow applies when expanding the package with new enrichers across code, tests, and docs to maintain architectural consistency.