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/tuning.asciidoc
+14-1Lines changed: 14 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,4 +95,17 @@ There are four settings you can modify to control this behavior:
95
95
96
96
As you can see, these settings are divided between app frames, which represent your application code, and library frames, which represent the code of your dependencies. Each of these categories are also split into separate error and span settings.
97
97
98
-
Reading source files inside a running application can cause a lot of disk I/O, and sending up source lines for each frame will have a network and storage cost that is quite high. Turning down these limits will help prevent excessive memory usage.
98
+
Reading source files inside a running application can cause a lot of disk I/O, and sending up source lines for each frame will have a network and storage cost that is quite high. Turning down these limits will help prevent excessive memory usage.
99
+
100
+
[float]
101
+
[[tuning-body-headers]]
102
+
=== Collecting headers and request body
103
+
104
+
You can configure the Elastic APM agent to capture headers of both requests and responses (<<config-capture-headers,`capture_headers`>>),
105
+
as well as request bodies (<<config-capture-body,`capture_body`>>).
106
+
By default, capturing request bodies is disabled.
107
+
Enabling it for transactions may introduce noticeable overhead, as well as increased storage use, depending on the nature of your POST requests.
108
+
In most scenarios, we advise against enabling request body capturing for transactions, and only enable it if necessary for errors.
109
+
110
+
Capturing request/response headers has less overhead on the agent, but can have an impact on storage use.
111
+
If storage use is a problem for you, it might be worth disabling.
0 commit comments