You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ScubaGear generates a set of results in several formats. The idea is to add timing information for the assessment run associated with the results to include timing information about the wall-clock execution time of the run, and possibly for each major product and component.
Motivation and context
Doing so can better inform users of where ScubaGear may be spending most of its time assessing, and provide feedback to developers to help optimize performance.
Implementation notes
Implementing timing information for the run could be implemented by:
Defining JSON fields for timing information to include in the ScubaResults output
Adding timing/profiling commands to ScubaGear execution at the orchestrator and provider levels
Acceptance criteria
How do we know when this work is done?
The ScubaResults.json includes a section for timing information that successfully tracks either start/stop times or execution duration for the overall program
ScubaResults.json includes timing information for each provider included in the assessment run
ScubaResults.json includes timing information for major phases of ScubaGear execution, including providers (aggregate), Rego test execution, and report/output creation
The text was updated successfully, but these errors were encountered:
💡 Summary
ScubaGear generates a set of results in several formats. The idea is to add timing information for the assessment run associated with the results to include timing information about the wall-clock execution time of the run, and possibly for each major product and component.
Motivation and context
Doing so can better inform users of where ScubaGear may be spending most of its time assessing, and provide feedback to developers to help optimize performance.
Implementation notes
Implementing timing information for the run could be implemented by:
Acceptance criteria
How do we know when this work is done?
The text was updated successfully, but these errors were encountered: