port stackdriver trace exporter from OpenCensus.

[naseemkullah]

Does one exist for js?

[mayurkale22]

Not yet, but we can port stackdriver trace exporter from OpenCensus.

[dyladan]

I'll take this

[mayurkale22]

The reference implementation has both trace and monitoring (metrics) exporters in the same package, maybe we should follow the same pattern here and include trace exporter first and monitoring later.

[dyladan]

Depending on how much code is shared I would prefer to actually keep them as separate packages. If a customer only needs one of them we are unnecessarily increasing their deployment size if they are together.

If there is shared code, we could make it a separate package?

• @opentelemetry/exporter-stackdriver-cloudtrace
• @opentelemetry/exporter-stackdriver-monitoring
• @opentelemetry/exporter-stackdriver-base
  • Only if there is enough shared code to justify a third package.

All three could live in packages/opentelemetry-stackdriver/ directory similar to pg and pg-pool

[mayurkale22]

AFAIK only resources(common-utils) stuff is shared between these two.

If a customer only needs one of them we are unnecessarily increasing their deployment size if they are together.

I completely agree with this and looks like OpenTelemetry Go also implemented like that : https://github.com/open-telemetry/opentelemetry-go/tree/master/exporter.

[mayurkale22]

Closing via #648