Skip to content

feat: add Container Stats extension v1.0.1#1052

Open
djhenry wants to merge 1 commit intopodman-desktop:mainfrom
djhenry:add-extension-stats
Open

feat: add Container Stats extension v1.0.1#1052
djhenry wants to merge 1 commit intopodman-desktop:mainfrom
djhenry:add-extension-stats

Conversation

@djhenry
Copy link
Copy Markdown

@djhenry djhenry commented Feb 24, 2026

Summary

  • Add new extension: Container Stats (dhenry/extension-stats v1.0.1)
  • Real-time container and host resource monitoring dashboard
  • Provides per-container CPU, memory, network I/O, block I/O, and PID metrics along with host system overview
  • OCI image: ghcr.io/djhenry/extension-stats:1.0.1
  • License: Apache-2.0

Files added

  • static/api/extensions/dhenry/extension-stats/1.0.1/icon.png
  • static/api/extensions/dhenry/extension-stats/1.0.1/README.md
  • static/api/extensions/dhenry/extension-stats/1.0.1/LICENSE
  • Updated static/api/extensions.json with new extension entry

Verification

  • verify_extensions.sh passes all checks (files present, version/name/publisher match OCI image)

@djhenry djhenry requested review from a team and benoitf as code owners February 24, 2026 03:24
@djhenry djhenry requested review from MarsKubeX and feloy and removed request for a team February 24, 2026 03:24
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Feb 24, 2026

Warning

Rate limit exceeded

@djhenry has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 0 minutes and 47 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between c53d753 and 36fc2e8.

⛔ Files ignored due to path filters (1)
  • static/api/extensions/dhenry/extension-stats/1.0.1/icon.png is excluded by !**/*.png
📒 Files selected for processing (3)
  • static/api/extensions.json
  • static/api/extensions/dhenry/extension-stats/1.0.1/LICENSE
  • static/api/extensions/dhenry/extension-stats/1.0.1/README.md
📝 Walkthrough

Walkthrough

Adds a new Podman Desktop extension entry for Container Stats (extension-stats) by publisher dhenry, version 1.0.1: metadata registered in the extensions catalog (duplicated entry), plus an Apache-2.0 LICENSE and a comprehensive README under the extension's path.

Changes

Cohort / File(s) Summary
Extension Metadata
static/api/extensions.json
Registers extension-stats v1.0.1 with icon, README, LICENSE asset references and OCI image details. The same extension entry is duplicated at two positions in the file.
Extension Documentation & Licensing
static/api/extensions/dhenry/extension-stats/1.0.1/LICENSE, static/api/extensions/dhenry/extension-stats/1.0.1/README.md
Adds Apache License 2.0 text and a comprehensive README describing features, installation, development setup, architecture, configuration, and contribution guidelines.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description check ✅ Passed The description provides comprehensive details about the Container Stats extension, including its purpose, functionality, files added, and verification status, all of which align with the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check ✅ Passed The title 'feat: add Container Stats extension v1.0.1' clearly and concisely summarizes the main change: adding a new extension with its specific name and version.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
static/api/extensions/dhenry/extension-stats/1.0.1/README.md (1)

43-49: Specify languages for fenced code blocks.

markdownlint flags missing language identifiers; add text (or a better fit) to both blocks.

💡 Suggested fix
-   ```
+   ```text
    ghcr.io/djhenry/extension-stats:latest
    ```
-```
+```text
 extension-stats/
 ├── packages/
 │   ├── shared/          # Shared types and utilities
 │   ├── backend/         # Extension backend (Node.js)
 │   └── frontend/        # Dashboard UI (Svelte 5)
 ├── docs/                # Architecture and development specs
 └── .github/workflows/   # CI/CD pipeline
-```
+```

Also applies to: 91-99

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@static/api/extensions/dhenry/extension-stats/1.0.1/README.md` around lines 43
- 49, The fenced code blocks in README.md are missing language identifiers which
markdownlint flags; update both fenced blocks by adding an appropriate language
tag (e.g., add ```text before the line "ghcr.io/djhenry/extension-stats:latest"
and add ```text before the ASCII tree that begins "extension-stats/") so both
code fences include a language specifier and then close them with ``` as
currently present.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@static/api/extensions/dhenry/extension-stats/1.0.1/README.md`:
- Around line 43-49: The fenced code blocks in README.md are missing language
identifiers which markdownlint flags; update both fenced blocks by adding an
appropriate language tag (e.g., add ```text before the line
"ghcr.io/djhenry/extension-stats:latest" and add ```text before the ASCII tree
that begins "extension-stats/") so both code fences include a language specifier
and then close them with ``` as currently present.

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ba08fdb and 8366a28.

⛔ Files ignored due to path filters (1)
  • static/api/extensions/dhenry/extension-stats/1.0.1/icon.png is excluded by !**/*.png
📒 Files selected for processing (3)
  • static/api/extensions.json
  • static/api/extensions/dhenry/extension-stats/1.0.1/LICENSE
  • static/api/extensions/dhenry/extension-stats/1.0.1/README.md

