remote/datasette
1
0
Fork 0
mirror of https://github.com/simonw/datasette.git synced 2026-09-25 19:34:09 +02:00
Code Issues Projects Releases Packages Wiki Activity

Typo fixes

Browse source
This commit is contained in:
Simon Willison 2026-09-24 12:09:29 -07:00
commit 0361afb12e
2 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/changelog.rst
View file

@ -9,7 +9,7 @@ Changelog
1.0a41 (2026-09-24)
-------------------
OpenTelemetry support, a new JavaScript AI for creating modal dialogs, and several smaller bug fixes.
OpenTelemetry support, a new JavaScript API for creating modal dialogs, and several smaller bug fixes.
OpenTelemetry
~~~~~~~~~~~~~

6
docs/internals.rst
View file

@ -2538,7 +2538,7 @@ Or using ``uv run``:
This will output pretty-printed JSON telemetry to your console, representing requests and database queries executed by Datasette.
To use an exporter endpoint, set ``OTEL_EXPORTER_OTLP_ENDPOINT`` to a URL, set ``OTEL_TRACES_EXPORTER`` to ``oltp``, and set the other exporters to ``none``:
To use an exporter endpoint, set ``OTEL_EXPORTER_OTLP_ENDPOINT`` to a URL, set ``OTEL_TRACES_EXPORTER`` to ``otlp``, and set the other exporters to ``none``:
.. code-block:: bash
@ -2549,7 +2549,7 @@ To use an exporter endpoint, set ``OTEL_EXPORTER_OTLP_ENDPOINT`` to a URL, set `
OTEL_TRACES_EXPORTER=otlp \
opentelemetry-instrument datasette mydb.db
On macOS one easy option for a port 4317 OLTP endpoint is `otel-tui <https://github.com/ymtdzzz/otel-tui>`__:
On macOS one easy option for a port 4317 OTLP endpoint is `otel-tui <https://github.com/ymtdzzz/otel-tui>`__:
.. code-block:: bash
@ -2651,7 +2651,7 @@ Metric reference
Spans describe events; metrics describe levels and rates. Metrics can be used to answer questions like "Am I saturating my :ref:`setting_num_sql_threads` threads right now?". Trace sampling drops a portion of traces but does not drop any metrics.
Datasette configures duration histogram in **seconds**. OpenTelemetry's default boundaries are tuned for milliseconds but these would file every SQLite query into a single bucket, making quantile queries meaningless.
Datasette configures duration histograms in **seconds**. OpenTelemetry's default boundaries are tuned for milliseconds but these would file every SQLite query into a single bucket, making quantile queries meaningless.
This reference is also generated from ``datasette/telemetry_registry.py``: