Reliability isn't reactive. Our crews trim trees near lines before they're a problem, because the goal isn't to restore power. It's to keep it on.
Trees near your lines? Call us: sjenergy.ca/safety#veget...
@sjenergy.ca
@sjenergy.caReliability isn't reactive. Our crews trim trees near lines before they're a problem, because the goal isn't to restore power. It's to keep it on.
Trees near your lines? Call us: sjenergy.ca/safety#veget...
@mh2333.bsky.social/health returns 200 because the process is alive, so the load balancer keeps routing traffic to an instance that cannot reach its database. Liveness and readiness are not the same check.
@freegardener.bsky.socialWhere does AI agent reliability really come from? New research separates prompt context, compliance & enforcement to show where trust is earned. #AI #LLM #AIAgents #Reliability
https://freegardner.com/synapse/where-ai-agent-task-state-reliability-comes-from.html
@jmm86.bsky.socialTo ensure reliable CI/CD, keeping artifact immutability is key. If QA passes the same image, it hits production reliably. For example, our image pipeline locks down previous builds. #CI/CD #reliability
@mzloteanu.bsky.social#statstab #621 A General Method For Estimating Reliability Using Bayesian Measurement Uncertainty
Thoughts: "estimating reliability [...] for complex cognitive and behavioural assessments without test-retest data" wow!
@dcac.comhttps://buff.ly/47ZkJuz Make the Cloud Work for Your Business
How #reliability, #faster and #easier product development, and cost #savings make a difference.
By @mrdenny.com via @inc.com
#cloud #Azure #AWS
@joseph11lim.mastodon.social.ap.brid.gy#SouthKorea wants free ‘ #AI for All’. Is #society ready for it?
“te #government plans to estab an #autonomous #reliability-assurance sys”,[👉🤔naive?] ICT ministry said, adding tis wld be based on te 7 “AI #Ethics Principles” it laid out last mth: #accountability, human-centredness, #privacy […]
@infoq.comWhat happens when AI takes over incident response?
Senior engineers build expertise through production “scar tissue.” If AI resolves every incident, that feedback loop breaks - and skills can atrophy.
🔗 Watch now: buff.ly/zQiI4hU
@getpacketai.bsky.socialShipping every log line to your aggregator is expensive and makes troubleshooting harder. One team cut costs 70% and 4x'd search speed by treating logs, metrics, and…
https://dev.to/samson_tanimawo/why-we-stopped-using-log-aggregation-for-everything-2f8b
@getpacketai.bsky.socialDNS drift is hard to debug in production. This breaks down how to detect unplanned zone changes and build reconciliation loops that actually catch who changed what.
https://dev.to/briarvoss47291/dns-zone-drift-reconcile-records-and-trace-unplanned-changes-3pbf
@getpacketai.bsky.socialStop letting AI improvise your incident response. Use versioned, hashed runbooks with a strict four-field contract—boring is what you need when the graph goes red.
https://dev.to/appcpp_9071/i-will-not-unfreeze-prod-until-the-runbook-hash-matches-the-page-4p89
@getpacketai.bsky.socialYour runbook isn't actually a runbook if it only works when one person remembers the rule. A practitioner shares what breaks when you scale incident response…
https://www.reddit.com/r/devops/comments/1wiraia/your_runbook_is_still_state_in_someones_head_you/
@getpacketai.bsky.socialAutomating Kubernetes API migrations shouldn't destroy your Git history or strip inline documentation. Here's how to migrate 300+ manifests while keeping…
https://www.reddit.com/r/devops/comments/1whx3fm/preserving_yaml_comments_and_git_blame_during/
@getpacketai.bsky.socialGoogle Cloud published its incident response playbook for outages. For SRE teams, the real value isn't the process—it's having a vendor page to point at when asking…
https://dev.to/leobaniak/google-cloud-publishes-a-six-phase-playbook-for-its-own-outages-1e2a
@getpacketai.bsky.socialHow to catch production problems before your users do: a practical walkthrough of observability-driven incident investigation using metrics, logs, and…
@hormozisky.bsky.socialThe deal-making matters more than the deal. Once you agree on terms, follow through completely. Consistency is what builds trust under pressure.
@getpacketai.bsky.socialAutomation isn't trustworthy until it shows what it actually changed. Learn why one team's manual double-checks persisted for years, and how true…
@getpacketai.bsky.socialClock skew across just 11 seconds created an impossible incident timeline and masked a real error spike. A cautionary tale on why time synchronization…
@getpacketai.bsky.socialRead-only mode seemed straightforward until every request path—from session tokens to health checks—tried to write. A hard-won lesson in testing platform…
https://dev.to/sergey_shinder_ab2d943365/we-announced-read-only-mode-and-could-not-even-sign-in-3pgp
@mh2333.bsky.socialA single hung dependency drained our worker pool in minutes because we never set one. Every service call needs a connect timeout, a request timeout, and a total deadline.