KusionStack/kusion

Feat: add trace mechanism to facilitate troubleshooting

Open

#1,230 opened on Jul 24, 2024

View on GitHubContributor guide
 (0 comments) (0 reactions) (1 assignee)Go (108 forks)auto 404
hacktoberfestkind/featurepriority/important-longterm

Repository metrics

Stars
 (1,315 stars)
PR merge metrics
 (PR metrics pending)

Description

What would you like to be added?

Add a trace mechanism to record all process steps in the kusion command

Why is this needed?

Add a trace mechanism to facilitate troubleshooting

Contributor guide

Research direction
Investigate existing logging in the codebase and implement a trace mechanism using Go's standard log or OpenTelemetry. Hook into the command execution flow.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70