-
Notifications
You must be signed in to change notification settings - Fork 519
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
[Fleet] Document apm fleet integration #4494
Comments
This was referenced Dec 7, 2020
Merged
15 tasks
jalvz
changed the title
[package] Improve documentation
[Fleet] Improve apm package documentation
Dec 16, 2020
jalvz
changed the title
[Fleet] Improve apm package documentation
[Fleet] Document apm fleet integration
Feb 19, 2021
Docs are going to be kinda all over the place while we figure out the best path forward. Here's what we're thinking of adding for
Other tasks:
@jalvz if you have concerns or recommendations, please let me know |
This was referenced Mar 5, 2021
Merged
This was referenced Mar 17, 2021
All documentation for 7.12 has been added. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
The apm package will be released in 7.12 as experimental. Package versions have a version independent of the stack; for this release we will ship 0.1.0. Later we'll probably align with stack versioning.
The documentation template file is at https://github.com/elastic/apm-server/blob/master/apmpackage/apm/0.1.0/_dev/docs/README.template.md
Run
make update
to generate the actual readme file that will be shown in the APM integration page: https://github.com/elastic/apm-server/tree/master/apmpackage/apm/0.1.0/docsTopics for consideration
Usage
apm-server will use data streams with a new indexing strategy. Indices are named after event type, service name, and namespace. Details: https://docs.google.com/document/d/1y56a9fjkLi6Zen5qGC_JKYM9ljYpBA5W0fgdWilcwYc/edit?ts=5f6c1aab#
The service name part of an index is case insensitive and with special characters removed.
If customers don't use RUM, it is recommended that they run Elastic Agent (and therefore apm-server) on the edge machines.
We do not support running apm-server under Elastic Agent standalone: https://www.elastic.co/guide/en/fleet/current/run-elastic-agent-standalone.html
Sourcemaps need to be uploaded directly to Elasticsearch, not apm-server. In the future we might have something so users can upload sourcemaps to Kibana.
Limitations
ILM: we install default ILM policies for all event types, but users need to query Elasticsearch directly to override them. Same for pipelines.
Can't use an Elastic Agent enrolled in a previous release: [Fleet] handle API key upgrade/renewal kibana#85777
No onboarding document: [APM] Getting started: Change logic to check whether APM Server was setup when running under fleet kibana#86462
For sourcemaps and agent central config features customer need to create api keys and them enter those api keys in the apm policy editor. This will be improved in future releases.
Not all settings are supported, the whole list is at https://github.com/elastic/apm-server/blob/master/apmpackage/apm/0.1.0/manifest.yml#L28
Crucially,
mem.queue.*
settings are not supported (yet).References
7.12 meta issue: #4558
GA meta issue: #4636
The text was updated successfully, but these errors were encountered: