docs(system-design): add observability and SRE guide - #46
Merged
Merged
Conversation
Co-authored-by: Codex <codex@openai.com>
Co-authored-by: Codex <codex@openai.com>
shalshcode08
marked this pull request as ready for review
August 6, 2026 07:51
…re-incident-response
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
TOPICS.md defines Observability, SRE, capacity planning, and incident response as System Design Topic 13. This guide provides in-depth, easy-language learning and interview preparation while staying language-neutral and using only an approved Go example where concrete code improves understanding.
Scope
Only these files change:
src/content/systemdesign/observability-sre-capacity-planning-incident-response.htmlmanifest.jsonNo tests, styles, shared design, or TOPICS.md files were changed.
Validation
npx prettier --write src/content/systemdesign/observability-sre-capacity-planning-incident-response.html manifest.jsonnpm testnpm run buildgit diff --check->and>=checks for HTML-safe diagram and pseudocode contentReferences
Technical claims are grounded in current primary official OpenTelemetry specifications and documentation, W3C Trace Context and Baggage specifications, Prometheus practices, Google SRE books and workbooks, NIST SP 800-61 Rev. 3, and Oracle Java Flight Recorder documentation.