Daniel Odievich

As we just discussed, as soon as we find the API that returns that, we can call it!

All authentication options are documented here https://github.com/Appdynamics/AppDynamics.DEXTER/wiki/Job-File#username-string - local auth or token auth

You can always restart the job https://github.com/Appdynamics/AppDynamics.DEXTER/wiki/Restart-Job-From-Specific-Step at the https://github.com/Appdynamics/AppDynamics.DEXTER/wiki/Phases-and-Job-Steps#indexapmmetrics-80 step and not rerun previous 25.99 hours.

All CSVs should now be using https://en.wikipedia.org/wiki/ISO_8601 format (2020-09-08T02:34:55.0020000+00:00) which should be compatible with any ETL software pipelines.

Why would you have a collision on the key for Errors? TierName\java.rmi.ConnectException and TierName\java.net.ConnectException are different keys!

Oh yes, yes. Indeed. The thing is you have to look them up by the name from the Metric name. It's fastest to add them to the dictionary with loop...

Exactly, but it's not the end of the world. It's a bit lossy yes, but you just grab the first Error that matches that name and at least fill one....

You need to adjust https://github.com/Appdynamics/AppDynamics.DEXTER/wiki/Job-File Specify what you need in https://github.com/Appdynamics/AppDynamics.DEXTER/wiki/Job-File#input-section Turn off report creation in https://github.com/Appdynamics/AppDynamics.DEXTER/wiki/Job-File#output-section by setting all reports to False. This will create all the indexed CSVs...

Well, did you specify https://github.com/Appdynamics/AppDynamics.DEXTER/wiki/Job-File#entitydetails-boolean in your job file to generate those reports?

https://github.com/Appdynamics/AppDynamics.DEXTER/wiki/Command-Line-Parameters, you need to specify the `--job-file` parameter to pass your job file