Add runbooks for observability controller alerts #280
Conversation
kubevirt-bot
added
the
dco-signoff: yes
|
@machadovilaca: GitHub didn't allow me to request PR reviews from the following users: jherrman. Note that only kubevirt members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
There was a problem hiding this comment.
Hi @machadovilaca , added a couple of suggestions and comments for the text, by way of writer review. Apply them as you see fit :-)
Cheers,
J.
machadovilaca
force-pushed
the
add-observability-controller-alerts-runbooks
branch
from
b4fcc01 to
d822c7d
Compare
|
updated @jherrman |
There was a problem hiding this comment.
@machadovilaca , apologies for the delay. Added a couple more suggestions for minor rewording, but otherwise this is ship-shape from my side :-)
machadovilaca
force-pushed
the
add-observability-controller-alerts-runbooks
branch
from
d822c7d to
a5cc59e
Compare
|
@jherrman updated 🚀 |
|
/lgtm |
|
@machadovilaca some of the command are grouped together so the user cant use the copy function. Can you please update? |
- HAControlPlaneDown - NodeNetworkInterfaceDown - HighCPUWorkload Signed-off-by: João Vilaça <[email protected]>
machadovilaca
force-pushed
the
add-observability-controller-alerts-runbooks
branch
from
a5cc59e to
c546cb5
Compare
@sradco updated |
| - Verify CPU, memory, and disk usage | ||
| ```bash | ||
| # Check the node's CPU and memory resource usage | ||
| kubectl top node <node-name> |
There was a problem hiding this comment.
we know how much usage will count as problematic?
| - Consider replacing the node if necessary | ||
|
|
||
| ## Additional notes | ||
| - Maintain at least three control plane nodes for high availability |
There was a problem hiding this comment.
| - Maintain at least three control plane nodes for high availability | |
| - Maintain at least 3 control plane nodes for high availability |
| ## Additional notes | ||
| - Maintain at least three control plane nodes for high availability | ||
| - Monitor etcd cluster health if the affected node runs etcd | ||
| - Document any infrastructure-specific recovery procedures |
There was a problem hiding this comment.
I'm not sure I understand this sentence, where to document? how it can help?
|
/lgtm |
…vability-controller-alerts-runbooks Add runbooks for observability controller alerts
Add runbooks for observability controller alerts
/cc @sradco @jherrman
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.
Release note: