You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an inventory administrator, I want inventory configured with New Relic so that I can can monitor and evaluate blocking requests/weak points in the system.
Acceptance Criteria
GIVEN the inventory playbook is run on staging
WHEN I look at New Relic UI
THEN I can see the different applications and machines
AND a breakdown of the different components of the application
Background
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 former link is to the old new relic implementation, which we will leave as is until inventory-next is live and replaced inventory-classic on production. And the second one can be removed, it's not being utilized.
User Story
As an inventory administrator, I want inventory configured with New Relic so that I can can monitor and evaluate blocking requests/weak points in the system.
Acceptance Criteria
WHEN I look at New Relic UI
THEN I can see the different applications and machines
AND a breakdown of the different components of the application
Background
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.
Related to #174.
Security Considerations (required)
None, New Relic is already installed, just tweaking the configuration.
Sketch
The text was updated successfully, but these errors were encountered: