Skip to content

Conversation

@beniwohli
Copy link
Contributor

also, added documentation for the sample_rate config, and reduced
the flush_interval setting to 10s

@beniwohli beniwohli force-pushed the tuning-docs branch 3 times, most recently from 7c6162f to ea9a04b Compare February 7, 2018 12:26
beniwohli added a commit to beniwohli/apm-agent-python that referenced this pull request Feb 7, 2018
also, added documentation for the sample_rate config, and reduced
the flush_interval setting to 10s

closes elastic#153
@beniwohli beniwohli requested a review from roncohen February 7, 2018 12:27
* 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we have added

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or "there are"

Copy link
Contributor Author

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

=== 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`,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

below

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and the transaction name

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),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

APM Server (capital s)

beniwohli added a commit to beniwohli/apm-agent-python that referenced this pull request Feb 8, 2018
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
@beniwohli beniwohli closed this in 593e1c7 Feb 8, 2018
@beniwohli beniwohli deleted the tuning-docs branch February 8, 2018 13:02
beniwohli added a commit that referenced this pull request Feb 13, 2018
also, added documentation for the sample_rate config, and reduced
the flush_interval setting to 10s

closes #153
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants