[M6.1] Log shipping, search and container exec

Open
  • Is something wrong?
#232 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
angular, docker, typescript
Domain
api, backend, frontend, observability

Research direction

Start by reading the implementation of the agent, control plane, and web UI, plus dependency M1.4; the issue does not name specific files or tests. Trace log shipping to VictoriaLogs and the gateway's ExecStream path, including permission checks and auditing. Done when running application logs appear live and are searchable in the UI, and exec sessions are audited and refused without permission.

Written by the indexing model from the issue text.

Description

priority:P1 security-review task track:agent track:control-plane track:web
Task id

M6.1

Track

A: agent, C: control plane, W: web UI

Scope
  • Agent ships logs to VictoriaLogs with labels; UI live tail and search; 30-day retention.
  • ExecStream: typed, RBAC-checked and audited container exec sessions (rule 3); the gateway currently answers Unimplemented.
Acceptance criteria

Logs of a running application appear in the UI live and are searchable; exec sessions are audited, and refused without the permission.

Depends on

M1.4

Dominant language
TypeScript
Stars
2
Forks
1
Avg merge
7h 17m
Merged PRs (30d)
197

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from shipkeepdev/shipkeep

All issues in shipkeepdev/shipkeep

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.