open-telemetry / open-telemetry/opentelemetry-cpp

Add support for event driven framework

Open
#1,250 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

do-not-stale good first issue help wanted
Dominant language
C++
Stars
1.4k
Forks
632
Avg merge
1d 13h
Merged PRs (30d)
75

Description

This would be eventually required for

  • To support async interface between span/log processor and exporters.
  • Async IO while exporting the spans.
  • Timers to poll for Spans in BatchSpanProcessor, and metrics in PeriodicMetricReader.
  • Asynchronously collect metrics for all the instruments across all the meters ( this would be a costly operation sequentially or even using threads).

References:

  • #63 - Initial work has been done in this PR.
  • hiredis: event adaptor used by Redis database as suggested by @owent
  • libwebsockets - Suggested by @owent

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing issue #63 and its initial work, then compare the event adapters in the referenced hiredis adapters and libwebsockets event-libs directories. Define the event-driven requirements for async exporting, timers, and metric collection before implementation; done should include an agreed design and demonstrated integration across the listed SDK operations.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
distributed-systems, observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.