open-telemetry/opentelemetry-specification

Completeness of semantic convention for k8s resources

Closed

#2,283 opened on Jan 21, 2022

View on GitHubContributor guide
 (5 comments) (0 reactions) (0 assignees)Makefile (987 forks)auto 404
help wantedspec:resource

Repository metrics

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

Description

What are you trying to achieve? Currently only few k8s object have a opentelemetry specification but we want a specification that covers all k8s objects that can be monitored. What did you expect to see? All k8s objects are modelled as opentelemetry resource with semantic convention for attributes defining these k8s resources.

Should this be an OTEP?

Contributor guide

Research direction
Review the existing Kubernetes resource semantic conventions in the OpenTelemetry specification, identify gaps for other Kubernetes objects, and propose a plan to cover all. Consider whether an OTEP is needed.
Tech stack
None
Domain
observability
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.
Clear
Prerequisites
GitKubernetesOpenTelemetry concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65