[turtlebits]

Implementing traces should be done by devs, not the infrastructure team. Devops should implement/support the platform that supports traces.

[jiggawatts]

In Azure, use Application Insights for this. It's easy to set up and shows distributed performance traces across multiple services in a GUI.

[latency-guy2]

Disagree, DevOps teams should be looking for resources that are being hit hard unnecessarily and request moves to better solutions when possible.

DevOps teams should be looking at CPU spikes, and should be performing RCAs, and they should be maintaining resources in a healthy state, and they should reject/revert changes and notify problem areas in code by product focused devs.

Product devs, for the most part, are only implementing human lex traces to debug business logic when it arises. Product devs are not equipped with the knowledge to identify system errors that are not "bugs in the code", i.e. they will not be good at telling you why SPROC_LXC1 fails as a result of making a ExcelParserFactoryFactory