Performance Timings Clarity

newtewt commented 4 years ago

We have this ticket that describes what to do for performance timing. Add more details to this to help clarify it for others.

Which data set
- Define instance to use, data set, and config.
Reports have a static reported_date once they are saved in csvs. As we move forward tasks generated by the config may never occur.
- This might take some custom scripting in medic-conf or csv altering. Not necessarily solved in this issue but determine if we should open a ticket in medic-conf to support this or maybe another backlog item for a custom csv script.
Someday automate this
- Timings by humans will always be susceptible to flaws. Find a way to automate this or move in that direction. We have telemetry maybe add tickets or do it yourself to get the steps recorded.

newtewt commented 3 years ago

Ticket in cht-core to track adding extra telemtery to make this somewhat easier to scoop the data out.

newtewt commented 3 years ago

csvs for reports are updated to use a relative time stamp now. They get reported within a few days now.

medic / cht-core