Everybody is talking about the importance of shift-left and they’re definitely right. But – little by little, we’re seeing the opposite movement. We’re seeing the SDLC itself shifting right. Today, engineers spend most of their time developing and testing code in production-like environments. To meet those challenges, we need to adapt appropriate Observability tools throughout the SDLC.

If you dig down to the bottom of it, you’ll find that Observability will eat up any budget allocated to it and then some. That’s because the need for more Observability is rarely rooted in engineering needs. It is in fact coming from a much more primal place: the fear of the unknown. This is why Observability is a huge cost driver, growing year over year, and tremendously hard to optimize. Because anything you cut away will be quickly replaced by new data points.

In the first episode, we will discuss the fourth pillar of Observability and how Snapshots are so much better than logs. One of the big benefits of Snapshots in particular and agile Observability in general is that you can adapt your Observability in real-time without requiring code changes or redeployments.

Abstract: Coming to the office has become deprecated, hasn’t it? A hallway conversion with developer colleagues about migration to kubernetes native CI/CD, led to a feature request they are already using - multi-branch pipeline. Argo Workflow does not support it natively.

Why should SREs get all the fun? Everyone knows logging sucks and so SREs created two new pillars: metrics and traces to make their jobs easier. Well, logging sucks for developers too and they deserve - and need - better Observability. That’s where the fourth pillar of Observability comes in: Snapshots.

Including 4 parts: 1) Signs telling you to leave - Idan Lousky, Director Engineering at Rookout 2) Improve LinkedIn - Will Sutton, Managing Consultant DevOps at Energize 3) Get noticed- Youssef Lahbabi, Talent Acquisition Business Partner - Tech at Getir 4) Q&A.

Hear from leading speakers and practitioners (Google Cloud, WIX, Stealth, and Rookout) how improving developer experience can boost your team's efficiency and tackle complex software challenges.

Finout & Rookout Webinar on the topic of 'Cutting Log Costs & Debugging Pain'.

Tackling customer issues is often one of the most important responsibilities of developer teams. It can be hard, slow work, and oftentimes it is viewed as less interesting, as it seldomly leverages the same level of creativity and innovation associated with developing new features. Even more so, there are additional challenges associated with gaining insight into what took place in an environment that you are not familiar with, is hard to reproduce locally, and you are working with users who won’t necessarily be there to provide every single detail that is needed.