Occasionally I look at the code metrics in visual studio for my solution. I don't ever see anything I would find alarming. My maintainability is usually pretty high with exception to some obvious classes (entity config classes, DAL classes that call SQL, etc). The only time I really ever find the cyclomatic complexity and class coupling values high is again, on classes that I expect to see high values on.
If I were to look at code metrics after there is already a problem then I don't understand why I need to look, just fix whatever the problem is. Looking before there is a problem usually doesn't point anything out as the only low maintainability indexes are the examples mentioned above.
The only time I actually come into the code metrics for a reason is when I'm curious about how many lines of code the project is, and that's just because of curiosity and not a need to do so.
When is it useful to actually look at the code metrics of an ASP.NET MVC5 project/solution?