-
Notifications
You must be signed in to change notification settings - Fork 525
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
docs: APM integration documentation #6287
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
Chunk level is changing which means a number of links need to be fixed before this PR can be merged: edit: removed because fixed |
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.
@bmorelli25 I took an initial look. I have a couple of remarks already but can also hold off for now until you ping me to take a closer look.
Hey @simitt — sure, any comments/suggestions are appreciated. The goal of this PR so far was to see if it was even possible to combine the APM Overview and APM Server into one book and get it to pass to The next steps, as I see them, are to:
|
edit: removed temp TOC headings |
Are you planning on duplicating information that stays valid with the new managment model? (For example explanation around distributed tracing, transaction sampling, OpenTracing bridges, etc.)? |
Yes. Duplication is unfortunate, but it's the only thing that made sense to me for content that is relevant to both the old way and the new way of doing things:
|
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.
I'm good with merging this in as is and then adding additional content (such as for configuring the apm Integration).
The comments I left can be handled in a follow up.
|
||
Elastic APM consists of four components: *APM agents*, *Elastic Agent*, *Elasticsearch*, and *Kibana*. | ||
|
||
image::./images/apm-architecture.png[Architecture of Elastic APM] |
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.
Another viable scenario will be to host an elastic-agent with an apm integration alongside a user's app, and then have these remote agents enroll via the centrally hosted elastic-agent.
Elastic APM consists of four components: APM agents, Elastic Agent, Elasticsearch, and Kibana.
Technically that is correct, but I think the interesting part for users would be the APM Integration, rather than the Elastic Agent. Could we generally talk about the APM Integration, and then in the concrete setup section, and in the more detailled paragraph below introduce the Elastic Agent to run the Integration?
These are known as events, and can be `spans`, `transactions`, `errors`, or `metrics`. | ||
|
||
* <<data-model-spans>> | ||
* <<data-model-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.
Maybe we could aready de-emphasize the the difference between spans and transactions a bit. They are written to the same data stream now, so maybe let's focus on traces
and then a bit less prominent mention the difference between spans and transactions.
|
||
[source,console] | ||
---- | ||
GET _ingest/pipeline/apm |
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'll have a set of pipelines per datastreams, so this will need to be changed a bit.
Great feedback, @simitt. I'll address in a future PR. |
* fix apmpackage changelog * update to go1.17.1 * make update-beats * Update go.mod to 1.17 * go mod tidy * go mod download all * Makefile: move fields.asciidoc to docs/legacy * Manual tweaks to fields.asciidoc See #6287 * Stop generating fields.asciidoc We won't be updating libbeat fields.yml anymore, so no need to keep regenerating fields.asciidoc. Co-authored-by: Andrew Wilkins <[email protected]>
# Conflicts: # docs/guide/index.asciidoc
* fix apmpackage changelog * update to go1.17.1 * make update-beats * Update go.mod to 1.17 * go mod tidy * go mod download all * Makefile: move fields.asciidoc to docs/legacy * Manual tweaks to fields.asciidoc See elastic/apm-server#6287 * Stop generating fields.asciidoc We won't be updating libbeat fields.yml anymore, so no need to keep regenerating fields.asciidoc. Co-authored-by: Andrew Wilkins <[email protected]>
Summary
/docs/legacy/*
. Retains a temporaryindex.asciidoc
in/docs/
to keep the build working until broken links are addressed/docs/legacy/guide/*
. Retains a temporaryindex.asciidoc
in/docs/guide/
to keep the build working until broken links are addressedintegrations-index.asciidoc
) for the APM User Guide documentation.Build it
To do after this PR is merged
fields.asciidoc
script which was manually overwritten in ab092acRelated issues and PRs