-
Notifications
You must be signed in to change notification settings - Fork 151
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
[DevOps] Elastic APM #580
base: develop
Are you sure you want to change the base?
[DevOps] Elastic APM #580
Conversation
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 think this looks good.
When I run this locally I get a stream of errors where the app is attempting to connect to the metrics server.
Is there a way to prevent this (maybe with an env variable or standard convention) if the metrics server is not expected to be running?
@jlubken That should be possible, let me see how I can accomplish that. We also have a |
@jlubken It looks like the capability to do this will be available in a future release with an environment variable. If you want it sooner than that, I could try and do something with the logging object |
108c24d
to
e278739
Compare
@jlubken I have added the configuration to disable APM locally. Should resolve that issue. I can add some instructions and methods in case Developers do want to run APM locally so they can test out different instrumentation options. Let me know what sounds best to you. cc: @MooseQuest |
#566
Changelog entry
Added annotations and alterations to methods to allow them to be instrumented with Elastic APM.
There is additional functionality like error message logging, which can be added but this gets the base line instrumentation and metrics
Additional info
This is noted in the APM.md, but in order for this to work there must be an active APM server available and configured with environment variables
Pull Request Checklist
For Reviewer