At my company, we don't have good tracking for escaped bugs (or awareness of in QA a lot of the time) once releases go to prod.
When the users find bugs they have a tendency to go straight to the developers and the developers don't tell the testers about it until they have a fix ready.
The problem with this is that there have been many times when it wasn't actually a bug, but a missed requirement or a requirement that was too ambiguous and wasn't coded and tested the way the user intended it to work. Both of those things need to be tracked too, but from a QA metrics perspective, they aren't being caused by something we missed in testing.
The other problem for me as a tester, is that if I missed something I want to know what it is for any number of reasons.
Have other teams had the same experience? How did you remedy it? Our users don't have access to open bugs (we use TFS) so that isn't an option.