open-telemetry/opentelemetry-php

[opentelemetry-php-contrib] OtelSdkBundle roadmap questions

Open

#1,203 opened on Jan 3, 2024

View on GitHub
 (6 comments) (2 reactions) (0 assignees)PHP (224 forks)auto 404
help wanted

Repository metrics

Stars
 (894 stars)
PR merge metrics
 (Avg merge 5d 5h) (5 merged PRs in 30d)

Description

Hi, I'd like to use OtelSdkBundle to start adopting opentelemetry. Currently there is abandoned package open-telemetry/contrib-sdk-bundle which suggests using open-telemetry/symfony-sdk-bundle.
This package directs to a read-only repository containing two bundles:

  • open-telemetry/contrib-sdk-bundle
  • open-telemetry/contrib-symfony-instrumentation-bundle

The first one open-telemetry/contrib-sdk-bundle in its readme mentions the uprising Instrumentation bundle (I guess the second one) which will add instrumentation for symfony project.

I have a few questions:

  1. Is there any timeline for a stable release? When we can expect to see version 1.0.0?
  2. What is the scope for the stable version for open-telemetry/contrib-sdk-bundle?
  3. Is there any publicly available roadmap where we can track development progress?
  4. What is the scope for the stable version of open-telemetry/contrib-symfony-instrumentation-bundle?
  5. In terms of backward compatibility: should we expect any breaking changes before version 1.0.0? I know that semantic versioning allows breaking changes before stable release but I'm asking about Your plans/policy. Do You have a large refactor in mind that could lead to breaking change in the public API?

Contributor guide

Research direction
Investigate the existing issues, discussions, and documentation for open telemetry/opentelemetry php and its symfony bundles (open telemetry/contrib sdk bundle, open telemetry/symfony sdk bundle) to provide answers to the roadmap questions. Focus on version timelines, scope, and backward compatibility plans.
Tech stack
php
Domain
backendapi
Issue type
Research
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
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80