Do (semi-)automatic profiling after each release

In order to have a detailed overview of a release performance, it would be good to do profiling (e.g. Sherlock style) over certain web transactions that are known to perform slowly. Triggering of such profiling can be done manually in the beginning, but later can be automated somehow.

rack-mini-profiler and peek could be good starting points on how to implement this.

One proposed solution is to trigger Sherlock profiling (screenshots below) only if a certain header (e.g. X-Profile: 1) is present in the request (with some form of authorization to restrict it a bit). I'm not sure about the runtime cost of Sherlock, so investigating is needed.

I shall start working on it once I'm finished with my onboarding.