feat: add plugin health dashboard with runnable, degraded, and blocke…#627
Open
khat190 wants to merge 2 commits into
Open
feat: add plugin health dashboard with runnable, degraded, and blocke…#627khat190 wants to merge 2 commits into
khat190 wants to merge 2 commits into
Conversation
utksh1
added
level:advanced
utksh1
requested changes
Jun 7, 2026
Owner
utksh1
left a comment
utksh1
left a comment
There was a problem hiding this comment.
The plugin health dashboard cannot be accepted with the current CI result. frontend-checks and backend-lint are failing, and the backend jobs are skipped. Please fix the failing checks and make sure the dashboard is wired without breaking the existing app/test baseline before requesting review again.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed:
Added a Plugin Health Dashboard page at /plugins that shows all registered plugins grouped by operational state: Blocked → Degraded → Runnable.
Why:
Operators had no UI visibility into which plugins are available, which are missing dependencies, and which are blocked by capability policy. This fixes #229.
Changes:
src/pages/PluginHealth.tsx— new page using existing listPlugins() API, groups plugins by health state derived from availability.runnable, missing_binaries, and statussrc/routes.ts— added plugins: '/plugins' routesrc/App.tsx— wired the routesrc/components/Sidebar.tsx— added Plugin Health nav item under Monitortesting/unit/pages/PluginHealth.test.tsx— 14 tests covering grouped states, empty states, error state with retry, summary metrics, ordering, and navigationdocs/plugin_health_dashboard.md— added UI Dashboard section documenting the three health states (Runnable/Degraded/Blocked), sidebar navigation path, plugin card contents, and operator capability policy configuration via SECUSCAN_DENIED_CAPABILITIESHow to test:
cd frontendnpx vitest run testing/unit/pages/PluginHealth.test.tsx --reporter=verboseAll 14 tests pass. To test visually: npm run dev → click Plugin Health in sidebar.
Known trade-offs:
Uses existing GET /plugins endpoint — no new backend endpoint needed since availability data is already returned per plugin.
Related issues:Closes #229