open-telemetry/opentelemetry-specification

Make the Resource accessible to Logging Library SDK

Open

#1,330 opened on Jan 11, 2021

View on GitHub
 (8 comments) (1 reaction) (0 assignees)Makefile (987 forks)auto 404
area:apiarea:sdkhelp wantedrelease:after-gaspec:logsspec:resource

Repository metrics

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

Description

What are you trying to achieve? I want to enrich legacy first-party application logs with resource information. In order to do so, I have to make resource attributes accessible while configuring logging patterns. Logging happens in user code, but the Resource is currently a part of SDK, rather than API, which means that an application must depend on SDK, rather than API, to write resource attributes to a log file.

Additional context.

Related issue in opentelemetry-java: https://github.com/open-telemetry/opentelemetry-java/issues/2466

Contributor guide

Research direction
Review the related opentelemetry java issue #2466 and understand the Resource class location. Propose moving Resource from SDK to API in the specification, ensuring backward compatibility and minimal impact on existing code.
Tech stack
None
Domain
apiobservability
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
Understanding of OpenTelemetry API/SDK separation
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30