-
Notifications
You must be signed in to change notification settings - Fork 234
added documentation on how to reduce overhead #153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
7c6162f to
ea9a04b
Compare
also, added documentation for the sample_rate config, and reduced the flush_interval setting to 10s closes elastic#153
docs/tuning.asciidoc
Outdated
| * Elasticsearch storage | ||
|
|
||
| We invested and continue to invest a lot of effort to keep the overhead of using Elastic APM as low as possible. | ||
| But because every deployment is different, we added some knobs you can turn to adapt it to your specific needs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we have added
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or "there are"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm yes, "there are" seems better
docs/tuning.asciidoc
Outdated
| === Transaction Sample Rate | ||
|
|
||
| The most straight forward way to reduce the overhead of the agent is to tell the agent to do less. | ||
| If you set the <<config-transaction-sample-rate,`transaction_sample_rate`>> to a value bellow `1.0`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
below
docs/tuning.asciidoc
Outdated
| If you set the <<config-transaction-sample-rate,`transaction_sample_rate`>> to a value bellow `1.0`, | ||
| the agent will randomly sample only a subset of transactions. | ||
| If a transaction is not sampled, the agent has to do a lot less work, | ||
| as we only record the overall transaction time and the result for unsampled transactions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and the transaction name
docs/tuning.asciidoc
Outdated
| To reduce the load on the APM server, the agent does not send every transaction up as it happens. | ||
| Instead, it queues them up, and flushes the queue periodically, or when it reaches a maximum size, using a background thread. | ||
|
|
||
| While this reduces the load on the APM server (and to a certain extent on the agent), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
APM Server (capital s)
ea9a04b to
0a61fdc
Compare
also, added documentation for the sample_rate config, and reduced the flush_interval setting to 10s closes elastic#153
also, added documentation for the sample_rate config, and reduced the flush_interval setting to 10s closes elastic#153
0a61fdc to
f4b58bf
Compare
also, added documentation for the sample_rate config, and reduced the flush_interval setting to 10s closes #153
also, added documentation for the sample_rate config, and reduced
the flush_interval setting to 10s