dastergon / awesome-sre Goto Github PK
View Code? Open in Web Editor NEWA curated list of Site Reliability and Production Engineering resources.
Home Page: https://sre.xyz
License: Creative Commons Zero v1.0 Universal
awesome-sre's Issues
Link Checker Report
Errors were reported while checking the availability of links.
Issues found in 1 input. Find details below.
[README.md]:
✗ [ERR] https://www.apress.com/us/book/9781484205129 | Network error: error following redirect for url (https://idp.springer.com/transit?redirect_uri=https%3A%2F%2Flink.springer.com%2Fbook%2F10.1007%2F978-1-4842-0511-2&code=c1d07662-9acd-4c35-b286-431751aa6e5b): too many redirects
✗ [404] https://blog.box.com/blog/a-tale-of-postmortems/ | Network error: Not Found
✗ [404] https://www.youtube.com/watch?v=bwt6TZjefGM | Network error: Not Found
⧖ [TIMEOUT] https://rachelbythebay.com/w/ | Timeout
✗ [ERR] https://blog.squadcast.com/how-to-avoid-on-call-burnout/ | Network error: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921: (Hostname mismatch)
✗ [404] https://blog.newrelic.com/2018/07/05/site-reliability-engineering-sre/ | Network error: Not Found
✗ [ERR] https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/ | Network error: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921: (Hostname mismatch)
✗ [404] https://www.youtube.com/watch?v=JLkr6UHXN44&nohtml5=False | Network error: Not Found
✗ [ERR] https://www.vividcortex.com/blog/monitoring-isnt-observability | Network error: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921: (Hostname mismatch)
✗ [ERR] http://blogs.atlassian.com/2016/02/inside-atlassian-sre-use-chatops-run-incident-management/ | Network error: error following redirect for url (http://www.atlassian.com/incident-management/devops/chatops): too many redirects
✗ [404] https://www.cruform.com/sre-capability-map/ | Network error: Not Found
✗ [404] https://twitter.com/The_SRE_Dev | Network error: Not Found
✗ [ERR] https://www.vividcortex.com/blog/why-percentiles-dont-work-the-way-you-think | Network error: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921: (Hostname mismatch)
✗ [404] https://twitter.com/i/moments/924656333495898112 | Network error: Not Found
✗ [404] http://pages.catchpoint.com/DEVOPS-SRE-AMA-mkty.html | Network error: Not Found
🔍 485 Total ✅ 470 OK 🚫 14 Errors (HTTP:14|Timeouts:1)
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 476 |
| ⏳ Timeouts | 2 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 11 |
Errors per input
Errors in README.md
- https://www.inc.com/justin-bariso/meet-postmortem-googles-brilliant-process-tool-for-learning-from-failure.html: Failed: Network error (status code: 403)
- 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.box.com/blog/a-tale-of-postmortems/: Failed: Network error (status code: 404)
- http://the-cloud-book.com/: Failed: Network error (status code: 522)
- https://twitter.com/The_SRE_Dev: Failed: Network error (status code: 404)
- 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://www.loomsystems.com/single-post/2016/03/23/So-you-want-to-be-a-Site-Reliability-Engineer: Failed: Network error (status code: 404)
- https://rachelbythebay.com/w/: Timeout (status code: TIMEOUT)
- https://blog.netsil.com/beyond-google-sre-what-is-site-reliability-engineering-like-at-medium-71c65bd35f4e: Failed: Network error (status code: ERR)
- 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/: Timeout (status code: TIMEOUT)
- https://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
- https://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
Link Checker Report
Errors were reported while checking the availability of links.
📝 Summary
---------------------
🔍 Total..........453
✅ Successful.....451
⏳ Timeouts.........2
🔀 Redirected.......0
👻 Excluded.........0
🚫 Errors...........0
Errors in README.md
⧖ http://www.brendangregg.com/blog/index.html
⧖ http://www.se-radio.net/2016/12/se-radio-episode-276-bjorn-rabenstein-on-site-reliability-engineering/
Link Checker Report
Errors were reported while checking the availability of links.
Issues found in 1 input(s). Find details below.
[README.md]:
✗ https://blog.squadcast.com/how-to-avoid-on-call-burnout/: Network error while trying to connect to an endpoint via reqwest
✗ https://www.youtube.com/watch?v=bwt6TZjefGM: Network error while trying to connect to an endpoint via reqwest
⧖ http://www.se-radio.net/2016/12/se-radio-episode-276-bjorn-rabenstein-on-site-reliability-engineering/
✗ https://twitter.com/SREcon: Network error while trying to connect to an endpoint via reqwest
⧖ http://www.brendangregg.com/blog/index.html
✗ https://twitter.com/The_SRE_Dev: Network error while trying to connect to an endpoint via reqwest
✗ https://blog.newrelic.com/2018/07/05/site-reliability-engineering-sre/: Network error while trying to connect to an endpoint via reqwest
✗ https://www.youtube.com/watch?v=JLkr6UHXN44&nohtml5=False: Network error while trying to connect to an endpoint via reqwest
✗ https://twitter.com/TwitterSRE: Network error while trying to connect to an endpoint via reqwest
✗ https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/: Network error while trying to connect to an endpoint via reqwest
✗ https://twitter.com/i/moments/924656333495898112: Network error while trying to connect to an endpoint via reqwest
🔍 471 Total ✅ 460 OK 🚫 9 Errors (HTTP:9|Timeouts:2)
Wrong profile link in index.html
Currently in index.html on the gh-pages branch the GitHub link points to https://github.com/dastegon.
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 478 |
| ⏳ Timeouts | 1 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 10 |
Errors per input
Errors in README.md
- https://cloud.google.com/blog/big-data/2016/10/a-google-sre-explores-github-reliability-with-bigquery: Failed: Network error (status code: 404)
- https://www.rootly.io/blog: Failed: Network error (status code: 403)
- https://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
- https://twitter.com/The_SRE_Dev: Failed: Network error (status code: 404)
- https://blog.box.com/blog/a-tale-of-postmortems/: Failed: Network error (status code: 404)
- https://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
- https://blog.netsil.com/beyond-google-sre-what-is-site-reliability-engineering-like-at-medium-71c65bd35f4e: Failed: Network error (status code: ERR)
- http://engineering.medallia.com/blog/posts/understanding-site-reliability-engineering-through-movies-and-books/: Timeout (status code: TIMEOUT)
- https://blog.netsil.com/the-4-golden-signals-of-api-health-and-performance-in-cloud-native-applications-a6e87526e74: Failed: Network error (status code: ERR)
- http://the-cloud-book.com/: Failed: Network error (status code: 522)
- https://www.inc.com/justin-bariso/meet-postmortem-googles-brilliant-process-tool-for-learning-from-failure.html: Failed: Network error (status code: 403)
Catchpoint migration
Hi !
It’s Gleb from Catchpoint.com.
I've noticed that your website links to our old blog, which we’re currently migrating from a subdomain to the main domain. The reason I’m reaching out is to make sure you won’t have a 404 error on your website.
You have a link to our old blog on the following page: https://www.opensourceagenda.com/projects/awesome-sre
I wonder if you’d be able to replace it with the new one: https://www.catchpoint.com/blog/sla-management-guide
Thanks for linking to Catchpoint.com!
Please don’t hesitate to contact me if something comes!
Best,
Gleb
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 455 |
| ⏳ Timeouts | 1 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 33 |
Errors per input
Errors in README.md
- https://www.loomsystems.com/blog/2017/02/06/spiraling-ops-debt-the-sre-coding-imperative: Failed: Network error (status code: ERR)
- http://queue.acm.org/detail.cfm?id=2839461: Failed: Network error (status code: 403)
- https://queue.acm.org/detail.cfm?id=3028689: Failed: Network error (status code: 403)
- https://dastergon.gr/posts/2020/09/the-production-readiness-spectrum/: Failed: Network error (status code: 404)
- 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://queue.acm.org/detail.cfm?id=2655736: Failed: Network error (status code: 403)
- https://blog.box.com/blog/a-tale-of-postmortems/: Failed: Network error (status code: 403)
- https://queue.acm.org/detail.cfm?id=2371297: 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://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
- 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://twitter.com/The_SRE_Dev: Failed: Network error (status code: 404)
- https://queue.acm.org/detail.cfm?id=2891413: Failed: Network error (status code: 403)
- http://queue.acm.org/detail.cfm?id=2745840: Failed: Network error (status code: 403)
- https://queue.acm.org/detail.cfm?id=3096459&__s=dnkxuaws9pogqdnxmx8i: Failed: Network error (status code: 403)
- https://dastergon.gr/awesome-sre: Failed: Network error (status code: 404)
- http://queue.acm.org/detail.cfm?id=2371516: Failed: Network error (status code: 403)
- https://dastergon.gr/error-budget-calculator/: Failed: Network error (status code: 404)
- https://queue.acm.org/detail.cfm?id=3178371: Failed: Network error (status code: 403)
- https://dzone.com/articles/the-cloudcast-301-sre-and-infrastructure-operation: Failed: Network error (status code: 410)
- https://www.reddit.com/r/IAmA/comments/1w1y5m/we_are_the_google_site_reliability_engineering/: Failed: Network error (status code: 403)
- https://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: 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://dastergon.gr/wheel-of-misfortune/: 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)
- https://www.rootly.io/blog: Failed: Network error (status code: 403)
- http://queue.acm.org/detail.cfm?ref=rss&id=2889274: Failed: Network error (status code: 403)
- https://www.youtube.com/watch?v=bC5dIPzNH24: Failed: Network error (status code: 404)
- https://twitter.com/TwitterSRE: Failed: Network error (status code: 404)
- https://queue.acm.org/detail.cfm?id=3194655: Failed: Network error (status code: 403)
- http://www.networkworld.com/article/3182827/cloud-computing/srecon17-brave-new-world-of-site-reliability-engineering.html: Failed: Network error (status code: 404)
- https://queue.acm.org/detail.cfm?id=3283589: Failed: Network error (status code: 403)
- http://engineering.medallia.com/blog/posts/understanding-site-reliability-engineering-through-movies-and-books/: Timeout (status code: TIMEOUT)
Link Checker Report
Errors were reported while checking the availability of links.
Issues found in 1 input(s). Find details below.
[README.md]:
✗ https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/: Network error while trying to connect to an endpoint via reqwest
⧖ http://www.se-radio.net/2016/12/se-radio-episode-276-bjorn-rabenstein-on-site-reliability-engineering/
✗ https://www.youtube.com/watch?v=bwt6TZjefGM: Network error while trying to connect to an endpoint via reqwest
⧖ https://billduncan.org/the-tail-at-scale/
✗ https://blog.newrelic.com/2018/07/05/site-reliability-engineering-sre/: Network error while trying to connect to an endpoint via reqwest
✗ https://blog.newrelic.com/2017/12/15/new-relic-sre/: Network error while trying to connect to an endpoint via reqwest
⧖ http://www.brendangregg.com/blog/index.html
✗ https://digital-forensics.sans.org/summit-archives/file/summit-archive-1492182549.pdf: Network error while trying to connect to an endpoint via reqwest
✗ https://blog.newrelic.com/2018/01/23/best-sre-tools/: Network error while trying to connect to an endpoint via reqwest
✗ https://blog.squadcast.com/how-to-avoid-on-call-burnout/: Network error while trying to connect to an endpoint via reqwest
✗ https://blog.newrelic.com/2017/10/30/site-reliability-engineer-sre: Network error while trying to connect to an endpoint via reqwest
✗ https://www.youtube.com/watch?v=JLkr6UHXN44&nohtml5=False: Network error while trying to connect to an endpoint via reqwest
🔍 464 Total ✅ 452 OK 🚫 9 Errors (HTTP:9|Timeouts:3)
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 466 |
| ⏳ Timeouts | 0 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 23 |
Errors per input
Errors in README.md
- https://blog.box.com/blog/a-tale-of-postmortems/: 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://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)
- http://www.networkworld.com/article/3182827/cloud-computing/srecon17-brave-new-world-of-site-reliability-engineering.html: Failed: Network error (status code: 404)
- https://www.youtube.com/watch?v=bC5dIPzNH24: Failed: Network error (status code: 404)
- https://dastergon.gr/wheel-of-misfortune/: Failed: Network error (status code: 404)
- https://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
- https://twitter.com/The_SRE_Dev: Failed: Network error (status code: 404)
- https://www.reddit.com/r/IAmA/comments/1w1y5m/we_are_the_google_site_reliability_engineering/: Failed: Network error (status code: 403)
- https://dzone.com/articles/the-cloudcast-301-sre-and-infrastructure-operation: Failed: Network error (status code: 410)
- https://www.reddit.com/r/IAmA/comments/177267/we_are_the_google_site_reliability_team_we_make: Failed: Network error (status code: 403)
- https://www.loomsystems.com/single-post/2016/03/23/So-you-want-to-be-a-Site-Reliability-Engineer: Failed: Network error (status code: ERR)
- https://www.loomsystems.com/blog/2017/02/06/spiraling-ops-debt-the-sre-coding-imperative: Failed: Network error (status code: ERR)
- https://blog.hostedgraphite.com/2018/09/13/how-to-write-a-status-page-update/: Failed: Network error (status code: 404)
- https://www.rootly.io/blog: Failed: Network error (status code: 403)
- https://www.weave.works/blog/gitops-part-3-observability: Failed: Network error (status code: 404)
- https://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
- https://blog.netsil.com/the-4-golden-signals-of-api-health-and-performance-in-cloud-native-applications-a6e87526e74: Failed: Network error (status code: ERR)
- http://engineering.medallia.com/blog/posts/understanding-site-reliability-engineering-through-movies-and-books/: Failed: Network error (status code: ERR)
- https://dastergon.gr/awesome-sre: Failed: Network error (status code: 404)
- https://dastergon.gr/error-budget-calculator/: Failed: Network error (status code: 404)
- https://twitter.com/TwitterSRE: Failed: Network error (status code: 404)
Link Checker Report
Errors were reported while checking the availability of links.
📝 Summary
---------------------
🔍 Total..........453
✅ Successful.....447
⏳ Timeouts.........0
🔀 Redirected.......0
👻 Excluded.........0
🚫 Errors...........6
Errors in README.md
✗ https://blog.newrelic.com/2017/10/30/site-reliability-engineer-sre (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2017/10/30/site-reliability-engineer-sre))
✗ https://danrl.com/blog/srm (HTTP status client error (404 Not Found) for url (https://danrl.com/blog/srm))
✗ https://blog.newrelic.com/2018/01/23/best-sre-tools/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2018/01/23/best-sre-tools))
✗ https://blog.newrelic.com/2018/07/05/site-reliability-engineering-sre/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2018/07/05/site-reliability-engineering-sre))
✗ https://digital-forensics.sans.org/summit-archives/file/summit-archive-1492182549.pdf (HTTP status client error (404 Not Found) for url (https://www.sans.org/digital-forensics-incident-response/summit-archives/file/summit-archive-1492182549.pdf))
✗ https://blog.newrelic.com/2017/12/15/new-relic-sre/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2017/12/15/new-relic-sre))
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 477 |
| ⏳ Timeouts | 2 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 10 |
Errors per input
Errors in README.md
- https://blog.box.com/blog/a-tale-of-postmortems/: Failed: Network error (status code: 403)
- https://twitter.com/The_SRE_Dev: Failed: Network error (status code: 404)
- https://blog.netsil.com/the-4-golden-signals-of-api-health-and-performance-in-cloud-native-applications-a6e87526e74: Failed: Network error (status code: ERR)
- http://engineering.medallia.com/blog/posts/understanding-site-reliability-engineering-through-movies-and-books/: Timeout (status code: TIMEOUT)
- http://the-cloud-book.com/: Failed: Network error (status code: 522)
- 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.netsil.com/beyond-google-sre-what-is-site-reliability-engineering-like-at-medium-71c65bd35f4e: Failed: Network error (status code: ERR)
- https://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
- https://rachelbythebay.com/w/: Timeout (status code: TIMEOUT)
- https://www.loomsystems.com/single-post/2016/03/23/So-you-want-to-be-a-Site-Reliability-Engineer: Failed: Network error (status code: 404)
- 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/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
Link Checker Report
Errors were reported while checking the availability of links.
Issues found in 1 input. Find details below.
[README.md]:
✗ [404] https://blog.newrelic.com/2018/07/05/site-reliability-engineering-sre/ | Network error: Not Found
✗ [404] https://twitter.com/i/moments/924656333495898112 | Network error: Not Found
⧖ [TIMEOUT] https://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660 | Timeout
✗ [404] https://www.youtube.com/watch?v=JLkr6UHXN44&nohtml5=False | Network error: Not Found
✗ [ERROR] https://blog.squadcast.com/how-to-avoid-on-call-burnout/ | Network error: No status code
✗ [404] https://www.cruform.com/sre-capability-map/ | Network error: Not Found
✗ [ERROR] http://blogs.atlassian.com/2016/02/inside-atlassian-sre-use-chatops-run-incident-management/ | Network error: No status code
✗ [404] https://www.youtube.com/watch?v=bwt6TZjefGM | Network error: Not Found
✗ [ERROR] https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/ | Network error: No status code
✗ [ERROR] https://www.apress.com/us/book/9781484205129 | Network error: No status code
✗ [404] http://pages.catchpoint.com/DEVOPS-SRE-AMA-mkty.html | Network error: Not Found
🔍 476 Total ✅ 465 OK 🚫 10 Errors (HTTP:10|Timeouts:1)
Link Checker Report
Errors were reported while checking the availability of links.
Issues found in 1 input(s). Find details below.
[README.md]:
✗ http://pages.catchpoint.com/DEVOPS-SRE-AMA-mkty.html: Network error (reqwest): HTTP status client error (404 Not Found) for url (https://pages.catchpoint.com/DEVOPS-SRE-AMA-mkty)
✗ https://twitter.com/SREBook: Network error (reqwest): HTTP status client error (403 Forbidden) for url (https://twitter.com/SREBook)
✗ https://twitter.com/TwitterSRE: Network error (reqwest): HTTP status client error (403 Forbidden) for url (https://twitter.com/TwitterSRE)
✗ https://twitter.com/SREWeekly: Network error (reqwest): HTTP status client error (403 Forbidden) for url (https://twitter.com/SREWeekly)
✗ https://twitter.com/i/moments/924656333495898112: Network error (reqwest): HTTP status client error (403 Forbidden) for url (https://twitter.com/i/moments/924656333495898112)
✗ https://blog.newrelic.com/2018/07/05/site-reliability-engineering-sre/: Network error (reqwest): HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2018/07/05/site-reliability-engineering-sre)
✗ https://twitter.com/The_SRE_Dev: Network error (reqwest): HTTP status client error (403 Forbidden) for url (https://twitter.com/The_SRE_Dev)
✗ https://twitter.com/googlesre: Network error (reqwest): HTTP status client error (403 Forbidden) for url (https://twitter.com/googlesre)
✗ https://twitter.com/SREcon: Network error (reqwest): HTTP status client error (403 Forbidden) for url (https://twitter.com/SREcon)
✗ https://www.youtube.com/watch?v=bwt6TZjefGM: Network error (reqwest): HTTP status client error (404 Not Found) for url (https://img.youtube.com/vi/bwt6TZjefGM/0.jpg)
✗ https://twitter.com/SREWorkbook: Network error (reqwest): HTTP status client error (403 Forbidden) for url (https://twitter.com/SREWorkbook)
✗ https://twitter.com/usenix: Network error (reqwest): HTTP status client error (403 Forbidden) for url (https://twitter.com/usenix)
✗ https://blog.squadcast.com/how-to-avoid-on-call-burnout/: Network error (reqwest): error sending request for url (https://blog.squadcast.com/how-to-avoid-on-call-burnout/): error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1913: (Hostname mismatch)
✗ https://www.youtube.com/watch?v=JLkr6UHXN44&nohtml5=False: Network error (reqwest): HTTP status client error (404 Not Found) for url (https://img.youtube.com/vi/JLkr6UHXN44/0.jpg)
✗ http://blogs.atlassian.com/2016/02/inside-atlassian-sre-use-chatops-run-incident-management/: Network error (reqwest): error following redirect for url (http://www.atlassian.com/incident-management/devops/chatops): too many redirects
✗ https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/: Network error (reqwest): error sending request for url (https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/): error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1913: (Hostname mismatch)
✗ https://www.apress.com/us/book/9781484205129: Network error (reqwest): error following redirect for url (https://idp.springer.com/transit?redirect_uri=http%3A%2F%2Flink.springer.com%2Fbook%2F10.1007%2F978-1-4842-0511-2&code=81f8fd02-9582-4ca0-8aca-52546ffc3f7f): too many redirects
🔍 472 Total ✅ 455 OK 🚫 17 Errors (HTTP:17)
Link Checker Report
Errors were reported while checking the availability of links.
📝 Summary
---------------------
🔍 Total..........452
✅ Successful.....450
⏳ Timeouts.........2
🔀 Redirected.......0
👻 Excluded.........0
🚫 Errors...........0
Errors in README.md
⧖ http://www.se-radio.net/2016/12/se-radio-episode-276-bjorn-rabenstein-on-site-reliability-engineering/
⧖ http://www.brendangregg.com/blog/index.html
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 465 |
| ⏳ Timeouts | 2 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 22 |
Errors per input
Errors in README.md
- https://www.youtube.com/watch?v=bC5dIPzNH24: 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)
- https://www.inc.com/justin-bariso/meet-postmortem-googles-brilliant-process-tool-for-learning-from-failure.html: Failed: Network error (status code: 403)
- https://twitter.com/The_SRE_Dev: Failed: Network error (status code: 404)
- https://codeascraft.com/2016/11/17/debriefing-facilitation-guide/: Failed: Network error (status code: 403)
- 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://dastergon.gr/posts/2020/09/the-production-readiness-spectrum/: Failed: Network error (status code: 404)
- https://cloud.google.com/blog/big-data/2016/10/a-google-sre-explores-github-reliability-with-bigquery: Failed: Network error (status code: 404)
- https://www.rootly.io/blog: Failed: Network error (status code: 403)
- http://www.networkworld.com/article/3182827/cloud-computing/srecon17-brave-new-world-of-site-reliability-engineering.html: Failed: Network error (status code: 404)
- https://dzone.com/articles/the-cloudcast-301-sre-and-infrastructure-operation: Failed: Network error (status code: 410)
- https://www.loomsystems.com/blog/2017/02/06/spiraling-ops-debt-the-sre-coding-imperative: Failed: Network error (status code: ERR)
- https://techbeacon.com/devops/how-accenture-retrofitted-site-reliability-engineering: Failed: Network error (status code: ERR)
- https://blog.netsil.com/beyond-google-sre-what-is-site-reliability-engineering-like-at-medium-71c65bd35f4e: Failed: Network error (status code: ERR)
- http://engineering.medallia.com/blog/posts/understanding-site-reliability-engineering-through-movies-and-books/: Timeout (status code: TIMEOUT)
- https://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
- https://dastergon.gr/wheel-of-misfortune/: Failed: Network error (status code: 404)
- https://blog.box.com/blog/a-tale-of-postmortems/: Failed: Network error (status code: 403)
- https://twitter.com/TwitterSRE: Failed: Network error (status code: 404)
- https://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
- https://dastergon.gr/awesome-sre: Failed: Network error (status code: 404)
- https://rachelbythebay.com/w/: Timeout (status code: TIMEOUT)
- https://dastergon.gr/error-budget-calculator/: Failed: Network error (status code: 404)
- https://www.squadcast.com/blog/succeeding-with-service-level-objectives: Failed: Network error (status code: 404)
Link Checker Report
Errors were reported while checking the availability of links.
Issues found in 1 input. Find details below.
[README.md]:
⧖ [TIMEOUT] https://rachelbythebay.com/w/ | Timeout
⧖ [TIMEOUT] http://www.brendangregg.com/blog/index.html | Timeout
✗ [404] https://www.youtube.com/watch?v=bwt6TZjefGM | Network error: Not Found
✗ [ERROR] http://blogs.atlassian.com/2016/02/inside-atlassian-sre-use-chatops-run-incident-management/ | Network error: No status code
✗ [ERROR] https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/ | Network error: No status code
⧖ [TIMEOUT] http://www.se-radio.net/2016/12/se-radio-episode-276-bjorn-rabenstein-on-site-reliability-engineering/ | Timeout
✗ [404] http://pages.catchpoint.com/DEVOPS-SRE-AMA-mkty.html | Network error: Not Found
✗ [404] https://www.youtube.com/watch?v=JLkr6UHXN44&nohtml5=False | Network error: Not Found
✗ [404] https://blog.newrelic.com/2018/07/05/site-reliability-engineering-sre/ | Network error: Not Found
✗ [ERROR] https://www.apress.com/us/book/9781484205129 | Network error: No status code
✗ [ERROR] https://blog.squadcast.com/how-to-avoid-on-call-burnout/ | Network error: No status code
✗ [404] https://twitter.com/i/moments/924656333495898112 | Network error: Not Found
🔍 476 Total ✅ 464 OK 🚫 9 Errors (HTTP:9|Timeouts:3)
Link Checker Report
Errors were reported while checking the availability of links.
📝 Summary
---------------------
🔍 Total..........454
✅ Successful.....446
⏳ Timeouts.........2
🔀 Redirected.......0
👻 Excluded.........0
🚫 Errors...........6
Errors in README.md
⧖ http://www.se-radio.net/2016/12/se-radio-episode-276-bjorn-rabenstein-on-site-reliability-engineering/
✗ https://blog.newrelic.com/2018/01/23/best-sre-tools/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2018/01/23/best-sre-tools))
✗ https://danrl.com/blog/srm (HTTP status client error (404 Not Found) for url (https://danrl.com/blog/srm))
✗ https://blog.newrelic.com/2017/10/30/site-reliability-engineer-sre (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2017/10/30/site-reliability-engineer-sre))
✗ https://digital-forensics.sans.org/summit-archives/file/summit-archive-1492182549.pdf (HTTP status client error (404 Not Found) for url (https://www.sans.org/digital-forensics-incident-response/summit-archives/file/summit-archive-1492182549.pdf))
✗ https://blog.newrelic.com/2018/07/05/site-reliability-engineering-sre/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2018/07/05/site-reliability-engineering-sre))
⧖ http://www.brendangregg.com/blog/index.html
✗ https://blog.newrelic.com/2017/12/15/new-relic-sre/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2017/12/15/new-relic-sre))
Link Checker Report
Errors were reported while checking the availability of links.
Issues found in 1 input. Find details below.
[README.md]:
✗ [404] https://www.youtube.com/watch?v=bwt6TZjefGM | Network error: Not Found
✗ [ERR] https://www.vividcortex.com/blog/why-percentiles-dont-work-the-way-you-think | Network error: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921: (Hostname mismatch)
✗ [ERR] http://blogs.atlassian.com/2016/02/inside-atlassian-sre-use-chatops-run-incident-management/ | Network error: error following redirect for url (http://www.atlassian.com/incident-management/devops/chatops): too many redirects
✗ [404] https://blog.newrelic.com/2018/07/05/site-reliability-engineering-sre/ | Network error: Not Found
✗ [ERR] https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/ | Network error: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921: (Hostname mismatch)
✗ [ERR] https://www.vividcortex.com/blog/monitoring-isnt-observability | Network error: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921: (Hostname mismatch)
✗ [404] https://www.cruform.com/sre-capability-map/ | Network error: Not Found
✗ [ERR] https://www.apress.com/us/book/9781484205129 | Network error: error following redirect for url (https://idp.springer.com/transit?redirect_uri=https%3A%2F%2Flink.springer.com%2Fbook%2F10.1007%2F978-1-4842-0511-2&code=40da76f0-f0e1-4965-8f61-09f9e86dff22): too many redirects
✗ [404] https://www.youtube.com/watch?v=JLkr6UHXN44&nohtml5=False | Network error: Not Found
⧖ [TIMEOUT] https://rachelbythebay.com/w/ | Timeout
✗ [404] https://twitter.com/i/moments/924656333495898112 | Network error: Not Found
✗ [404] http://pages.catchpoint.com/DEVOPS-SRE-AMA-mkty.html | Network error: Not Found
✗ [ERR] https://blog.squadcast.com/how-to-avoid-on-call-burnout/ | Network error: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921: (Hostname mismatch)
🔍 479 Total ✅ 466 OK 🚫 12 Errors (HTTP:12|Timeouts:1)
Link Checker Report
Errors were reported while checking the availability of links.
📝 Summary
---------------------
🔍 Total..........453
✅ Successful.....450
⏳ Timeouts.........2
🔀 Redirected.......0
👻 Excluded.........0
🚫 Errors...........1
Errors in README.md
✗ https://sysadmincasts.com/episodes/20-how-to-write-an-incident-report-postmortem (502 Bad Gateway)
⧖ http://www.brendangregg.com/blog/index.html
⧖ http://www.se-radio.net/2016/12/se-radio-episode-276-bjorn-rabenstein-on-site-reliability-engineering/
Link Checker Report
Errors were reported while checking the availability of links.
Issues found in 1 input. Find details below.
[README.md]:
✗ [ERR] https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/ | Network error: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921: (Hostname mismatch)
✗ [404] https://blog.newrelic.com/2018/07/05/site-reliability-engineering-sre/ | Network error: Not Found
✗ [404] https://blog.box.com/blog/a-tale-of-postmortems/ | Network error: Not Found
✗ [404] https://twitter.com/The_SRE_Dev | Network error: Not Found
⧖ [TIMEOUT] https://rachelbythebay.com/w/ | Timeout
✗ [404] https://www.cruform.com/sre-capability-map/ | Network error: Not Found
✗ [404] https://www.youtube.com/watch?v=JLkr6UHXN44&nohtml5=False | Network error: Not Found
✗ [ERR] https://blog.squadcast.com/how-to-avoid-on-call-burnout/ | Network error: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921: (Hostname mismatch)
✗ [404] https://www.youtube.com/watch?v=bwt6TZjefGM | Network error: Not Found
✗ [404] http://pages.catchpoint.com/DEVOPS-SRE-AMA-mkty.html | Network error: Not Found
✗ [ERR] https://www.apress.com/us/book/9781484205129 | Network error: error following redirect for url (https://idp.springer.com/transit?redirect_uri=https%3A%2F%2Flink.springer.com%2Fbook%2F10.1007%2F978-1-4842-0511-2&code=98d2c822-12c6-43b1-9cc2-ab6110bf3d00): too many redirects
✗ [ERR] http://blogs.atlassian.com/2016/02/inside-atlassian-sre-use-chatops-run-incident-management/ | Network error: error following redirect for url (http://www.atlassian.com/incident-management/devops/chatops): too many redirects
✗ [404] https://twitter.com/i/moments/924656333495898112 | Network error: Not Found
🔍 488 Total ✅ 475 OK 🚫 12 Errors (HTTP:12|Timeouts:1)
Link Checker Report
Errors were reported while checking the availability of links.
📝 Summary
---------------------
🔍 Total..........452
✅ Successful.....445
⏳ Timeouts.........0
🔀 Redirected.......0
👻 Excluded.........0
🚫 Errors...........7
Errors in README.md
✗ https://www.ibm.com/developerworks/cloud/library/cl-SLAloadbalance-numanalysis/ (HTTP status client error (400 Bad Request) for url (https://www.ibm.com/developerworks/cloud/library/cl-SLAloadbalance-numanalysis/))
✗ https://blog.newrelic.com/2018/01/23/best-sre-tools/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2018/01/23/best-sre-tools))
✗ https://blog.newrelic.com/2017/10/30/site-reliability-engineer-sre (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2017/10/30/site-reliability-engineer-sre))
✗ https://blog.newrelic.com/2018/07/05/site-reliability-engineering-sre/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2018/07/05/site-reliability-engineering-sre))
✗ https://blog.newrelic.com/2017/12/15/new-relic-sre/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2017/12/15/new-relic-sre))
✗ https://danrl.com/blog/srm (HTTP status client error (404 Not Found) for url (https://danrl.com/blog/srm))
✗ https://www.ibm.com/developerworks/cloud/library/cl-slastandards/ (HTTP status client error (400 Bad Request) for url (https://www.ibm.com/developerworks/cloud/library/cl-slastandards/))
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 473 |
| ⏳ Timeouts | 2 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 14 |
Errors per input
Errors in README.md
- http://engineering.medallia.com/blog/posts/understanding-site-reliability-engineering-through-movies-and-books/: Timeout (status code: TIMEOUT)
- https://twitter.com/The_SRE_Dev: Failed: Network error (status code: 404)
- https://www.inc.com/justin-bariso/meet-postmortem-googles-brilliant-process-tool-for-learning-from-failure.html: Failed: Network error (status code: 403)
- https://rachelbythebay.com/w/: Timeout (status code: TIMEOUT)
- https://www.loomsystems.com/blog/2017/02/06/spiraling-ops-debt-the-sre-coding-imperative: Failed: Network error (status code: ERR)
- https://www.rootly.io/blog: Failed: Network error (status code: 403)
- https://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
- https://dzone.com/articles/the-cloudcast-301-sre-and-infrastructure-operation: Failed: Network error (status code: 410)
- https://www.loomsystems.com/single-post/2016/03/23/So-you-want-to-be-a-Site-Reliability-Engineer: Failed: Network error (status code: ERR)
- https://www.youtube.com/watch?v=bC5dIPzNH24: Failed: Network error (status code: 404)
- https://blog.hostedgraphite.com/2018/09/13/how-to-write-a-status-page-update/: Failed: Network error (status code: 404)
- 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.box.com/blog/a-tale-of-postmortems/: Failed: Network error (status code: 403)
- 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://blog.netsil.com/beyond-google-sre-what-is-site-reliability-engineering-like-at-medium-71c65bd35f4e: Failed: Network error (status code: ERR)
- https://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 466 |
| ⏳ Timeouts | 1 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 22 |
Errors per input
Errors in README.md
- https://dastergon.gr/awesome-sre: 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://dastergon.gr/wheel-of-misfortune/: Failed: Network error (status code: 404)
- 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://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
- https://www.youtube.com/watch?v=bC5dIPzNH24: Failed: Network error (status code: 404)
- https://www.reddit.com/r/IAmA/comments/1w1y5m/we_are_the_google_site_reliability_engineering/: Failed: Network error (status code: 403)
- https://www.rootly.io/blog: Failed: Network error (status code: 403)
- https://dzone.com/articles/the-cloudcast-301-sre-and-infrastructure-operation: Failed: Network error (status code: 410)
- https://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
- http://engineering.medallia.com/blog/posts/understanding-site-reliability-engineering-through-movies-and-books/: Timeout (status code: TIMEOUT)
- https://dastergon.gr/error-budget-calculator/: Failed: Network error (status code: 404)
- http://www.networkworld.com/article/3182827/cloud-computing/srecon17-brave-new-world-of-site-reliability-engineering.html: Failed: Network error (status code: 404)
- https://cloud.google.com/blog/big-data/2016/10/a-google-sre-explores-github-reliability-with-bigquery: Failed: Network error (status code: 404)
- https://twitter.com/The_SRE_Dev: 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)
- https://www.reddit.com/r/IAmA/comments/177267/we_are_the_google_site_reliability_team_we_make: Failed: Network error (status code: 403)
- https://twitter.com/TwitterSRE: Failed: Network error (status code: 404)
- https://www.loomsystems.com/blog/2017/02/06/spiraling-ops-debt-the-sre-coding-imperative: Failed: Network error (status code: ERR)
- https://blog.box.com/blog/a-tale-of-postmortems/: 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://blogs.vmware.com/services-education-insights/2018/02/site-reliability-engineering.html: Failed: Network error (status code: 404)
- https://dastergon.gr/posts/2020/09/the-production-readiness-spectrum/: Failed: Network error (status code: 404)
Link Checker Report
Errors were reported while checking the availability of links.
📝 Summary
---------------------
🔍 Total..........460
✅ Successful.....448
⏳ Timeouts.........2
🔀 Redirected.......0
👻 Excluded.........0
⚠ Unknown..........0
🚫 Errors..........10
Errors in README.md
✗ https://blog.newrelic.com/2018/07/05/site-reliability-engineering-sre/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2018/07/05/site-reliability-engineering-sre))
✗ https://blog.squadcast.com/how-to-avoid-on-call-burnout/ (error sending request for url (https://blog.squadcast.com/how-to-avoid-on-call-burnout/): error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1913: (Hostname mismatch))
✗ https://blog.colinbreck.com/observations-on-observability/ (error sending request for url (https://blog.colinbreck.com/observations-on-observability/): error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1913: (certificate has expired))
✗ https://www.youtube.com/watch?v=bwt6TZjefGM (HTTP status client error (404 Not Found) for url (https://img.youtube.com/vi/bwt6TZjefGM/0.jpg))
✗ https://digital-forensics.sans.org/summit-archives/file/summit-archive-1492182549.pdf (HTTP status client error (404 Not Found) for url (https://www.sans.org/digital-forensics-incident-response/summit-archives/file/summit-archive-1492182549.pdf))
✗ https://blog.newrelic.com/2017/12/15/new-relic-sre/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2017/12/15/new-relic-sre))
⧖ http://www.brendangregg.com/blog/index.html
✗ https://blog.newrelic.com/2017/10/30/site-reliability-engineer-sre (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2017/10/30/site-reliability-engineer-sre))
✗ https://www.youtube.com/watch?v=JLkr6UHXN44&nohtml5=False (HTTP status client error (404 Not Found) for url (https://img.youtube.com/vi/JLkr6UHXN44/0.jpg))
⧖ http://www.se-radio.net/2016/12/se-radio-episode-276-bjorn-rabenstein-on-site-reliability-engineering/
✗ https://blog.newrelic.com/2018/01/23/best-sre-tools/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2018/01/23/best-sre-tools))
✗ https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/ (error sending request for url (https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/): error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1913: (Hostname mismatch))
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 466 |
| ⏳ Timeouts | 2 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 21 |
Errors per input
Errors in README.md
- https://www.rootly.io/blog: 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://twitter.com/TwitterSRE: Failed: Network error (status code: 404)
- https://dzone.com/articles/the-cloudcast-301-sre-and-infrastructure-operation: Failed: Network error (status code: 410)
- https://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
- https://www.weave.works/blog/gitops-part-3-observability: 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://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
- https://rachelbythebay.com/w/: Timeout (status code: TIMEOUT)
- https://dastergon.gr/error-budget-calculator/: Failed: Network error (status code: 404)
- 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://blog.box.com/blog/a-tale-of-postmortems/: Failed: Network error (status code: 403)
- https://www.reddit.com/r/IAmA/comments/177267/we_are_the_google_site_reliability_team_we_make: Failed: Network error (status code: 403)
- http://engineering.medallia.com/blog/posts/understanding-site-reliability-engineering-through-movies-and-books/: 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)
- https://www.loomsystems.com/blog/2017/02/06/spiraling-ops-debt-the-sre-coding-imperative: 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://www.loomsystems.com/single-post/2016/03/23/So-you-want-to-be-a-Site-Reliability-Engineer: Failed: Network error (status code: ERR)
- https://dastergon.gr/wheel-of-misfortune/: Failed: Network error (status code: 404)
- https://www.youtube.com/watch?v=bC5dIPzNH24: Failed: Network error (status code: 404)
- https://dastergon.gr/awesome-sre: Failed: Network error (status code: 404)
- https://www.reddit.com/r/IAmA/comments/1w1y5m/we_are_the_google_site_reliability_engineering/: Failed: Network error (status code: 403)
- https://twitter.com/The_SRE_Dev: Failed: Network error (status code: 404)
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 475 |
| ⏳ Timeouts | 2 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 12 |
Errors per input
Errors in README.md
- http://engineering.medallia.com/blog/posts/understanding-site-reliability-engineering-through-movies-and-books/: Timeout (status code: TIMEOUT)
- https://rachelbythebay.com/w/: Timeout (status code: TIMEOUT)
- https://www.inc.com/justin-bariso/meet-postmortem-googles-brilliant-process-tool-for-learning-from-failure.html: Failed: Network error (status code: 403)
- 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://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
- https://www.rootly.io/blog: Failed: Network error (status code: 403)
- 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://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
- https://www.loomsystems.com/blog/2017/02/06/spiraling-ops-debt-the-sre-coding-imperative: Failed: Network error (status code: 404)
- https://www.youtube.com/watch?v=bC5dIPzNH24: 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: 404)
- https://blog.box.com/blog/a-tale-of-postmortems/: Failed: Network error (status code: 403)
- https://twitter.com/The_SRE_Dev: Failed: Network error (status code: 404)
Link Checker Report
Errors were reported while checking the availability of links.
📝 Summary
---------------------
🔍 Total..........453
✅ Successful.....452
⏳ Timeouts.........1
🔀 Redirected.......0
👻 Excluded.........0
🚫 Errors...........0
Errors in README.md
⧖ https://sysadmincasts.com/episodes/20-how-to-write-an-incident-report-postmortem
Link Checker Report
Errors were reported while checking the availability of links.
📝 Summary
---------------------
🔍 Total..........453
✅ Successful.....450
⏳ Timeouts.........2
🔀 Redirected.......0
👻 Excluded.........0
🚫 Errors...........1
Errors in README.md
✗ https://sysadmincasts.com/episodes/20-how-to-write-an-incident-report-postmortem (502 Bad Gateway)
⧖ http://www.brendangregg.com/blog/index.html
⧖ http://www.se-radio.net/2016/12/se-radio-episode-276-bjorn-rabenstein-on-site-reliability-engineering/
Broken link to Awesome tools
The tools section contains a broken link: https://github.com/squadcastHQ/awesome-sre-tools
Link Checker Report
Errors were reported while checking the availability of links.
Issues found in 1 input(s). Find details below.
[README.md]:
✗ http://pages.catchpoint.com/DEVOPS-SRE-AMA-mkty.html: Network error (reqwest): HTTP status client error (404 Not Found) for url (https://pages.catchpoint.com/DEVOPS-SRE-AMA-mkty)
✗ https://www.youtube.com/watch?v=JLkr6UHXN44&nohtml5=False: Network error (reqwest): HTTP status client error (404 Not Found) for url (https://img.youtube.com/vi/JLkr6UHXN44/0.jpg)
✗ https://blog.squadcast.com/how-to-avoid-on-call-burnout/: Network error (reqwest): error sending request for url (https://blog.squadcast.com/how-to-avoid-on-call-burnout/): error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1913: (Hostname mismatch)
✗ http://blogs.atlassian.com/2016/02/inside-atlassian-sre-use-chatops-run-incident-management/: Network error (reqwest): error following redirect for url (http://www.atlassian.com/incident-management/devops/chatops): too many redirects
✗ https://www.youtube.com/watch?v=bwt6TZjefGM: Network error (reqwest): HTTP status client error (404 Not Found) for url (https://img.youtube.com/vi/bwt6TZjefGM/0.jpg)
⧖ http://www.se-radio.net/2016/12/se-radio-episode-276-bjorn-rabenstein-on-site-reliability-engineering/
✗ https://blog.newrelic.com/2018/07/05/site-reliability-engineering-sre/: Network error (reqwest): HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2018/07/05/site-reliability-engineering-sre)
⧖ https://rachelbythebay.com/w/
⧖ http://www.brendangregg.com/blog/index.html
✗ https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/: Network error (reqwest): error sending request for url (https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/): error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1913: (Hostname mismatch)
✗ https://www.apress.com/us/book/9781484205129: Network error (reqwest): error following redirect for url (https://idp.springer.com/transit?redirect_uri=http%3A%2F%2Flink.springer.com%2Fbook%2F10.1007%2F978-1-4842-0511-2&code=64b3414e-4195-41c1-8ebb-3d8de6ff74ac): too many redirects
🔍 475 Total ✅ 464 OK 🚫 8 Errors (HTTP:8|Timeouts:3)
Link Checker Report
Errors were reported while checking the availability of links.
📝 Summary
---------------------
🔍 Total..........453
✅ Successful.....450
⏳ Timeouts.........2
🔀 Redirected.......0
👻 Excluded.........0
🚫 Errors...........1
Errors in README.md
⧖ http://www.brendangregg.com/blog/index.html
✗ https://sysadmincasts.com/episodes/20-how-to-write-an-incident-report-postmortem (502 Bad Gateway)
⧖ http://www.se-radio.net/2016/12/se-radio-episode-276-bjorn-rabenstein-on-site-reliability-engineering/
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 477 |
| ⏳ Timeouts | 1 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 11 |
Errors per input
Errors in README.md
- https://www.rootly.io/blog: 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://cloud.google.com/blog/big-data/2016/10/a-google-sre-explores-github-reliability-with-bigquery: Failed: Network error (status code: 404)
- https://www.meetup.com/South-Bay-Site-Reliability-Engineering/: Failed: Network error (status code: 404)
- https://twitter.com/The_SRE_Dev: Failed: Network error (status code: 404)
- https://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
- http://engineering.medallia.com/blog/posts/understanding-site-reliability-engineering-through-movies-and-books/: Timeout (status code: TIMEOUT)
- https://blog.box.com/blog/a-tale-of-postmortems/: Failed: Network error (status code: 403)
- https://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
- https://www.loomsystems.com/single-post/2016/03/23/So-you-want-to-be-a-Site-Reliability-Engineer: Failed: Network error (status code: 404)
- 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://blog.netsil.com/beyond-google-sre-what-is-site-reliability-engineering-like-at-medium-71c65bd35f4e: Failed: Network error (status code: ERR)
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 474 |
| ⏳ Timeouts | 1 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 14 |
Errors per input
Errors in README.md
- https://www.rootly.io/blog: 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://www.loomsystems.com/single-post/2016/03/23/So-you-want-to-be-a-Site-Reliability-Engineer: Failed: Network error (status code: ERR)
- http://blog.adnanmasood.com/2016/05/19/intelligent-site-reliability-engineering-a-machine-learning-perspective/: Failed: Network error (status code: 500)
- https://www.youtube.com/watch?v=bC5dIPzNH24: Failed: Network error (status code: 404)
- https://blog.box.com/blog/a-tale-of-postmortems/: Failed: Network error (status code: 403)
- http://engineering.medallia.com/blog/posts/understanding-site-reliability-engineering-through-movies-and-books/: Timeout (status code: TIMEOUT)
- https://blog.netsil.com/beyond-google-sre-what-is-site-reliability-engineering-like-at-medium-71c65bd35f4e: Failed: Network error (status code: ERR)
- https://twitter.com/The_SRE_Dev: 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://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
- https://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
- https://cloud.google.com/blog/big-data/2016/10/a-google-sre-explores-github-reliability-with-bigquery: Failed: Network error (status code: 404)
- https://www.loomsystems.com/blog/2017/02/06/spiraling-ops-debt-the-sre-coding-imperative: Failed: Network error (status code: ERR)
Link Checker Report
Errors were reported while checking the availability of links.
📝 Summary
---------------------
🔍 Total..........457
✅ Successful.....447
⏳ Timeouts.........0
🔀 Redirected.......0
👻 Excluded.........0
🚫 Errors..........10
Errors in README.md
✗ https://blog.squadcast.com/how-to-avoid-on-call-burnout/ (error sending request for url (https://blog.squadcast.com/how-to-avoid-on-call-burnout/): error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1915: (Hostname mismatch))
✗ https://www.youtube.com/watch?v=bwt6TZjefGM (HTTP status client error (404 Not Found) for url (https://img.youtube.com/vi/bwt6TZjefGM/0.jpg))
✗ https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/ (error sending request for url (https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/): error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1915: (Hostname mismatch))
✗ https://blog.newrelic.com/2018/07/05/site-reliability-engineering-sre/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2018/07/05/site-reliability-engineering-sre))
✗ https://danrl.com/blog/srm (HTTP status client error (404 Not Found) for url (https://danrl.com/blog/srm))
✗ https://blog.newrelic.com/2017/12/15/new-relic-sre/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2017/12/15/new-relic-sre))
✗ https://blog.newrelic.com/2017/10/30/site-reliability-engineer-sre (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2017/10/30/site-reliability-engineer-sre))
✗ https://digital-forensics.sans.org/summit-archives/file/summit-archive-1492182549.pdf (HTTP status client error (404 Not Found) for url (https://www.sans.org/digital-forensics-incident-response/summit-archives/file/summit-archive-1492182549.pdf))
✗ https://www.youtube.com/watch?v=JLkr6UHXN44&nohtml5=False (HTTP status client error (404 Not Found) for url (https://img.youtube.com/vi/JLkr6UHXN44/0.jpg))
✗ https://blog.newrelic.com/2018/01/23/best-sre-tools/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2018/01/23/best-sre-tools))
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 470 |
| ⏳ Timeouts | 1 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 18 |
Errors per input
Errors in README.md
- https://blog.box.com/blog/a-tale-of-postmortems/: Failed: Network error (status code: 403)
- 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://www.rootly.io/blog: Failed: Network error (status code: 403)
- https://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
- https://www.loomsystems.com/blog/2017/02/06/spiraling-ops-debt-the-sre-coding-imperative: Failed: Network error (status code: ERR)
- https://twitter.com/The_SRE_Dev: Failed: Network error (status code: 404)
- https://dzone.com/articles/the-cloudcast-301-sre-and-infrastructure-operation: Failed: Network error (status code: 410)
- https://dastergon.gr/posts/2020/09/the-production-readiness-spectrum/: Failed: Network error (status code: 404)
- https://www.inc.com/justin-bariso/meet-postmortem-googles-brilliant-process-tool-for-learning-from-failure.html: Failed: Network error (status code: 403)
- https://www.loomsystems.com/single-post/2016/03/23/So-you-want-to-be-a-Site-Reliability-Engineer: Failed: Network error (status code: ERR)
- https://dastergon.gr/wheel-of-misfortune/: Failed: Network error (status code: 404)
- https://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
- https://dastergon.gr/awesome-sre: Failed: Network error (status code: 404)
- https://dastergon.gr/error-budget-calculator/: Failed: Network error (status code: 404)
- https://cloud.google.com/blog/big-data/2016/10/a-google-sre-explores-github-reliability-with-bigquery: Failed: Network error (status code: 404)
- https://www.youtube.com/watch?v=bC5dIPzNH24: Failed: Network error (status code: 404)
- https://twitter.com/TwitterSRE: Failed: Network error (status code: 404)
- http://engineering.medallia.com/blog/posts/understanding-site-reliability-engineering-through-movies-and-books/: Timeout (status code: TIMEOUT)
- https://blog.netsil.com/beyond-google-sre-what-is-site-reliability-engineering-like-at-medium-71c65bd35f4e: Failed: Network error (status code: ERR)
Link Checker Report
Errors were reported while checking the availability of links.
📝 Summary
---------------------
🔍 Total..........460
✅ Successful.....446
⏳ Timeouts.........0
🔀 Redirected.......0
👻 Excluded.........0
⚠ Unknown..........0
🚫 Errors..........14
Errors in README.md
✗ https://www.reddit.com/r/IAmA/comments/177267/we_are_the_google_site_reliability_team_we_make (HTTP status client error (429 Too Many Requests) for url (https://www.reddit.com/r/IAmA/comments/177267/we_are_the_google_site_reliability_team_we_make))
✗ https://honeycomb.io/blog/2017/01/instrumentation-worst-case-performance-matters/ (HTTP status client error (404 Not Found) for url (https://www.honeycomb.io/blog/2017/01/instrumentation-worst-case-performance-matters/))
✗ https://www.reddit.com/r/IAmA/comments/1w1y5m/we_are_the_google_site_reliability_engineering/ (HTTP status client error (429 Too Many Requests) for url (https://www.reddit.com/r/IAmA/comments/1w1y5m/we_are_the_google_site_reliability_engineering/))
✗ https://honeycomb.io/blog/2018/02/oncall-and-sustainable-software-development/ (HTTP status client error (404 Not Found) for url (https://www.honeycomb.io/blog/2018/02/oncall-and-sustainable-software-development/))
✗ https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/ (error sending request for url (https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/): error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1915: (Hostname mismatch))
✗ https://blog.newrelic.com/2017/10/30/site-reliability-engineer-sre (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2017/10/30/site-reliability-engineer-sre))
✗ https://blog.newrelic.com/2017/12/15/new-relic-sre/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2017/12/15/new-relic-sre))
✗ https://www.youtube.com/watch?v=JLkr6UHXN44&nohtml5=False (HTTP status client error (404 Not Found) for url (https://img.youtube.com/vi/JLkr6UHXN44/0.jpg))
✗ https://honeycomb.io/blog/2017/01/instrumentation-what-does-uptime-mean/ (HTTP status client error (404 Not Found) for url (https://www.honeycomb.io/blog/2017/01/instrumentation-what-does-uptime-mean/))
✗ https://blog.newrelic.com/2018/01/23/best-sre-tools/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2018/01/23/best-sre-tools))
✗ https://blog.squadcast.com/how-to-avoid-on-call-burnout/ (error sending request for url (https://blog.squadcast.com/how-to-avoid-on-call-burnout/): error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1915: (Hostname mismatch))
✗ https://www.youtube.com/watch?v=bwt6TZjefGM (HTTP status client error (404 Not Found) for url (https://img.youtube.com/vi/bwt6TZjefGM/0.jpg))
✗ https://digital-forensics.sans.org/summit-archives/file/summit-archive-1492182549.pdf (HTTP status client error (404 Not Found) for url (https://www.sans.org/digital-forensics-incident-response/summit-archives/file/summit-archive-1492182549.pdf))
✗ https://blog.newrelic.com/2018/07/05/site-reliability-engineering-sre/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2018/07/05/site-reliability-engineering-sre))
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 472 |
| ⏳ Timeouts | 2 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 15 |
Errors per input
Errors in README.md
- https://blog.hostedgraphite.com/2018/09/13/how-to-write-a-status-page-update/: Failed: Network error (status code: 404)
- https://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
- http://engineering.medallia.com/blog/posts/understanding-site-reliability-engineering-through-movies-and-books/: Timeout (status code: TIMEOUT)
- https://blog.box.com/blog/a-tale-of-postmortems/: Failed: Network error (status code: 403)
- 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://www.rootly.io/blog: Failed: Network error (status code: 403)
- https://www.hostedgraphite.com/blog/its-dead-jim-how-we-write-an-incident-postmortem: Failed: Network error (status code: 404)
- https://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
- https://rachelbythebay.com/w/: Timeout (status code: TIMEOUT)
- https://www.hostedgraphite.com/blog/incident-postmortem-template: Failed: Network error (status code: 404)
- https://cloud.google.com/blog/big-data/2016/10/a-google-sre-explores-github-reliability-with-bigquery: Failed: Network error (status code: 404)
- https://www.youtube.com/watch?v=bC5dIPzNH24: 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://www.inc.com/justin-bariso/meet-postmortem-googles-brilliant-process-tool-for-learning-from-failure.html: Failed: Network error (status code: 403)
- https://twitter.com/The_SRE_Dev: Failed: Network error (status code: 404)
- https://www.loomsystems.com/blog/2017/02/06/spiraling-ops-debt-the-sre-coding-imperative: 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: 404)
Link Checker Report
Errors were reported while checking the availability of links.
📝 Summary
---------------------
🔍 Total..........457
✅ Successful.....443
⏳ Timeouts.........2
🔀 Redirected.......0
👻 Excluded.........0
🚫 Errors..........12
Errors in README.md
✗ https://honeycomb.io/blog/2018/02/oncall-and-sustainable-software-development/ (HTTP status client error (404 Not Found) for url (https://www.honeycomb.io/blog/2018/02/oncall-and-sustainable-software-development/))
✗ https://www.youtube.com/watch?v=JLkr6UHXN44&nohtml5=False (HTTP status client error (404 Not Found) for url (https://img.youtube.com/vi/JLkr6UHXN44/0.jpg))
✗ https://blog.newrelic.com/2018/01/23/best-sre-tools/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2018/01/23/best-sre-tools))
✗ https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/ (error sending request for url (https://blog.squadcast.com/intent-based-capacity-planning-autoscaling-kubernetes/): error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1915: (Hostname mismatch))
✗ https://blog.newrelic.com/2017/10/30/site-reliability-engineer-sre (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2017/10/30/site-reliability-engineer-sre))
✗ https://blog.squadcast.com/how-to-avoid-on-call-burnout/ (error sending request for url (https://blog.squadcast.com/how-to-avoid-on-call-burnout/): error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1915: (Hostname mismatch))
✗ https://honeycomb.io/blog/2017/01/instrumentation-what-does-uptime-mean/ (HTTP status client error (404 Not Found) for url (https://www.honeycomb.io/blog/2017/01/instrumentation-what-does-uptime-mean/))
✗ https://honeycomb.io/blog/2017/01/instrumentation-worst-case-performance-matters/ (HTTP status client error (404 Not Found) for url (https://www.honeycomb.io/blog/2017/01/instrumentation-worst-case-performance-matters/))
✗ https://www.youtube.com/watch?v=bwt6TZjefGM (HTTP status client error (404 Not Found) for url (https://img.youtube.com/vi/bwt6TZjefGM/0.jpg))
✗ https://digital-forensics.sans.org/summit-archives/file/summit-archive-1492182549.pdf (HTTP status client error (404 Not Found) for url (https://www.sans.org/digital-forensics-incident-response/summit-archives/file/summit-archive-1492182549.pdf))
✗ https://blog.newrelic.com/2017/12/15/new-relic-sre/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2017/12/15/new-relic-sre))
✗ https://blog.newrelic.com/2018/07/05/site-reliability-engineering-sre/ (HTTP status client error (404 Not Found) for url (https://newrelic.com/blog/2018/07/05/site-reliability-engineering-sre))
⧖ http://www.se-radio.net/2016/12/se-radio-episode-276-bjorn-rabenstein-on-site-reliability-engineering/
⧖ http://www.brendangregg.com/blog/index.html
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 464 |
| ⏳ Timeouts | 2 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 23 |
Errors per input
Errors in README.md
- https://twitter.com/SREcon: Failed: Network error (status code: 404)
- https://www.meetup.com/Site-Reliability-Engineering-Munich/: Failed: Network error (status code: 404)
- https://blog.box.com/blog/a-tale-of-postmortems/: Failed: Network error (status code: 403)
- https://twitter.com/TwitterSRE: Failed: Network error (status code: 404)
- https://twitter.com/The_SRE_Dev: Failed: Network error (status code: 404)
- https://rachelbythebay.com/w/: Timeout (status code: TIMEOUT)
- https://twitter.com/googlesre: Failed: Network error (status code: 404)
- https://twitter.com/SREWorkbook: Failed: Network error (status code: 404)
- 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/the-4-golden-signals-of-api-health-and-performance-in-cloud-native-applications-a6e87526e74: Failed: Network error (status code: ERR)
- https://www.youtube.com/watch?v=bC5dIPzNH24: 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://www.meetup.com/South-Bay-Site-Reliability-Engineering/: Failed: Network error (status code: 404)
- https://twitter.com/usenix: Failed: Network error (status code: 404)
- https://www.meetup.com/San-Francisco-Reliability-Engineering/: Failed: Network error (status code: 404)
- https://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
- https://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
- https://twitter.com/SREBook: Failed: Network error (status code: 404)
- https://twitter.com/SREWeekly: 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: 404)
- https://www.loomsystems.com/blog/2017/02/06/spiraling-ops-debt-the-sre-coding-imperative: Failed: Network error (status code: 404)
- http://engineering.medallia.com/blog/posts/understanding-site-reliability-engineering-through-movies-and-books/: Timeout (status code: TIMEOUT)
- https://www.inc.com/justin-bariso/meet-postmortem-googles-brilliant-process-tool-for-learning-from-failure.html: Failed: Network error (status code: 403)
- https://www.rootly.io/blog: Failed: Network error (status code: 403)
- https://www.meetup.com/Site-Reliability-Engineering-Paris/: Failed: Network error (status code: 404)
Dead link to SRE Tools/SRE Capability Map
Hello, the link to the SRE Capability Map is dead (http 404), the domain name changed for a new one, and the map is not available on the new website.
In Readme.md
- SRE Tools
--- SRE Capability Map -> https://www.cruform.com/sre-capability-map/
Validate Links
Hello, I wrote a tool that can validate README links. It can be run when someone submits a pull request to awesome-sre.
For example, you would see that
https://www.loomsystems.com/single-post/2016/03/23/So-you-want-to-be-a-Site-Reliability-Engineer redirects to
https://www.loomsystems.com/blog/single-post/2016/03/23/so-you-want-to-be-a-site-reliability-engineer
https://www.atlassian.com/it-service/site-reliability-engineering-sre redirects to
http://www.atlassian.com/it-unplugged/devops/site-reliability-engineering-sre
http://126kr.com/article/7vkoxnk6s01 is now 404 🔴
More here https://gist.github.com/828ba5a566d1c4ea7abf3b272c3a5850
This tool is currently being used by
- https://github.com/matteocrippa/awesome-swift
- https://github.com/brabadu/awesome-fonts
- and many more
Examples
- https://travis-ci.org/matteocrippa/awesome-swift/builds/96526196 ok ✅
- https://travis-ci.org/matteocrippa/awesome-swift/builds/96722421 link redirected / rename 🔴
- https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/96763135 bad link / project deleted 🔴
- https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/95754715 dupe 🔴
If you are interested, connect this repo to https://travis-ci.org/ and add a .travis.yml file to the project (you can also use Circle CI or other CI services).
See https://github.com/dkhamsing/awesome_bot for options, more information
Feel free to leave a comment 😄
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 481 |
| ⏳ Timeouts | 0 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 8 |
Errors per input
Errors in README.md
- https://blog.box.com/blog/a-tale-of-postmortems/: Failed: Network error (status code: 404)
- https://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
- 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.netsil.com/the-4-golden-signals-of-api-health-and-performance-in-cloud-native-applications-a6e87526e74: Failed: Network error (status code: ERR)
- https://blog.netsil.com/beyond-google-sre-what-is-site-reliability-engineering-like-at-medium-71c65bd35f4e: Failed: Network error (status code: ERR)
- https://twitter.com/The_SRE_Dev: Failed: Network error (status code: 404)
- https://cloud.google.com/blog/big-data/2016/10/a-google-sre-explores-github-reliability-with-bigquery: Failed: Network error (status code: 404)
- https://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 470 |
| ⏳ Timeouts | 1 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 18 |
Errors per input
Errors in README.md
- https://rachelbythebay.com/w/: Timeout (status code: TIMEOUT)
- https://devblog.xero.com/sre-xero-managing-incidents-part-ii-224a6e06f426: Failed: Network error (status code: ERR)
- 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.netsil.com/the-4-golden-signals-of-api-health-and-performance-in-cloud-native-applications-a6e87526e74: Failed: Network error (status code: ERR)
- https://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
- https://medium.com/devopslinks/how-to-monitor-the-sre-golden-signals-1391cadc7524: Failed: Network error (status code: ERR)
- https://blog.heptio.com/embracing-feedback-2fd703da714f: Failed: Network error (status code: ERR)
- https://www.rootly.io/blog: Failed: Network error (status code: 403)
- 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/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
- https://devblog.xero.com/sre-xero-managing-incidents-part-i-7d02d650a71c: Failed: Network error (status code: ERR)
- https://medium.com/back-market-engineering/how-back-market-sres-prepared-for-black-friday-5f017f343408: Failed: Network error (status code: ERR)
- https://blog.box.com/blog/a-tale-of-postmortems/: 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://sreally.com/hiring-your-first-sre-bdda38ee175d#.2m3sqyuw9: Failed: Network error (status code: ERR)
- https://standalone-sysadmin.com/the-difference-between-site-reliability-engineering-system-administration-and-devops-d05031495499: Failed: Network error (status code: ERR)
- https://medium.com/better-programming/site-reliability-engineering-best-practices-for-data-pipelines-44a78e91f6f0: Failed: Network error (status code: ERR)
- https://tech.buzzfeed.com/checklists-an-operational-gift-aaf42cf0be12: Failed: Network error (status code: ERR)
- https://twitter.com/The_SRE_Dev: Failed: Network error (status code: 404)
Link Checker Report
Summary
| Status | Count |
|---|---|
| 🔍 Total | 489 |
| ✅ Successful | 467 |
| ⏳ Timeouts | 2 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 20 |
Errors per input
Errors in README.md
- https://blog.box.com/blog/a-tale-of-postmortems/: 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://cloud.google.com/blog/big-data/2016/10/a-google-sre-explores-github-reliability-with-bigquery: Failed: Network error (status code: 404)
- https://twitter.com/TwitterSRE: Failed: Network error (status code: 404)
- https://rachelbythebay.com/w/: Timeout (status code: TIMEOUT)
- https://www.rootly.io/blog: Failed: Network error (status code: 403)
- https://dzone.com/articles/the-cloudcast-301-sre-and-infrastructure-operation: Failed: Network error (status code: 410)
- https://blog.netsil.com/beyond-google-sre-what-is-site-reliability-engineering-like-at-medium-71c65bd35f4e: Failed: Network error (status code: ERR)
- https://www.loomsystems.com/single-post/2016/03/23/So-you-want-to-be-a-Site-Reliability-Engineer: Failed: Network error (status code: ERR)
- https://www.youtube.com/watch?v=bC5dIPzNH24: Failed: Network error (status code: 404)
- https://twitter.com/SREWeekly: Failed: Network error (status code: 404)
- 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://twitter.com/googlesre: Failed: Network error (status code: 404)
- https://twitter.com/SREcon: Failed: Network error (status code: 404)
- http://engineering.medallia.com/blog/posts/understanding-site-reliability-engineering-through-movies-and-books/: Timeout (status code: TIMEOUT)
- https://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
- https://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
- https://twitter.com/SREWorkbook: Failed: Network error (status code: 404)
- https://twitter.com/usenix: Failed: Network error (status code: 404)
- https://twitter.com/The_SRE_Dev: Failed: Network error (status code: 404)
- https://www.loomsystems.com/blog/2017/02/06/spiraling-ops-debt-the-sre-coding-imperative: Failed: Network error (status code: ERR)
- https://twitter.com/SREBook: Failed: Network error (status code: 404)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.