[M6.2] Metrics

Open
  • Is something wrong?
#233 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
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
angular, docker, typescript
Domain
full-stack, observability

Research direction

Start by tracing the agent, control plane, and web UI components, then inspect the M1.4 dependency to understand what infrastructure is already available. The issue calls for container, node, and Caddy metrics to reach VictoriaMetrics and for dashboard charts; done means the dashboard shows real CPU, memory, and request data.

Written by the indexing model from the issue text.

Description

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

M6.2

Track

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

Scope
  • Container, node and Caddy metrics to VictoriaMetrics; charts in UI.
Acceptance criteria

Real CPU, memory and request charts in the dashboard.

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.