Could we hack this to better understand what your code is doing in prod? Let me describe a scenario: Let's say you just inherited some service that is already

Could we hack this to better understand what your code is doing in prod? Let me describe a scenario: Let's say you just inherited some service that is already running in production but it don't have a great documentation nor a good test suite. To make matters worse you don't really know how this service is being used and what are the critical paths inside it. What I'm thinking is if it would be possible to use this feature to collect some real world usage data for this application. And this data could give you a better understanding about what is actually important in the service. For APIs we already have a part of this data, as most server in Go have the number of requests for each endpoint. But I think in many cases a more granular data could be really helpful. Yes, I know that the number of times some function was called isn't a reliable indicator of the importance of said function. But it should be better than nothing. And I also know that something like this would have a negative performance effect that would not be acceptable for some situations.