Settings: OpenTelemetry

Enable OpenTelemetry support

Use this option to enable or disable the whole OpenTelemetry functionality.

Launch OpenTelemetry host on startup

In most cases, you want to have the OpenTelemetry service running before you start the target application, that's why by default the service is started automatically when you start Rider.

To start and stop the service, select the OpenTelemetry node in the Services window and use the corresponding buttons on the toolbar.

Activate the Services tool window for run configuration

When this checkbox is selected, launching a supported run configuration will activate the Services window instead of Run window or Debug window

Overwrite OpenTelemetry environment variables

For .NET applications launched from the IDE, the OTEL_EXPORTER_OTLP_ENDPOINT environment variable is set automatically. This means that if an application is configured with OpenTelemetry, has the OTLP exporter added, but the endpoint is not explicitly set in the code, the application will automatically start sending data to Rider OTLP server. You can disable auto-assigning of the environment variable by clearing this checkbox.

Use fixed OTLP server port

Use this checkbox to start the OpenTelemetry server on the specified port. You may need to use a fixed port to route the log streams from apps started locally outside the IDE.

Use fixed MCP server port

Allow automatic instrumentation

Use this checkbox to enable or disable auto-instrumentation of the ASP.NET Core apps launched from the IDE.