The latest articles on DEV Community by Bhuvaneshwari Mohan (@bhuvi_mohan). https://dev.to/bhuvi_mohan https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3791485%2F9020adda-c244-49b1-b47e-3695dc826ad4.png https://dev.to/bhuvi_mohan en Bhuvaneshwari Mohan Wed, 25 Feb 2026 10:24:08 +0000 https://dev.to/bhuvi_mohan/from-aiml-to-observability-an-unexpected-learning-experience-hdb https://dev.to/bhuvi_mohan/from-aiml-to-observability-an-unexpected-learning-experience-hdb <h2> Introduction: My AI/ML Comfort Zone </h2> <p>Basically I come from an AI/ML background. For a long time, my learning revolved around data, models, training and testing the dataset, and so on. I always assumed my path would stay somewhere related to machine learning, AI, deep learning and related areas. </p> <h2> An Unplanned Shift into Observability </h2> <p>But recently, I got an opportunity to work on an Observability related project and honestly, I didn’t have any prior knowledge on Observability. It was not something I planned for. At first, it felt uncomfortable. Observability was not a term I had worked with deeply. I heard about monitoring, metrics, logs but I really don’t know what if observability comes to picture. </p> <h2> The Initial Discomfort: Facing Real System Failures </h2> <p>Suddenly I was exposed to a world, where I have to face so many system failures, I have to resolve those failures as well as I understand problems don’t come up with some neat error messages. Before solving the failure, I had to find out what actual failure is. As I’m coming from an AI/ML background, this shift really felt big. </p> <h2> From Datasets to Distributed Systems </h2> <p>Instead of thinking about datasets, model training, I had to think about metrics, containers, logs, latency. Initially, it felt both challenging as well as interesting. </p> <h2> Understanding What Observability Really Means </h2> <p>As I spent more time on the project, I started exploring the core ideas behind observability. I learned that observability is not something like what happened, but actually understanding why it happened. </p> <h2> Key Concepts and Tools I Explored </h2> <p>So here I got the chance to explore,</p> <ol> <li>Metrics, Logs and Traces - which are the three major components of Observability.</li> <li>Golden Signals - Saturation, Latency, Traffic and Errors. </li> <li>Basic kubernetes concepts like pods, nodes and deployment.</li> <li>And also I explored monitoring tools like Prometheus and visualizing tools like Grafana. </li> </ol> <h2> Why Observability Felt So Real </h2> <p>What stood out to me was how practical and real this domain is. Unlike assumptions, observability deals with real-time live data, downtime and failures. And also I learned one thing, how observability helps the teams debug faster instead of guessing what is the actual failure. </p> <h2> Lessons Beyond Technology </h2> <p>This experience taught me that learning does not always follow a straight line, and stepping outside a comfort zone actually strengthens my core engineering skills. Observability gave me a clear picture that how real world applications behave after deployment and also building an intelligent system with AI support is not only enough, the system should be observed, maintained and monitored properly. </p> <h2> Expanding My Perspective as an AI Engineer </h2> <p>I don’t see this shift as moving away from AI/ML, but rather as expanding my perspective. Understanding observability makes me think more responsibly about how systems are built, deployed, and maintained. </p> <h2> Conclusion: Intelligence Needs Reliability </h2> <p>In the future, I believe this experience will help me become a more well-rounded engineer who understands both intelligence and reliability.</p> observability ai machinelearning beginners