@djhenry djhenry force-pushed the add-extension-stats branch from 8366a28 to c53d753 Compare February 24, 2026 03:50
@djhenry djhenry changed the title Add Container Stats extension (dhenry/extension-stats v1.0.1) feat: add Container Stats extension v1.0.1 Feb 24, 2026
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (1)
static/api/extensions/dhenry/extension-stats/1.0.1/README.md (1)

142-145: Consider a more neutral placeholder in the commit example.

“amazing feature” is informal; swapping it for a more neutral placeholder keeps the doc tone consistent.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@static/api/extensions/dhenry/extension-stats/1.0.1/README.md` around lines
142 - 145, Replace the informal commit example "feat: add amazing feature" with
a neutral placeholder; update the example commit line in the README to use a
generic token such as "feat: add <feature-name>" or "feat: add your-feature" so
the commit message remains professional and consistent with the document tone
(locate the example list lines showing the git commands and change the commit
message text accordingly).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@static/api/extensions/dhenry/extension-stats/1.0.1/README.md`:
- Around line 41-49: The README has fenced code blocks without language
identifiers; update each fenced block that shows the OCI image and the directory
tree to include a language tag (for example use "text") so markdownlint stops
flagging them — specifically add the language identifier to the block containing
"ghcr.io/djhenry/extension-stats:latest" and to the block showing the
"extension-stats/" directory tree (also apply the same change to the similar
blocks referenced at the later section around lines 89-99); keep the content
unchanged, only prepend the opening ``` with the chosen language (e.g.,
```text).
- Around line 37-51: The README.md in the extension bundle references local
relative docs (e.g., INSTALL-SIMPLE.md, INSTALLATION.md,
docs/ARCHITECTURE-1_0_0.md) which will break when installed from the OCI
registry; update those references in README.md to use absolute upstream
repository URLs (or alternatively include the referenced files in the catalog
bundle) so the links resolve outside the source tree—search for the strings
"INSTALL-SIMPLE.md", "INSTALLATION.md", and "docs/ARCHITECTURE-1_0_0.md" in
README.md and replace them with full HTTPS links to the files in the GitHub repo
or add the missing files to the bundle.

---

Nitpick comments:
In `@static/api/extensions/dhenry/extension-stats/1.0.1/README.md`:
- Around line 142-145: Replace the informal commit example "feat: add amazing
feature" with a neutral placeholder; update the example commit line in the
README to use a generic token such as "feat: add <feature-name>" or "feat: add
your-feature" so the commit message remains professional and consistent with the
document tone (locate the example list lines showing the git commands and change
the commit message text accordingly).

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8366a28 and c53d753.

⛔ Files ignored due to path filters (1)
  • static/api/extensions/dhenry/extension-stats/1.0.1/icon.png is excluded by !**/*.png
📒 Files selected for processing (3)
  • static/api/extensions.json
  • static/api/extensions/dhenry/extension-stats/1.0.1/LICENSE
  • static/api/extensions/dhenry/extension-stats/1.0.1/README.md

Comment thread static/api/extensions/dhenry/extension-stats/1.0.1/README.md
Comment thread static/api/extensions/dhenry/extension-stats/1.0.1/README.md
Real-time container and host resource monitoring dashboard providing
per-container CPU, memory, network I/O, block I/O, and PID metrics
along with host system overview.

OCI image: ghcr.io/djhenry/extension-stats:1.0.1

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: David Henry <dhenry@redhat.com>
@djhenry djhenry force-pushed the add-extension-stats branch from c53d753 to 36fc2e8 Compare February 24, 2026 03:53
Copy link
Copy Markdown
Contributor

@axel7083 axel7083 left a comment

Choose a reason for hiding this comment

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

Hey, that's an interesting extension, but I'm wondering if we would not duplicate the data, currently in Containers > Details we have an existing component displaying the CPU / Memory usage of the component

  • Containers -> Details
Image
  • Containers Stats extension
Image

Similarly, the Host System Overview seems pretty familiar with the Settings > Resources page where we display usage for a given machine / connection when available.

Image

The Containers > Details page is pretty limited, and for example does not allow you to graph, so maybe this is something we may want to have improved inside Podman Desktop, but would need to be investigate and study!

@djhenry
Copy link
Copy Markdown
Author

djhenry commented Feb 24, 2026

Hey, that's an interesting extension, but I'm wondering if we would not duplicate the data, currently in Containers > Details we have an existing component displaying the CPU / Memory usage of the component

Hi Axel, thanks for your feedback!
I'm very new here, but I don't see these features in podman-desktop 1.25.1 that I'm running locally. Am I missing something? I'm excited to contribute, but I don't want to duplicate functionality. Thanks in advance for your guidance.

image

@axel7083
Copy link
Copy Markdown
Contributor

Hi Axel, thanks for your feedback! I'm very new here, but I don't see these features in podman-desktop 1.25.1 that I'm running locally. Am I missing something? I'm excited to contribute, but I don't want to duplicate functionality. Thanks in advance for your guidance.

Current we don't have a global view, you can check containers usage by opening a container details (This can be done by clicking the name of the container in the table).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants