Skip to content

Conversation

@arkadeepsen
Copy link

@arkadeepsen arkadeepsen commented Oct 30, 2025

What this PR does / why we need it:

Plugin to analyze sosreports. The plugin offers various areas for analysis. By default, all the areas are analyzed. The individual areas can be also be optionally enabled/disabled.

Uasge: /sosreport:analyze <path-to-sosreport> [--only <areas>] [--skip <areas>]

assisted-by: Claude

Which issue(s) this PR fixes:

Fixes

Special notes for your reviewer:

Checklist:

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.

Plugin to analyze sosreports. The plugin offers various areas for analysis. By default, all the areas are analyzed.
The individual areas can be also be optionally enabled/disabled.

Uasge: /sosreport:analyze <path-to-sosreport> [--only <areas>] [--skip <areas>]
@openshift-ci openshift-ci bot requested review from bentito and brandisher October 30, 2025 13:14
@openshift-ci
Copy link

openshift-ci bot commented Oct 30, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: arkadeepsen
Once this PR has been reviewed and has the lgtm label, please assign stbenjam for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Oct 30, 2025
@openshift-ci
Copy link

openshift-ci bot commented Oct 30, 2025

Hi @arkadeepsen. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@@ -0,0 +1,455 @@
---
name: Resource Analysis
description: Analyze system resource usage including memory, CPU, disk, and processes
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The only thing loaded into an LLM's context is the skill description, these should all be a little more verbose to tell it when to use the skill. This one's worded generically enough it could try to do it for things other than sosreports.

The "When To Use This Skill" section is helpful but Claude won't read it until it thinks it should use it

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added more details in the description of each skill.

Updated the descriptions for various analysis skills in the sosreport plugin to provide more detailed information on the data extracted and the issues diagnosed. This includes Logs Analysis, Network Analysis, Resource Analysis, and System Configuration Analysis.
@stbenjam
Copy link
Member

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants