Connecting OpenTelemetry spans to your feature flags implementation provides a clear connection between the code, your product and engineering teams, and what your customers are seeing in production. The full context from OpenTelemetry removes the mystery when managing your deployments and customer experience.
| What are you looking to do? |
|---|
| Add new telemetry to your feature flag SDK or library |
| See example integrations |
The goal here is to connect feature flag state and customer experience to the full picture of both production system state so that engineers can move faster in building the product.
-
Find the OpenTelemetry SDK for the language(s) or framework(s) used by your SDK
-
Import the language-specific OpenTelemetry API and patch your library method(s)
-
Use the OpenTelemetry docs to add spans, metrics, and logs to annotate calls to retrieve feature flags produced by your SDK with more actionable context
- As an example, here the Rollbar SDK creates an attribute to linking back to the specific error so the developer can link to the full context of the error
- Send data from your product to an OpenTelemetry collector that outputs to the console and verify output.
- Optional: verify in an OpenTelemetry production tool of your choice
Make your code usable to as many people as possible! If you're looking for help here, contact us at partnerships@lightstep.com. We'd love to help support you!
These example solutions use plugins to generate metrics, logs or traces by automatically-instrumenting Javascript libaries or frameworks. No change to the underlying library or framework is needed.
| Instrumentation Package | Instrumented Package |
|---|---|
| opentelemetry-plugin-splitio | @splitsoftware/splitio |
| opentelemetry-plugin-launchdarkly-node-server | launchdarkly-node-server-sdk |