Skip to content

Latest commit

 

History

History
124 lines (88 loc) · 3.2 KB

areas-of-interest.md

File metadata and controls

124 lines (88 loc) · 3.2 KB
Raw

Member areas of interest

OpenTelemetry technical committee members, maintainers, and approvers may list their areas of interest below, to help the community to find good points of contact for topics of interest across the project.

Technical committee members are required to list these areas of interest, and this is optional for maintainers and approvers. These listings may be useful to find an appropriate person to tag on an issue, for example.

Members who are specifically employed by a company to contribute to the OpenTelemetry project are recommended to list their company affiliation, so that they may be contacted with vendor-specific concerns.

Technical committee members

Armin Ruech, Dynatrace

  • Trace API and SDK
  • Semantic conventions

Bogdan Drutu, Splunk

  • OpenTelemetry protocol
  • OpenTelemetry collector
  • Metrics API and SDK

Carlos Alberto, Lightstep

  • Trace API and SDK
  • OpenTracing compatibility
  • Semantic conventions

Jack Berg, New Relic

  • Metrics API and SDK
  • Logging API and SDK
  • SDK configuration
  • OpenTelemetry Java
  • OpenTelemetry protocol

Josh MacDonald, Lightstep

  • Metrics API and SDK and data model
  • Metrics collection infrastructure
  • Metrics protocol compatibility
  • OpenTelemetry protocol
  • Trace sampling algorithms
  • Trace API & SDK

Josh Suereth, Google

  • Metrics API and SDK
  • OpenTelemetry Protocol
  • Telemetry correlation (Trace <-> Metrics <-> Logs via Resource, Exemplars, etc.)
  • Protocol compatibility (OpenCensus, Prometheus, Statsd, etc.)
  • Semantic conventions

Reiley Yang, Microsoft

  • Logging API and SDK
  • Metrics API and SDK
  • Trace API and SDK
  • OpenTelemetry .NET
  • OpenTelemetry C++
  • W3C trace context specification

Tigran Najaryan, Splunk

  • OpenTelemetry collector
  • OpenTelemetry protocol
  • OpenTelemetry schemas and versioning
  • Logging API and SDK

Yuri Shkuro, Meta

  • Trace API and SDK
  • Jaeger tracing compatibility
  • OpenTracing compatibility
  • W3C trace context specification

Maintainers and approvers

Maintainers and approvers are invited to list their areas of interest to further assist the community in finding appropriate points of contact.

Alex Boten, Lightstep

  • OpenTelemetry Python
  • OpenTelemetry Collector
  • OTel-Lambda support

Daniel Dyla, Dynatrace

  • OpenTelemetry JavaScript
  • W3C Trace Context Specification
  • Trace and Metrics
  • Trace Sampling

Dan Jaglowski, observIQ

  • OpenTelemetry log collection
  • Logging API and SDK
  • OpenTelemetry metric scrapers
  • Semantic conventions
  • Open Agent Management Protocol

Tom Tan, Microsoft

  • Logging API and SDK
  • Trace API and SDK
  • OpenTelemetry C++
  • OpenTelemetry Protocol