Adding runbook for 'CephXattrSetLatency' alert

[aruniiird]

No description provided.

[aruniiird]

/retest-required

[agarwal-mudit]

@aruniiird

1. Who should review this PR, pls reach out.
2. You need to fix the lint error

[aruniiird]

@weirdwiz , can you please take a look?

[aruniiird]

@Rakshith-R , can you please take a look at this runbook doc?

[Rakshith-R]

We should not use upstream links in our downstream product runbooks ?

[aruniiird]

Done

[BlaineEXE]

This is a good, consise summary of triage steps for customers. Customers with high-quality admins should be able to self-support with this doc, and customers still having difficulties will have good additional info to bring to support requests. No concerns adding this.

[aruniiird]

@agarwal-mudit , the PR is good to go now. Please check.
Thanks

[Rakshith-R]

We should be using odf cli where possible

@subham.kumar.rai ^

I don't think users can understand anything with outputs of step 2 and step 6.

@aruniiird you have used links to other runbooks here, users will be directed to github repo instead of viewing the runbook on the console ?

[aruniiird]

@Rakshith-R

We should be using odf cli where possible

@subham.kumar.rai ^

This should be done in all the other (applicable) runbooks as well. I will take this as a separate issue.
PS: also we have to see which odf versions the odf cli was introduced and add notes accordingly.

I don't think users can understand anything with outputs of step 2 and step 6.

Thanks for the feedback on the audience level.
If you are pointing to these two steps, Step 2: Check MDS Performance Metrics and Step 6: Check for Lock Contention, I included those steps primarily for admins who might be familiar with memory/process dump commands, and as a way to gather diagnostic data for our support team.

Rather than removing them entirely, perhaps we could reframe them as optional (or even as an Advanced) diagnostic steps? This keeps the guide useful for experts without confusing beginners. However, if you believe these specific metrics won't lead to a resolution, let me know and I'll gladly take them out.

@aruniiird you have used links to other runbooks here, users will be directed to github repo instead of viewing the runbook on the console ?

All our alerts has a runbook_url session, which points to this github repo.
Example: https://github.com/red-hat-storage/ocs-operator/blob/main/metrics/deploy/prometheus-ocs-rules.yaml
It is standard practice to link to an existing runbook if the mitigation steps are already documented elsewhere.

[openshift-ci]

@aruniiird: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

[agarwal-mudit]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agarwal-mudit, aruniiird, BlaineEXE

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• alerts/openshift-container-storage-operator/OWNERS [BlaineEXE,agarwal-mudit]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment