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

Define deployment profiles for APM and create best practices for it. #1293

Closed
simitt opened this issue Aug 16, 2018 · 4 comments
Closed

Define deployment profiles for APM and create best practices for it. #1293

simitt opened this issue Aug 16, 2018 · 4 comments
Milestone

Comments

@simitt
Copy link
Contributor

simitt commented Aug 16, 2018

Come up with some default customer profiles and different default values and best practices around them (e.g. having different apm-server.discover.yml, apm-server.highload.yml, apm-server.microservices.yml, ..)

@simitt simitt added this to the 6.5 milestone Aug 17, 2018
@alvarolobato alvarolobato changed the title Define customer profiles for APM and create best practices for it. Define deployment profiles for APM and create best practices for it. Aug 20, 2018
@alvarolobato alvarolobato modified the milestones: 6.5, 6.6 Nov 20, 2018
@alvarolobato
Copy link

alvarolobato commented Dec 4, 2018

We should discuss if the best approach is creating different yml files or just document the sizes.
Using the sizing we recently did should be enough for these values.

@elastic/apm-server opinions here?

@alvarolobato alvarolobato modified the milestones: 6.6, 7.0 Feb 5, 2019
@graphaelli
Copy link
Member

lowering priority and moving to backlog as we consider alternatives like automatically adjusting configuration based on available resources

@bmorelli25
Copy link
Member

@graphaelli Is there anything we can do now to resolve this issue, or are we still not sure of the path forward?

@graphaelli
Copy link
Member

Thanks for the mention, we can remove the docs label and mention #2631 as that's likely when we can take a real look at this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants