-
Notifications
You must be signed in to change notification settings - Fork 55
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
Feature Request - Application Insights #102
Comments
Thanks @gcormier . The deployer already adds an Application Insights instance to the resource group, so the work here is to plumb it through for the Azure Batch tasks in the BatchScheduler class. This would also enable the CPU/memory/etc. to be viewed in the Azure Batch Explorer. We'd certainly appreciate the help if you and/or the team (or anyone else) can add this. Otherwise, this is definitely something we want to get done this year. |
UPDATE - The Genomics team is working on a way to capture and report max cpu, disk, and memory utilization, then upload the info into cosmosdb. |
As of 2.2, you can get detailed metrics on disk utilization from cosmosdb. We'll use this item to track progress on feeding the rest of this information to application insights to make accessible after the run. |
TODO enable Batch and Application Insights integration. Since we don't use autopools anymore, Pools are longer-lived, and this feature makes more sense to implement. |
@MattMcL4475 this looks like a long pending issue open since 2020, can this be closed and reopened later when we decide to work on it or would you say this is something we intend to do in 2024? |
I would love to see this in 2024, but I wonder how oversubscribed we might be. However, I fear that if we close this, it's more likely that we'd forget about it rather than remember to reopen/recreate it later. |
So our scientists can monitor and tune instance sizing accordingly (some workloads don't multithread well, might as well lower the instance sizes)
I believe we need to modify start tasks accordingly. Also the setup script could create application insights in the resource group.
The text was updated successfully, but these errors were encountered: