You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/integrations/use_cases/web_frameworks.md
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,10 @@ Otherwise, check if your server uses [WSGI](../wsgi.md) or [ASGI](../asgi.md) an
15
15
16
16
## Capturing HTTP server request and response headers
17
17
18
-
There are three environment variables to tell the OpenTelemetry instrumentation libraries to capture request and response headers:
18
+
Some methods (e.g. `logfire.instrument_fastapi()`) allow you to pass `capture_headers=True` to record all request and response headers in the spans,
19
+
and that's all you usually need.
20
+
21
+
If you want more control, there are three environment variables to tell the OpenTelemetry instrumentation libraries to capture request and response headers:
(although usually it's better to rely on **Logfire**'s [scrubbing](../../guides/advanced/scrubbing.md) feature)
51
+
45
52
## Query HTTP requests duration per percentile
46
53
47
54
It's usually interesting to visualize HTTP requests duration per percentile. Instead of having an average, which may be influenced by extreme values, percentiles allow us know the maximum duration for 50%, 90%, 95% or 99% of the requests.
0 commit comments