Skip to content

Conversation

@watson
Copy link
Contributor

@watson watson commented Aug 6, 2018

Changes for intake API v2

@watson watson self-assigned this Aug 6, 2018
@watson watson requested a review from Qard August 6, 2018 16:23

[float]
[[performance-transaction-queue]]
=== Transaction Queue
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@Qard are you ok with removing this entire section without replacing it with anything else?

Copy link
Contributor

Choose a reason for hiding this comment

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

We should probably replace it with a new section describing how apiRequestTime and apiRequestSize will impact the performance.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated

@watson watson added the docs label Aug 6, 2018
@watson watson mentioned this pull request Aug 6, 2018
21 tasks
@watson
Copy link
Contributor Author

watson commented Aug 6, 2018

The CI failures are because of the npm bug with the github link in the dependencies


The agent uses a persistent outgoing HTTP request to stream data to the APM Server.
To avoid issues with intermittent proxies and load balancers,
the HTTP request is ended and a new one created at regular intervals or when the size of the reqeust becomes too big.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

s/reqeust/request/

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

Using the <<api-request-size,`apiRequestSize`>> config option,
this time limit can be modified.

Lowering the size limit might be nessecary if dealing with very agressive proxies,
Copy link
Contributor

Choose a reason for hiding this comment

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

necessary*

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

Copy link
Contributor

@Qard Qard left a comment

Choose a reason for hiding this comment

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

The last commit has a typo with "fro" rather than "for" but other than that, LGTM. You can fix that and merge, or squash merge. 😅

@Qard
Copy link
Contributor

Qard commented Aug 8, 2018

There seems to be an asciidoc error. 🤔

WARNING: performance-tuning.asciidoc: line 54: section title out of sequence: expected level 2, got level 3

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants