Enable DB profiling for edxapp

robrap commented 2 months ago

AC:

[ ] Create DD support ticket to determine usefulness of taking on risk of enabling (if enabled before New Relic is disabled).
[ ] Follow-up as appropriate (implement, block, etc.)

Enable DB profiling for the edxapp DB.

This may need to be an SRE ticket. We could use the escalate label.
See https://docs.datadoghq.com/database_monitoring/setup_mysql/aurora/?tab=mysql56
Blocked: See https://github.com/edx/configuration/pull/30 for revert of the last time we tried this. This work is blocked by NR being removed from edxapp, because we think that was the problem.

robrap commented 4 weeks ago

Where did this feature go in DD, and can we see an example of it in DD to know whether it would be useful before enabling? We would just enable it if it didn't have any risk.

robrap commented 3 weeks ago

[inform] I'm marking this as blocked for a bit. I'm hoping we can resolve the NR issue, and unblock this work with less risk. Also, Jeremy is on vacation and I want to minimize risk during that time.

edx / edx-arch-experiments

Enable DB profiling for edxapp #708