Skip to content

OpenTracing.Integration isn't compatible with OpenTracing interface #2251

Description

@Bessonov

Package + Version

  • @sentry/browser
  • @sentry/node 5.6.2
  • @sentry/opentracing 5.1.2
  • @sentry/integrations 5.6.1
  • raven-js
  • raven-node(raven for node)
  • other:

Version:

0.0.0

Description

Subclass of Tracer in @sentry/opentracing introduce some fields which leads to incompatibility:

import*asOpenTracingfrom'@sentry/opentracing'import{Tracer}from'opentracing'consttracer: Tracer=newTracer()// no opconstot=newOpenTracing.Integration(undefined,tracer)// <-- compile error
{
"resource": "/home/vagrant/workspace/poc-backend/packages/common.errors/src/index.ts",
"owner": "typescript",
"code": "2345",
"severity": 8,
"message": "Argument of type 'import(\"/home/vagrant/workspace/poc-backend/node_modules/opentracing/lib/tracer\").Tracer' is not assignable to parameter of type 'import(\"/home/vagrant/workspace/poc-backend/node_modules/@sentry/opentracing/dist/tracer\").Tracer'.\n Type 'Tracer' is missing the following properties from type 'Tracer': _spans, setTraceId, flush",
"source": "ts",
"startLineNumber": 17,
"startColumn": 51,
"endLineNumber": 17,
"endColumn": 57
}

I didn't find a way to use integrations with OpenTracing either.
How to integrate it with OpenTracing clients like zipkin-javascript-opentracing? Just add traceId to extra?

I've seen that there is more work in #2161. That's the goal of sentry project here? TBH, I would like to see Errors, Traces and Logs in one place and not distributed in Sentry, Jaeger, ELK/EFK and others.

Activity

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions