Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update diagnosis discovery content page #31

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update diagnosis discovery content page #31

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/content.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,3 +14,5 @@ In this approach, we try to identify issues before they occur, or before they si
In this approach, we first try to determine which deployments exhibit similar types of "symptoms" (i.e. health problems). Once we have this grouping, we try to figure out the precise set of symptoms that best characterizes the underlying issue in each of the groups of deployments. Support engineers can then use these symptom patterns to determine the "diagnosis" for these problematic deployments, and programatically define the issue.

* [Notebook](../notebooks/stage/diagnosis-discovery-demo.ipynb)
* [Blog](../docs/blog/diagnosis-discovery-blog.md)
* [DevConf.CZ 2021 Talk](https://youtu.be/RPBXma8NY0s)