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/http-clients/aiohttp.md
+119Lines changed: 119 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,6 +42,125 @@ if __name__ == "__main__":
42
42
43
43
The keyword arguments of `logfire.instrument_aiohttp_client()` are passed to the `AioHttpClientInstrumentor().instrument()` method of the OpenTelemetry aiohttp client Instrumentation package, read more about it [here][opentelemetry-aiohttp].
44
44
45
+
## Configuration
46
+
47
+
The `logfire.instrument_aiohttp_client()` method accepts various parameters to configure the instrumentation.
48
+
49
+
!!! note
50
+
The aiohttp client instrumentation captures request and response headers, and response bodies. Request bodies are not captured.
51
+
52
+
53
+
### Capture HTTP Headers
54
+
55
+
By default, **Logfire** doesn't capture HTTP headers. You can enable capturing both request and response headers by setting the `capture_headers` parameter to `True`.
The `url_filter` keyword argument can be used to modify the URL that's recorded in spans. Here's an example of how to use this to redact query parameters:
0 commit comments