Skip to content
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

[7.x] Instrument Kibana with Elastic APM (#43548) #52186

Merged
merged 1 commit into from
Dec 4, 2019

Conversation

watson
Copy link
Contributor

@watson watson commented Dec 4, 2019

Backports the following commits to 7.x:

Instruments Kibana with Elastic APM by adding the Node.js agent to the
source code. The agent is not turned on by default but can be enabled by
setting the environment variable `ELASTIC_APM_ACTIVE=true` or by
creating an apm config file called `config/apm.dev.js` and setting
`active: true` inside of it.

This implementation is not meant to be used by end-users of Kibana as it
lacks integration with the regular Kibana config file. For now, this is
meant as a useful internal tool for Elastic employees when developing
Kibana.

By default, it's pre-configured with a `serverUrl` pointing to an APM
Server hosted on Elastic Cloud. The data is stored in an ES cluster
accessible only by Elastic employees. These defaults can easily be
overwritten using environment variables or via the custom config file.
@watson watson added the backport label Dec 4, 2019
@watson watson self-assigned this Dec 4, 2019
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@watson watson merged commit c2fac8a into elastic:7.x Dec 4, 2019
@watson watson deleted the backport/7.x/pr-43548 branch December 4, 2019 16:04
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