Observability has exploded onto the software engineering zeitgeist over the last five years, and for a good reason. However, it suffers from being misunderstood and sometimes equated with a closely related subject—monitoring. This confusion is compounded by the fact that some of the existing tools and frameworks just adopted a lot of the observability terminology in just the letter of the word, not the intent. Not having a solid grasp on the basics of observability is becoming unacceptable in the world of effective software quality engineering. Kaushal Dalvi shares his experiences in the...
Kaushal Dalvi
UKG
Since he got his first computer at age thirteen, Kaushal Dalvi has been interested in systems and software performance. He spent days researching performance characteristics of different motherboards, CPUs, GPUs, RAM, and disks to configure and overclock them in order to squeeze the maximum frames per second out of the games he played. Kaushal built and maintained websites for local businesses, where he started learning about performance and reliability. He developed a taste for it, and now ten years later he continues working in the same field as the director of quality and performance engineering at Ultimate Software, leading teams that deal with workload modeling, test scripting and execution, bottleneck analysis, debugging, and much more.