Skip to content

Commit 011d321

Browse files
committed
docs: mode NOTE block down below code-example
1 parent c4bd8fb commit 011d321

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/performance-tuning.asciidoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -178,8 +178,6 @@ if it is set too low.
178178

179179
An alternative to limiting the maximum number of spans can be to drop spans with a very short duration, as those might not be that relevant.
180180

181-
NOTE: Using a span filter does not reduce the load of recording the spans in your application, but merely filters them out before sending them to the APM Server.
182-
183181
This, however, both reduces the amount of storage needed to store the spans in Elasticsearch, and the bandwidth needed to transport the data to the APM Server from the instrumented application.
184182

185183
This can be implemented by providing a span-filter:
@@ -190,3 +188,5 @@ agent.addSpanFilter(payload => {
190188
return payload.duration < 10 ? null : payload
191189
})
192190
----
191+
192+
NOTE: Using a span filter does not reduce the load of recording the spans in your application, but merely filters them out before sending them to the APM Server.

0 commit comments

Comments
 (0)