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

Expose commit (aka private bytes) metric for a function app through MDM #726

Open
paulbatum opened this Issue Mar 20, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@paulbatum
Copy link
Member

paulbatum commented Mar 20, 2018

GB-sec usage for a consumption function app is calculated based on how long a function runs for and how much memory was consumed by the sandbox during that time. Specifically, commit / private bytes. This memory usage is limited to 1.5GB per instance.

Ideally, the commit for the process would be captured as a metric and exposed through MDM. This would allow customers to gain an understanding of their memory usage and to create alerts. The latter capability is particularly useful when you consider that the runtime will start throwing OutOfMemoryExceptions once these limits are hit. These exceptions are hard to handle gracefully and some customers would prefer to be notified through these alerts so they can take action in their code/config to reduce the memory footprint of their function app.

By making this metric available through MDM, it would be browsable from the Monitor->Metrics UX in the azure portal.

@paulbatum paulbatum added the metrics label Apr 4, 2018

@ColbyTresness

This comment has been minimized.

Copy link
Collaborator

ColbyTresness commented Dec 4, 2018

@nimakms for monitoring
@paulbatum is this still relevant?

@paulbatum

This comment has been minimized.

Copy link
Member Author

paulbatum commented Dec 4, 2018

@ColbyTresness Yes its relevant. Not sure why you put this in the active questions milestone. It describes a known platform gap.

@ColbyTresness

This comment has been minimized.

Copy link
Collaborator

ColbyTresness commented Dec 4, 2018

Will move to backlog.

@paulbatum paulbatum added the Blocked label Dec 5, 2018

@paulbatum

This comment has been minimized.

Copy link
Member Author

paulbatum commented Dec 5, 2018

Actually, I just realized that functions V2 is completely missing performance counters (I just filed Azure/azure-functions-host#3852 to track). So I have marked this as blocked. We'd need to resolve that first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment