feat(host-detail): live Activity tab (host-scoped feed) (Phase 2a)#618
Merged
Conversation
frontend-host-detail v1.7.0 (AC-43). Phase 2a of the activity readability initiative (docs/engineering/activity_readability_plan.md). The host-detail Activity tab was a deferred stub, so the Recent-activity card's 'View all' link dead-ended. It now mounts HostActivityTab — the host-scoped unified feed at GET /api/v1/activity?host_id=X with cursor pagination (useInfiniteQuery + Load more), source filter chips (All/Monitoring/Compliance/Intelligence/Alert), and the shared ActivityRow + eventDisplay rendering. Activity joins Compliance/Remediation as a live tab (removed from the TAB_BACKEND_SUBSYSTEM stub registry), mirroring the exact precedent set when Compliance went live. The Audit log tab stays a stub for now: audit events carry no host_id, so a host-scoped audit view needs backend resource=host filtering (Phase 2b), which is also where the keep-vs-drop decision for that tab is made. Verified live: the owas-tst01 Activity tab renders the paginated feed with working filter chips. Full frontend suite (320) + specter (111) green.
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
1 participant
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.
Phase 2a of the activity readability initiative (
docs/engineering/activity_readability_plan.md) — finish a deferred host-detail stub.The host-detail Activity tab was a stub, so the Recent-activity card's
"View all" link dead-ended. It now mounts HostActivityTab — the
host-scoped unified feed (
GET /api/v1/activity?host_id=X):useInfiniteQuery+ a Load more control.(Audit omitted — audit has no
host_id, so a host-scoped audit filter isempty by design).
ActivityRow+eventDisplayrendering (Phase 0/1).Activity joins Compliance/Remediation as a live tab (removed from the
TAB_BACKEND_SUBSYSTEMstub registry), mirroring the exact precedent whenCompliance went live.
Audit log tab stays a stub for now: a host-scoped audit view needs backend
resource=hostfiltering, which lands in Phase 2b along with thekeep-vs-drop decision for that tab and the per-id detail endpoints.
Verified live on
owas-tst01: the Activity tab renders the paginated feedwith working filter chips.
Spec
frontend-host-detailv1.7.0 (AC-43). Full frontend suite (320) +specter (111, incl. structural coverage) green.