-
Notifications
You must be signed in to change notification settings - Fork 107
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
Add New Relic application agents #174
Comments
All front applications now have New Relic applications installed, Solr and Harvester agents are pending. |
@dano-reisys We also need to group instances so each application metrics are consolidated. |
Updated description. |
We think this one probably should be broken up into one issue per app. |
This is super old and written for a different infrastructure. For cloud.gov specifically, NR is installed on catalog, inventory and dashboard. The only place we haven't implemented this is our Solr deployment, |
When this story is up for the next sprint: We think it should be broken up into one issue per app.
As an application developer, I need my application configured with New Relic so that I can can monitor and alert across all hosts.
Acceptance criteria
Details
We currently have language-specific playbooks to deploy and configure New Relic for applications. However, this has some deficiencies. The platform has to know details about the application, environments, app names, configuration settings. The platform has to know where to install hooks within the application (wsgi, worker scripts, etc). The platform might install conflicting versions of dependencies, outside of application pinned dependencies. The platform installing New Relic might cause an extra restart, prolonging any service disruption during deploy.
The text was updated successfully, but these errors were encountered: