kubernetes-sigs/cluster-api

Distributed Tracing

Open

#3,760 opened on Oct 7, 2020

View on GitHub
 (22 comments) (0 reactions) (1 assignee)Go (1,532 forks)auto 404
help wantedkind/featurepriority/backlogtriage/accepted

Repository metrics

Stars
 (4,267 stars)
PR merge metrics
 (PR metrics pending)

Description

User Story

As a developer/operator I would like to see how one Cluster-API component calls another, and also how they use the Kubernetes API, for learning, troubleshooting or optimisation.

Detailed Description

Calls can be inserted into clusterctl and CAPI controllers to emit "spans". Context can be carried from one component to another via "span context" data in an annotation. See this doc for more details.

/kind feature

Related: #1477

Contributor guide

Research direction
Review the design doc for span propagation details. Identify key components (clusterctl, CAPI controllers) and determine where to insert span creation and context propagation via annotations. Then implement spans and context propagation in the codebase.
Tech stack
go
Domain
backendobservabilityapi
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.
1-2 days
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.
Mostly clear
Prerequisites
GoKubernetesOpenTelemetry
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50