create-evlog-adapter

To add an evlog adapter for wide events, implement a standard skeleton covering eight touchpoints: source file, build config, package exports, tests, adapters docs page, adapters overview, AGENTS.md entry, and custom docs renumbering.

The evlog adapter skeleton includes a config interface, optional event transformation logic, build configuration entries, package exports, comprehensive tests, and documentation, ensuring seamless integration of new drains like Datadog, Sentry, Loki, or Elasticsearch.

The best way to structure an observability adapter for wide events is enforcing a standard structure with a config interface and optional event transformation, while following naming conventions and update workflows across source, build config, exports, tests, and documentation.

Yes, creating a new evlog adapter requires updating the build config and package exports as part of the eight touchpoints, alongside writing the source file, tests, and documentation to ensure full lifecycle support.

The evlog adapter handles event transformation through an optional event transformation step within the standard adapter structure, allowing custom processing of wide events before they reach drains like Loki or Elasticsearch.

You need to renumber custom docs when adding an evlog adapter if the new adapter entry disrupts existing documentation ordering, as part of the eight touchpoints that include updating the adapters docs page and adapters overview.