-
Notifications
You must be signed in to change notification settings - Fork 20
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
Remove optional import of newrelic #396
Comments
Thanks for the history. If a deployment had removed this dependency, even for an outdated reason, this would cause a backward-incompatibility. I don’t think we should change anything around this until this code is no longer run by default in the first place. |
I think someone would have to go to some lengths to avoid having it installed, as it's currently pulled in automatically. I don't think it would be a big deal to do a major-version bump and remove the conditionals. But it's certainly not urgent; the main reason I filed this ticket was just to have a place to link to in a comment. :-) |
@timmc-edx will look at this to determine whether to backlog or close. |
I'm going to go ahead and close this for now. With the work in #397 we might be moving towards a situation where we can contain all of the New Relic references to a single plugin, and at that point it might be relatively straightforward to move newrelic from base to testing dependencies. But it's too early to say at this point. |
edx-django-utils.monitoring
currently does a try-import of thenewrelic
package and then sets a flag if the import fails. This is a historical artifact that is no longer needed; we can justimport newrelic.agent
directly and drop anyif newrelic:
checks.Archaeological notes:
newrelic
package, and has from the very beginning.The text was updated successfully, but these errors were encountered: