Configuration for server-side observability

You can configure the observability plugin for the .NET (server-side) SDK through a mix of environment variables, OpenTelemetry configuration options, and plugin configuration options.

Use the ObservabilityPlugin.ObservabilityPluginBuilder to set the options. In many cases, you can use an OpenTelemetry-specific environment variable instead, if you prefer. For example, if you want to set a custom OTLP endpoint, you can either set OtlpEndpoint in your ObservabilityPlugin.ObservabilityPluginBuilder, or you can set the OTEL_EXPORTER_OTLP_ENDPOINT environment variable.

Here’s how:

1
var builder = WebApplication.CreateBuilder(args);
2
3
var config = Configuration.Builder("YOUR_SDK_KEY")
4
    .Plugins(new PluginConfigurationBuilder()
5
        .Add(ObservabilityPlugin.Builder(builder.Services)
6
            .WithServiceName("example-service")
7
            // we recommend setting service version to the latest deployed git SHA
8
            .WithServiceVersion("example-sha")
9
            .Build())).Build();
10
11
// Building the LdClient with the Observability plugin. This line will add services to the web application.
12
var client = new LdClient(config);
13
14
// Client must be built before your web application.
15
var app = builder.Build();

For a complete list of configuration options, read ObservabilityPlugin.ObservabilityPluginBuilder.

You can configure the observability plugin for the Go SDK through the plugin’s options.

Use the functions in the Option type to set the options.

Here’s how:

1
client, _ := ld.MakeCustomClient("YOUR_SDK_KEY",
2
  ld.Config{
3
    Plugins: []ldplugins.Plugin{
4
      ldobserve.NewObservabilityPlugin(
5
        ldobserve.WithServiceName("example-service"),
6
        // we recommend setting service version to the latest deployed git SHA
7
        ldobserve.WithServiceVersion("example-sha"),
8
      ),
9
    },
10
  }, 5*time.Second)

For a complete list of configuration options, read Option.

You can configure the observability plugin for the Node.js (server-side) SDK through a mix of environment variables, OpenTelemetry configuration options, and plugin configuration options.

Environment variables

The environment variables specify where to enable instrumentation:

• LAUNCHDARKLY_OTEL_NODE_ENABLE_FILESYSTEM_INSTRUMENTATION enables file system instrumentation. It defaults to false.
• LAUNCHDARKLY_OTEL_NODE_ENABLE_OUTGOING_HTTP_INSTRUMENTATION enables outgoing HTTP instrumentation. It defaults to true. It only affects outgoing HTTP requests instrumented by @opentelemetry/instrumentation-http.

OpenTelemetry configuration options

If you are already using OpenTelemetry configuration options for Node in your application, you can continue to use them.

When you use the observability plugin, the @opentelemetry/instrumentation-fs instrumentation behaves as follows:

• The instrumentation will only be enabled if LAUNCHDARKLY_OTEL_NODE_ENABLE_FILESYSTEM_INSTRUMENTATION is true.
• The instruction is unaffected by the OTEL_NODE_ENABLED_INSTRUMENTATIONS and OTEL_NODE_DISABLED_INSTRUMENTATIONS OpenTelemetry environment variables.

Plugin configuration options

To specify the observability plugin configuration options, use the NodeOptions interface to set the options.

Here’s how:

1
const client = init(
2
  'YOUR_SDK_KEY',
3
  {
4
    plugins: [
5
      new Observability({
6
        serviceName: 'example-service',
7
        // we recommend setting serviceVersion to the latest deployed git SHA
8
        serviceVersion: 'example-sha'
9
      })
10
    ]
11
  }
12
)

For a complete list of configuration options, read NodeOptions.

You can configure the observability plugin for the Python SDK through a mix of environment variables, OpenTelemetry configuration options, and plugin configuration options.

Use the ObservabilityConfig class to set the options. In many cases, you can use an OpenTelemetry-specific environment variable instead, if you prefer. For example, if you want to set a custom OTLP endpoint, you can either set otlp_endpoint in your ObservabilityConfig, or you can set the OTEL_EXPORTER_OTLP_ENDPOINT environment variable.

Here’s how:

1
observability_config = ObservabilityConfig(
2
  # alternatively, set the OTEL_SERVICE_NAME environment variable
3
  service_name = "example-service",
4
  # we recommend setting service_version to the latest deployed git SHA
5
  service_version = "example-sha"
6
)
7
8
plugin = ObservabilityPlugin(observability_config)

For a complete list of configuration options, read ObservabilityConfig.

You can configure options for the Ruby observability plugin when you initialize the SDK, or using environment variables.

Plugin configuration options

The plugin constructor accepts optional keyword arguments for configuration.

Here’s how:

1
plugin = LaunchDarklyObservability::Plugin.new(
2
  service_name: 'example-service',
3
  # we recommend setting service_version to the latest deployed git SHA
4
  service_version: 'example-sha'
5
)

For a complete list of configuration options, read Plugin Options.

Environment variables

The environment variables specify where to enable instrumentation:

• LAUNCHDARKLY_SDK_KEY provides the LaunchDarkly SDK key. This key is automatically extracted from the client during initialization.
• OTEL_EXPORTER_OTLP_ENDPOINT provides a custom OTLP endpoint.
• OTEL_SERVICE_NAME provides the service name, if not specified in plugin options.