Skip to content

providers

etrack.infra.config.providers

infra/config/providers: the providers' knobs — one block per driver and adapter, each field its env variable.

The value types every provider takes beside them: a provider is built with keyword arguments (OtlpConfig's keys, HttpConfig's…), and what it is not handed infra/defaults fills from these fields. ETRACK_HTTP_* configures the HTTP driver read from the environment; a custom driver built on HttpDriver passes its own endpoint and auth — one endpoint per instance, as many instances as systems.

AnyioConfig

Bases: TypedDict

An AnyioAdapter's keyword arguments: events queued per sink.

Encoding

Bases: StrEnum

How a batch travels: one JSON array, or one JSON object per line (application/x-ndjson).

GranianConfig

Bases: TypedDict

A GranianAdapter's keyword arguments: where the viewer listens, how long opening waits.

HttpConfig

Bases: TypedDict

An HttpDriver's keyword arguments: where it sends, how it signs, batches and retries, the kinds it sends.

LiveConfig

Bases: TypedDict

A LiveAdapter's keyword arguments: frames kept per thread, threads kept, a subscriber's lag.

OtlpConfig

Bases: TypedDict

An OtlpDriver's keyword arguments: its collectors, the signals that leave, how fast, under which service.

OtlpTarget

Bases: BaseModel

One collector: its OTLP/HTTP base URL (signals under /v1/traces, /v1/logs), fixed headers, and how it authenticates (auth: none, headers, bearer, basic, or google — Cloud Trace through the Telemetry API).

PrometheusConfig

Bases: TypedDict

A PrometheusAdapter's keyword arguments: the metrics' prefix and the latency buckets.

ProviderSettings

Bases: BaseSettings

The providers' edges: one block per driver and adapter.