Stitcher for Podcasts

Get the App Open App
Bummer! You're not a
Stitcher Premium subscriber yet.
Learn More
Start Free Trial
$4.99/Month after free trial

Show Info

Episode Info

Episode Info: We’re using telemetry to fill in the gaps and anticipate problems while discussing The DevOps Handbook, while Michael is still weird about LinkedIn, Joe knows who’s your favorite JZ, and Allen might have gone on vacation. You can find these show notes at, in case you’re reading these within your podcast player. Sponsors Datadog – Sign up today for a free 14 day trial and get a free Datadog t-shirt after your first dashboard.Secure Code Warrior – Start gamifying your organization’s security posture today, score 5,000 points, and get a free Secure Code Warrior t-shirt.Survey Says Anonymous VoteSign in with WordpressWhat's your favorite mobile device?An iPad. The Tab-father of tablets.An Android-based tablet. Great hw specs, without the hassle of longterm support.A Kindle. It was on sale.Chromebook FTW. Not quite as portable as a tablet, nor as useful as a laptop ...2-in-1 Laptop. A giant, bulky tablet that can run Joe’s Super Secret Survey Anonymous VoteSign in with WordpressGo or Rust?GoRustvote News Thank you to everyone that left us a new review:iTunes: AbhiZambre, Traz3rStitcher: AndyIsTakenMost important things to do for new developer job seekers?I Got 99 Problems and DevOps ain’t One Find and Fill Any Gaps Once we have telemetry in place, we can identify any gaps in our metrics, especially in the following levels of our application: Business level – These are metrics on business items, such as sales transactions, signups, etc.Application level – This includes metrics such as timing metrics, errors, etc.Infrastructure level – Metrics at this level cover things like databases, OS’s, networking, storage, CPU, etc.Client software level – These metrics include data like errors, crashes, timings, etc.Deployment pipeline level – This level includes metrics for data points like test suite status, deployment lead times, frequencies, etc.Application and Business Metrics Gather telemetry not just for technical bits, but also organizational goals, i.e. things like new users, login events, session lengths, active users, abandoned carts, etc.Have every business metric be actionable. And if they’re not actionable, they’re “vanity metrics”.By radiating these metrics, you enable fast feedback with feature teams to identify what’s working and what isn’t within their business unit.Infrastructure Metrics Need enough telemetry to identify what part of the infrastructure is having problems.Graphing telemetry across infrastructure and application allows you to detect when things are going wrong.Using business metrics along with infrastructure metrics allows development and operations teams to work quickly to resolve problems.Need the same telemetry in pre-production environments so you can catch problems before they make it to production.Overlaying other Relevant Information onto Our Metrics In ...
Read more »

Discover more stories like this.

Like Stitcher On Facebook


Show Info

Episode Options

Listen Whenever

Similar Episodes

Related Episodes