# Impact v0.0.1 - Table of Contents

> OpenTelemetry-native LLM/AI tracing SDK for Elixir, exporting to Impact via OTLP.

## Modules

- [Impact](Impact.md): Impact is an OpenTelemetry-native SDK for capturing LLM/AI traces from Elixir
applications and exporting them to Impact via OTLP.
- [Impact.Bedrock](Impact.Bedrock.md): Span helpers for AWS Bedrock Converse-style API calls.
- [Impact.Config](Impact.Config.md): Resolves Impact configuration from `init/1` options and environment variables.
- [Impact.Context](Impact.Context.md): Stores Impact request context on the current OpenTelemetry baggage so that
the canonical `impact.context.<key>` attributes ride with the OTel context
across process boundaries (GenServer calls, Tasks, anywhere
`OpenTelemetry.Ctx.attach/1` is used).
- [Impact.Instrumentation.Bedrock](Impact.Instrumentation.Bedrock.md): Auto-instrumentation for AWS Bedrock LLM calls made via `Req`.
- [Impact.Instrumentation.OpenAI](Impact.Instrumentation.OpenAI.md): Auto-instrumentation for OpenAI-compatible Chat Completions endpoints via
`Req`. Works for OpenAI proper (`api.openai.com`), Azure OpenAI, and the
OpenAI-compatible AWS Bedrock endpoint (`bedrock-*.api.aws`).
- [Impact.Otel](Impact.Otel.md): Provider lifecycle: bootstrap / attach according to `Impact.Config.mode`.
- [Impact.Propagator](Impact.Propagator.md): Cross-process OpenTelemetry context propagation.
- [Impact.Runtime](Impact.Runtime.md): One-call runtime configuration. Designed to be invoked from `config/runtime.exs`
in a Phoenix/Mix application — BEFORE any application starts — so the
`:opentelemetry` and `:opentelemetry_exporter` supervision trees boot with
Impact's OTLP endpoint and auth header already wired in.
- [Impact.Tool](Impact.Tool.md): Span helpers for LLM tool / function calls. Provider-agnostic — works for any
agent loop where the LLM emits structured tool requests and the app executes
them.
- [Impact.Trace](Impact.Trace.md): Manual span helper. Emits the canonical Impact trace attributes