feature: Metrics

Open
#9 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
observability

Research direction

The issue names no files, tests, or entry points. Start by locating the agent's sync-operation path and CLI setup, then determine how a dedicated metrics address and an optional workspace-ID grouping flag fit there; done means emitting OpenTelemetry metrics for actual syncs without requiring high-cardinality grouping.

Written by the indexing model from the issue text.

Description

kind/feature
Feature Description

The agent should be able to emit OpenTelemetry metrics on a dedicated metrics address. I would like to see the amount of sync operations (not all reconciliations, but those were things actually change), optionally grouped by kcp workspace ID (this should be optional via CLI flag because of the high cardinality).

Proposed Solution

Integrate the necessary Go libraries and have at it.

Alternative Solutions

No response

Want to contribute?
  • I would like to work on this issue.
Additional Context

No response

Dominant language
Go
Stars
25
Forks
30
Avg merge
3d 9h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

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 kcp-dev/api-syncagent

All issues in kcp-dev/api-syncagent

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.