My customer is asking for...My first question to the customer would be "why?", as in, what is the business intent behind this question? For example, you could run a database in trace mode 24 hours a day and have the exact metrics for every single execution of every query, but in reality, what is the benefit of that (besides having hundreds of gigabytes of trace data :-))
If they are looking for some *testing* or *indicative* data, then yes, running the application in trace mode for (say) an hour or two is a valid approach to get some good data, but wanting that *permanently* doesn't really serve any purpose.
If, on the other hand, they want to know about *outliers*, ie, when things go wrong, then active session history (ASH) is probably your best bet here, in conjunction with the AWR report facilities we provided.
John Beresniewicz did an excellent presentation on all the ways you can exploit ASH here
https://www.oracle.com/technetwork/database/manageability/con9577-ash-deep-dive-oow2013-2031468.pdf