Azure / Azure/azure-container-networking

[Stateless CNI] Improve logs sent via CNI Telemetry Sidecar

Open
#4,225 1 comment 0 reactions 0 assignees View on GitHub
cni stale telemetry
Dominant language
Go
Stars
434
Forks
276
Avg merge
5d 20h
Merged PRs (30d)
33

Description

Following #3824, we need improvements to send additional information that are helpful in troubleshooting CNI-related issues that reveal the behaviour of CNI and not just the happy path for ADD/DELETE. There should also be a way to identify the CNI binary that is executing when initializing.

Contributor guide

Open the contributing guide

Research direction

Start by reading #3824 and locating the Stateless CNI Telemetry Sidecar plus its ADD/DELETE and initialization entry points. Determine which troubleshooting information is needed for non-happy-path CNI behavior and how to identify the executing CNI binary; the issue names no files or tests, so completion criteria need clarification.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.