home.social

#slos — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #slos, aggregated by home.social.

  1. Want your LLMs to stay reliable, not drift into hallucinations? Applying classic SRE discipline—SLOs, error budgets, and the golden signals—gives you observability and a human‑in‑the‑loop safety net. Learn how to turn metrics into trust for generative AI. #SRE #SLOs #ErrorBudgets #GoldenSignals

    🔗 aidailypost.com/news/apply-sre

  2. Want your LLMs to stay reliable, not drift into hallucinations? Applying classic SRE discipline—SLOs, error budgets, and the golden signals—gives you observability and a human‑in‑the‑loop safety net. Learn how to turn metrics into trust for generative AI. #SRE #SLOs #ErrorBudgets #GoldenSignals

    🔗 aidailypost.com/news/apply-sre

  3. as you know, i was trained by Stan. i see your point, & i've lived the history of the evolution of this revolution in uncovering the self. #TruthWarriors nice to have this interaction with you, YanaarLee #ExperienceIsDivinity #SLOS #D7V1 Experience Is Divinity #FallsFromGrace #PrimalRenaissance

    RE: https://bsky.app/profile/did:plc:ikeucrcrjj2onqkbleink3n7/post/3lyeoktquy22w

  4. 🛏️ Don’t get out of bed for anything less than an SLO!

    Learn how to set meaningful Service Level Objectives that actually matter. At #FOSSASIASummit2025, Joe Blubaugh shares how great #SLOs help teams prioritize, stay focused, and sleep better at night.

    🎥 Watch now: youtu.be/yNO4OmJFqdI

  5. @thisismissem "#DevOps" is definitely worthless as a term. I've got a presentation kicking around somewhere where the thesis is "If you want to create a DevOps team you've already failed".

    In a well functioning team there should be no "us vs. them" between the SWE and #SRE people. Both groups are engineers, it's just that the engineering focus is different.

    The goal is still the same. Build and deliver services that meet the users' needs, within the #SLOs.

  6. If you are into Observability and Reliability you should check out the "9 Things You Should Do When Starting to Use SLOs" talk I gave at DevOps Days NYC. If you agree, and especially if you disagree, please leave a comment and lets chat! #SRE #observability #reliability #SLOs #devops

    youtu.be/_thEyZxltm4

  7. So happy to have had the opportunity to speak at @devopsdaysnyc yesterday! I gave out 9 tips for folks starting to use SLOs and how to get more value out of the SLOs they already have. #sre #reliability #slos

  8. Over my morning coffee, I enjoyed @Ilovelemons #SLOconf talk examining SLO practice through the lens of the book "Seeing Like A State".

    youtube.com/watch?v=NiupBm3bXd

    I keep seeing that book come up so it's probably time for me to read it... I think there's a lot we can untangle in the greater #SRE discipline using social and political thinking.

    Dan's language around using #SLOs as an interface between the company and the team feels really powerful!

  9. @jgoerzen @rthoelen I'd look past the tools and Clouds and into what the mindset of #SRE is. The Google SRE Book is a pretty good start.

    If you want to begin with just one thing, implement a #postmortem process. That way you'll learn what to do next one incident at a time. If you want a second thing I'd say embrace the concept of #errorbudgets and talk to your customers about #SLOs which help you prioritize work. Only tools needed are a text editor and a monitoring system. HTH

  10. @jgoerzen @rthoelen I'd look past the tools and Clouds and into what the mindset of #SRE is. The Google SRE Book is a pretty good start.

    If you want to begin with just one thing, implement a #postmortem process. That way you'll learn what to do next one incident at a time. If you want a second thing I'd say embrace the concept of #errorbudgets and talk to your customers about #SLOs which help you prioritize work. Only tools needed are a text editor and a monitoring system. HTH

  11. @jgoerzen @rthoelen I'd look past the tools and Clouds and into what the mindset of #SRE is. The Google SRE Book is a pretty good start.

    If you want to begin with just one thing, implement a #postmortem process. That way you'll learn what to do next one incident at a time. If you want a second thing I'd say embrace the concept of #errorbudgets and talk to your customers about #SLOs which help you prioritize work. Only tools needed are a text editor and a monitoring system. HTH