open-telemetry/opentelemetry-specification

Define what "traces" as a signal type means

Open

#2,792 opened on Sep 13, 2022

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Makefile (987 forks)auto 404
[label deprecated] triaged-acceptedhelp wantedspec:trace

Repository metrics

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

Description

What are you trying to achieve?

When OpenTelemetry refers to different "signals", we should have some definition of each signal.

What did you expect to see?

Have the definition of traces in the Glossary https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/glossary.md

Contributor guide

Research direction
Review the existing OpenTelemetry specification Glossary file at specifications/glossary.md and add a definition for 'traces' as a signal type, following the format of existing entries.
Tech stack
None
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
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
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90