From cb043ca4985490f7ebe94e4f2502dbcec9ed45eb Mon Sep 17 00:00:00 2001
From: Nate <37554478+servusdei2018@users.noreply.github.com>
Date: Mon, 16 Mar 2026 21:56:27 -0400
Subject: [PATCH] docs(tracing/instrumentation): add pyreqwest to suppoorted
 automatic instrumentation

---
 .../tracing/instrumentation/automatic-instrumentation.mdx       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/platforms/python/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/python/tracing/instrumentation/automatic-instrumentation.mdx
index b1e73f973a3258..7b69826d1cdde5 100644
--- a/docs/platforms/python/tracing/instrumentation/automatic-instrumentation.mdx
+++ b/docs/platforms/python/tracing/instrumentation/automatic-instrumentation.mdx
@@ -27,7 +27,7 @@ Many integrations for popular frameworks automatically capture transactions. If
 Spans are instrumented for the following operations within a transaction:
 
 - Database queries that use SQLAlchemy or the Django ORM
-- HTTP requests made with HTTPX, requests, or the stdlib
+- HTTP requests made with HTTPX, pyreqwest, requests, or the stdlib
 - Spawned subprocesses
 - Redis operations