In my experience (nearly 20yr in tech now) may Devs AND Ops struggle with implementing observability. The sheer amount of "things" that can be monitored and lo

In my experience (nearly 20yr in tech now) may Devs AND Ops struggle with implementing observability. The sheer amount of "things" that can be monitored and logged on modern SaaS applications can be overwhelming and people seem to default to the "switch everything on and then decide" mentality. As you can probably guess... this leads to even more confusion... and has a negative impact on their original goal. My recommendation would be to learn how to create useful observability that benefits both Devs and Ops. The greater the overlap in a Venn diagram, the greater the success at resolving issues together - and NOT pointing the finger at the other party. Over the years I have done a few gigs which focused on observability and they have been the most lucrative too. It turns out companies are more than willing to pay top dollar if it means their teams work _together_ much better.