Monitoring and observability around deprecating old code
When following the DEPR process, adding monitoring can be useful for the following:
Discovery on how wide-spread is the usage of the proposed DEPR
Monitoring to ensure all usage has been removed as planned
DEPR monitoring has also revealed when a new usage was added in the day that all known usages were finally removed, and helped catch and resolve issues quickly.
Start here:
Additionally, you may consider the following:
Add a “XXX DEPR” temporary dashboard in your monitoring tool (e.g. New Relic).
Use this to track the DEPR progress throughout, and delete it when you are done.
Monitoring custom metrics has typically been good enough, but there is some sampling.
If you need to be more certain, you can follow similar patterns, but use logging instead.