Skip to main content

polars-telemetry

OpenTelemetry instrumentation for Polars query execution.

One span per query carrying the plan, and per-node counters as metrics, to any OTLP collector — or a profile file you open in your browser, with no collector at all.

Both plans, per-node counters and diagnostics for one query in the profile viewer

Install

pip install polars-telemetry          # API only; bring your own OTel SDK
pip install 'polars-telemetry[otlp]'  # with SDK and OTLP exporter
pip install 'polars-telemetry[datadog]'  # for the DogStatsD exporter

Python 3.10+.

Use

import polars_telemetry

polars_telemetry.install()

install() enables polars' query monitoring, which sets the engine affinity to "streaming" and therefore changes how your queries execute — so it never happens on import. uninstall() turns monitoring off but cannot restore the previous affinity; polars exposes no way to read it back.

What you get

A polars.collect span per query, on whatever trace context was active:

  • the plan — scan sources, pushed-down predicates, join types and keys, group-by keys
  • polars.cpu_ms, polars.parallelism, result rows
  • the hottest node and its share of total CPU
  • diagnostics — parallel efficiency, filter selectivity, join amplification, projection efficiency, morsel skew, predicate pushdown, row-group skipping
  • the file, line and function that ran the query, as OpenTelemetry's code.* attributes

Per-node counters — rows, morsels, polls, work-stealing, poll latency, state updates, IO time and bytes — as 15 metric instruments dimensioned by node kind.

Every name is listed in the attribute reference.

Where it goes

Exporter Sends To
OTelExporter, the default a span and per-node metrics your OpenTelemetry SDK
DogStatsdExporter the same metrics, with tags the Datadog Agent, or Telegraf into InfluxDB
FileExporter a profile per query: both plans, every counter a .jsonl file for the viewer
ConsoleExporter a short summary standard error
from datadog import DogStatsd
from polars_telemetry.export.dogstatsd import DogStatsdExporter

statsd = DogStatsd(disable_buffering=False, disable_background_sender=False)
polars_telemetry.install(exporter=DogStatsdExporter(statsd))

exporter takes a list, so several can run at once. Each has a page in the docs, with its options and what it costs.

Profiles without a collector

from polars_telemetry.export.file import FileExporter

polars_telemetry.install(exporter=FileExporter("profiles/session.jsonl"))

One self-contained JSON document per query: both plans with every node property, all 19 per-node counters, the diagnostics, and a fingerprint of the plan shape.

Drop the file on the profile viewer to read both plans, per-node counters, and a diff between two runs of the same shape. It runs entirely in your browser; nothing is uploaded. To try it without a workload of your own, download a TPC-H session from examples/: the 22 queries at scale factor 1 or 10, three runs each.

Label what runs

with polars_telemetry.label("revenue_by_region"):
    report.collect()

The label is on the span and in the profile; nested labels join with /.

Profile a block of code

from polars_telemetry import profile

with profile() as session:
    report = build_report()

session.slowest.call_site  # where the slow one was run
session.write("report.jsonl")  # open in the viewer

Installs instrumentation only if nothing was installed. With an application already instrumented it collects alongside the existing exporter.

Configure

from polars_telemetry import Config

polars_telemetry.install(Config(node_metrics=False))
Option Default Effect
node_metrics True Read per-node counters once at query end
include_plan False Attach the full plan to the span as JSON
call_site True Record the file, line and function that ran the query
redaction None What to mask before exporters see a query; Redaction() masks literal values
redact_literals False Deprecated: use redaction=Redaction()
resource_attributes {} Deprecated: never applied; set them on your OpenTelemetry provider

Your data

Spans carry plan detail: scan paths, column names, join keys and literal predicate values — col("email") == "..." arrives verbatim, because knowing which predicate was slow is usually the point.

  • Config(redaction=Redaction()) masks literal values: text, numbers, dates and times. Redaction(paths=True, call_site=True, labels=True) masks more.
  • redacted(exporter, ...) gives one exporter its own setting, so a shared backend can get a masked copy while a local file keeps full detail.
  • Literals are never used as metric attributes, at any setting.
  • Attributes that can carry user data are listed in polars_telemetry.export.semconv.CARRIES_USER_DATA.

Polars Cloud

If polars-cloud is installed, its observer is wrapped and forwarded to rather than replaced. Both work at once.

License

Apache-2.0. See LICENSE and NOTICE.

Metadata

Release files for polars-telemetry 0.3.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for polars-telemetry 0.3.1
File Size Uploaded
polars_telemetry-0.3.1.tar.gz 523.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for polars-telemetry 0.3.1
File Interpreter ABI Platform
polars_telemetry-0.3.1-py3-none-any.whl Python 3 none any Details

Total release size: 583.7 kB

Release files / polars_telemetry-0.3.1.tar.gz

Download URL polars_telemetry-0.3.1.tar.gz
Size 523.4 kB
Tags Source
SHA-256 checksum
How to use checksums
8ad59bb4b5045e8f1386b51a9b0eb7358892ae1f8c0446acc74fb2333593c263
BLAKE2b-256 checksum
How to use checksums
23d06734c25ffdf36bb6d43be05c9498de505a7f81a8c13fef151ccf655e355a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.

Transparency log

Release files / polars_telemetry-0.3.1-py3-none-any.whl

Download URL polars_telemetry-0.3.1-py3-none-any.whl
Size 60.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d8068754b4c68ba0bddfc5baa8d8d98ed12abdb57511b8b9adcc2913237e43a5
BLAKE2b-256 checksum
How to use checksums
f408afc360d5646ae995c2856dda9bc2a1f659dfac68c6da33a54f68cb7b72a1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.

Transparency log

Release history Release notifications | RSS feed

0.4.0

2 release files

This release

0.3.1 This release

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page