thoughts on how to measure/trend a method that runs for hours?
We have a large ETL system that we are trying to hook dynaTrace up to. We have a use case to provide timings on how long it takes to process a entire file, which can actually take several hours to complete. In this use case we don't really care about purepaths – just the ability to track a measure tied to the file processing entry point. Dropping down a level, which would normally be our best-practice recommendation, doesn't work so well since that is the time to process a record, and there will be millions of those, which ultimately doesn't seem to lend itself to do anything useful for us.
Are there any thoughts/best practices on how to get that type of timing data?
I suggest creating your own JMX Measure - meaning - that your application delivers the response time. You can then capture that JMX value with dynaTrace
my 2 cents 
Ok, I got it. Thanks. Didn't think this was a native option.
Community Member of the Month
September 2018
Announcing Dynatrace's Community Member of the Month for September 2018, Muthu P.! Click here to read more! Employee Member of the Month
September 2018
Announcing Dynatrace's Employee Member of the Month for September 2018, Kris Z.! Click here to read more! 