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

Include the APM agent in production builds #70497

Closed
1 task done
joshdover opened this issue Jul 1, 2020 · 4 comments
Closed
1 task done

Include the APM agent in production builds #70497

joshdover opened this issue Jul 1, 2020 · 4 comments
Assignees
Labels
enhancement New value added to drive a business result performance Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@joshdover
Copy link
Contributor

joshdover commented Jul 1, 2020

In order to enable collection of APM instrumentation data in production, we should start shipping the APM agent in production builds. This needs to be changed for both the Node.js agent and the RUM agent on the frontend.

The agent is currently not included at all in production builds of Kibana.

Blockers:

@joshdover joshdover added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc performance enhancement New value added to drive a business result labels Jul 1, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform (Team:Platform)

@vigneshshanmugam
Copy link
Member

@joshdover The blocker should be fixed by #74658, We are good to go from agent perspective.

@tylersmalley
Copy link
Contributor

Thanks @vigneshshanmugam!

@joshdover
Copy link
Contributor Author

Closed by #78697

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result performance Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

4 participants