Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEA] Provide tracing and performance statistics gathering capability in App SDK #388

Open
MMelQin opened this issue Nov 3, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request
Projects

Comments

@MMelQin
Copy link
Collaborator

MMelQin commented Nov 3, 2022

Is your feature request related to a problem? Please describe.
With the use of logging library, application execution logs can be gathered at various logging level per configuration. However, with the maturing of the App SDK, especially when venturing into clinical deployment (IRB'ed), there are stronger needs to provide additional insights into the application execution, e.g. activity audits, performance metrics both in terms of latency and ideally result accuracy.

This is important when AI applications are deployed and used in imaging workflow, as the IT/PACS admins always need to have insights into the latency, resource, and clinical performance of the applications, so as to better manage the critical workflow stage for operational, clinical, as well as regulatory requirements.

Describe the solution you'd like
A logging framework that will support pre-defined as well as custom categories of metrics collection, while making the aggregation and delivery of the metrics dynamic and configurable, e.g. records gather could be delivered to the stats gathering agent on the host system that runs the MAP.

Describe alternatives you've considered
Native logging library with logging level combined with defined string literal indicating the categories of information, e.g. default being execution log, "PERF" for elapsed time for blocks of execution, etc.

Additional context

@MMelQin MMelQin added the enhancement New feature or request label Nov 3, 2022
@MMelQin MMelQin added this to Needs Triage in Backlog via automation Nov 3, 2022
@dbericat
Copy link
Member

dbericat commented Nov 9, 2022

Right now is defined by the application developer.

Ideally, existing built in operators include performance type logs and support SOLE: what gets executed and what performance.

Define statistics we want to gather.

@MMelQin MMelQin moved this from Needs Triage to High priority in Backlog Nov 9, 2022
@MMelQin MMelQin self-assigned this Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Backlog
High priority
Development

No branches or pull requests

2 participants