We usually think about observability as a feature intended for application developers. Client library authors provide observability as an afterthought to improve developer experience and reduce support burden. But native instrumentation intended for end users is extremely valuable for library authors as well during development process.

In this session I will show how we leverage native instrumentation when stress and load testing Azure client libraries and how it helps us optimize performance, detect and fix reliability issues.
I'll provide a few examples of such issues we were able to detect: the unnecessary HTTP requests we could avoid, transient issues we didn't retry, memory we over-allocated, thread pools we didn't configure.

Client library authors don't usually have expertise in observability. I'll show how stress testing helps us bridge this gap and find good observability signals for the end users and ourselves.