镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

Transfer DataDog/orchestrion-js to the org #1011

Closed

Description

@bengl

Earlier this year, we (Datadog) released Orchestrion-JS, a code instrumentation tool that uses SWC to transform JavaScript, either at load time or statically through bundler plugins, in order to add TracingChannel publishes into otherwise-uninstrumented library code. This is intended as a successor to import-in-the-middle.

The implementation details of import-in-the-middle make it impossible to properly instrument some libraries. Orchestrion-JS avoids these issues by transforming source code directly, rather than relying on monkey-patching live objects in the runtime.

Since the release, there's been active participation in the project, particularly from folks who were previously working on/with import-in-the-middle (i.e. other APM vendors). We (Datadog and the other contributors) think that because of this, much like with import-in-the-middle, the Node.js GitHub org is a better home for Orchestrion-JS. Therefore, we're requesting this transfer.

The existing contributors have all agreed to continue with maintenance, review, etc., and that's @bengl (me), @simon-id, @jsumners-nr, @bizob2828, @AbhiPrasad, and @timfish, so we can all be added to a new team for maintenance.

For reference, here's the issue opened for transferring import-in-the-middle.

Activity

  1. mcollina commented on Oct 15, 2025

    @mcollina
    SponsorMember

    Approved, let's coordinate for the move and setting up the team.

  2. bengl commented on Oct 31, 2025

    @bengl
    MemberAuthor

    The repo has been transferred, and a team has been created to maintain it. I'll close this now. As always, please feel free to re-open if necessary.

  3. GeoffreyBooth commented on Oct 31, 2025

    @GeoffreyBooth
    Member

    Orchestrion-JS avoids these issues by transforming source code directly, rather than relying on monkey-patching live objects in the runtime.

    Ever since you proposed this, this has felt like the right solution to the instrumentation problem. I feel like one step further in the direction that Orchestrion takes us would be to upstream these transforms into the patched projects themselves—so open PRs to the projects to bake TracingChannel support into the projects directly, avoiding the need for them to be patched. Perhaps this can also be an effort led by the new Orchestrion team?

  4. jsumners-nr commented on Nov 3, 2025

    @jsumners-nr

    I think everyone on the team wants to get there, but it should be recognized that not everything we patch is going to want to incorporate our changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions