-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Open
Labels
Description
Summary
| Status | Count |
|---|---|
| π Total | 489 |
| β Successful | 426 |
| β³ Timeouts | 4 |
| π Redirected | 0 |
| π» Excluded | 0 |
| β Unknown | 0 |
| π« Errors | 59 |
Errors per input
Errors in README.md
- https://twitter.com/SREWorkbook: Failed: Network error (status code: 403)
- https://doordash.engineering/2022/04/25/using-fault-injection-testing-to-improve-doordash-reliability/: Failed: Network error (status code: 403)
- https://www.socallinuxexpo.org/sites/default/files/presentations/Scale%20x14%20Slides.pdf: Failed: Network error (status code: 404)
- https://dastergon.gr/wheel-of-misfortune/: Failed: Network error (status code: 404)
- https://twitter.com/SREWeekly: Failed: Network error (status code: 403)
- https://www.sidewalksafari.com/2018/12/sre-in-a-travel-emergency.html: Failed: Network error (status code: 404)
- https://twitter.com/googlesre: Failed: Network error (status code: 403)
- https://www.honeycomb.io/usecase/o11ycast/: Failed: Network error (status code: 404)
- https://devops.com/three-ways-to-minimize-the-impact-of-high-severity-incidents/: Failed: Network error (status code: 403)
- https://codeascraft.com/2016/11/17/debriefing-facilitation-guide/: Failed: Network error (status code: 403)
- https://www.verica.io/top-seven-myths-of-robust-systems/: Failed: Network error (status code: ERR)
- https://twitter.com/SREcon: Failed: Network error (status code: 403)
- https://blogs.vmware.com/services-education-insights/2018/02/site-reliability-engineering.html: Failed: Network error (status code: 404)
- https://devops.com/sres-the-happiest-and-highest-paid-in-the-industry/: Failed: Network error (status code: 403)
- https://dastergon.gr/error-budget-calculator/: Failed: Network error (status code: 404)
- https://twitter.com/usenix: Failed: Network error (status code: 403)
- https://dastergon.gr/awesome-sre: Failed: Network error (status code: 404)
- https://twitter.com/SREBook: Failed: Network error (status code: 403)
- https://danrl.com/blog/srm: Failed: Network error (status code: ERR)
- https://cloud.google.com/blog/big-data/2016/10/a-google-sre-explores-github-reliability-with-bigquery: Failed: Network error (status code: 404)
- https://blog.netsil.com/beyond-google-sre-what-is-site-reliability-engineering-like-at-medium-71c65bd35f4e: Failed: Network error (status code: ERR)
- https://codeascraft.com/2012/05/22/blameless-postmortems/: Failed: Network error (status code: 403)
- https://www.reddit.com/r/IAmA/comments/1w1y5m/we_are_the_google_site_reliability_engineering/: Failed: Network error (status code: 403)
- https://www.loomsystems.com/blog/2017/02/06/spiraling-ops-debt-the-sre-coding-imperative: Failed: Network error (status code: ERR)
- https://chaosengineering.news/: Timeout (status code: TIMEOUT)
- http://www.wired.com/insights/2011/12/service-level-agreements-in-the-cloud-who-cares/: Failed: Network error (status code: 404)
- https://www.packtpub.com/web-development/real-world-sre: Failed: Network error (status code: 404)
- https://honeycomb.io/blog/2018/02/oncall-and-sustainable-software-development/: Failed: Network error (status code: 404)
- https://honeycomb.io/blog/2017/01/instrumentation-worst-case-performance-matters/: Failed: Network error (status code: 404)
- http://the-cloud-book.com/: Failed: Network error (status code: 521)
- http://everythingsysadmin.com/: Failed: Network error (status code: 521)
- https://blog.twitter.com/2014/push-our-limits-reliability-testing-at-twitter: Failed: Network error (status code: 403)
- https://github.com/fhivemind/sre-playground: Failed: Network error (status code: 404)
- https://dzone.com/articles/the-cloudcast-301-sre-and-infrastructure-operation: Failed: Network error (status code: 410)
- https://blog.netsil.com/the-4-golden-signals-of-api-health-and-performance-in-cloud-native-applications-a6e87526e74: Failed: Network error (status code: ERR)
- https://rachelbythebay.com/w/: Timeout (status code: TIMEOUT)
- https://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
- https://www.verica.io/blog/inhumanity-of-root-cause-analysis/: Failed: Network error (status code: ERR)
- https://www.reddit.com/r/IAmA/comments/177267/we_are_the_google_site_reliability_team_we_make: Failed: Network error (status code: 403)
- https://podcasts.apple.com/us/podcast/resilience-in-action/id1506828506: Failed: Network error (status code: 404)
- https://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
- https://www.youtube.com/watch?v=bC5dIPzNH24: Failed: Network error (status code: 404)
- https://devops.com/site-reliability-engineering-sre-true-ops-devops/: Failed: Network error (status code: 403)
- https://www.weave.works/blog/gitops-part-3-observability: Timeout (status code: TIMEOUT)
- http://www.networkworld.com/article/3182827/cloud-computing/srecon17-brave-new-world-of-site-reliability-engineering.html: Failed: Network error (status code: 404)
- http://googleresearch.blogspot.gr/2012/07/site-reliability-engineers-solving-most.html: Failed: Network error (status code: ERR)
- https://devops.com/sre-devops-cloud-native-server-cage-match/: Failed: Network error (status code: 403)
- https://devops.com/code-yellow-when-operations-isnt-perfect/: Failed: Network error (status code: 403)
- https://www.inc.com/justin-bariso/meet-postmortem-googles-brilliant-process-tool-for-learning-from-failure.html: Failed: Network error (status code: 403)
- https://blog.twitter.com/2015/how-we-break-things-at-twitter-failure-testing: Failed: Network error (status code: 403)
- https://twitter.com/The_SRE_Dev: Failed: Network error (status code: 403)
- https://honeycomb.io/blog/2017/01/instrumentation-what-does-uptime-mean/: Failed: Network error (status code: 404)
- https://www.verizondigitalmedia.com/e-book/oreilly-what-is-sre/: Timeout (status code: TIMEOUT)
- https://community.atlassian.com/t5/Jira-Ops-questions/I-m-John-Allspaw-Ask-Me-Anything-about-incident-analysis-and/qaq-p/957084: Failed: Network error (status code: ERR)
- https://www.verica.io/inhumanity-of-root-cause-analysis/: Failed: Network error (status code: ERR)
- https://blog.box.com/blog/a-tale-of-postmortems/: Failed: Network error (status code: 403)
- https://www.rootly.io/blog: Failed: Network error (status code: 403)
- http://engineering.medallia.com/blog/posts/understanding-site-reliability-engineering-through-movies-and-books/: Failed: Network error (status code: ERR)
- https://blog.twitter.com/2017/the-infrastructure-behind-twitter-scale: Failed: Network error (status code: 403)
- https://blog.twitter.com/2016/the-infrastructure-behind-twitter-efficiency-and-optimization: Failed: Network error (status code: 403)
- https://twitter.com/TwitterSRE: Failed: Network error (status code: 403)
- https://www.transposit.com/blog/2020.01.30-writing-runbook-documentation-when-youre-an-sre/: Failed: Network error (status code: 404)
- https://www.loomsystems.com/single-post/2016/03/23/So-you-want-to-be-a-Site-Reliability-Engineer: Failed: Network error (status code: ERR)
Reactions are currently unavailable