Cut over the .NET agent

Switch a supported .NET combined agent from dual-signal mode to Splunk-only mode during migration cutover.

Overview

Use this procedure to switch a supported .NET combined agent from dual-signal mode to Splunk-only mode.

Prerequisites

Confirm that:

  • The application uses a .NET combined-agent version and deployment model that supports Splunk-only mode.
  • The application passed Phase 5 validation.
  • Keep the last verified dual-signal package, configuration, and deployment files available for rollback.
  • Record the OpenTelemetry endpoint, protocol, service name, namespace, deployment environment, and other approved resource attributes.
  • Confirm the cutover window, representative traffic, and rollback owner.

Review the .NET combined-agent compatibility requirements for the installed release. If the application does not support the .NET combined agent, do not use this procedure. Use the independent OpenTelemetry instrumentation path approved for the migration wave.

Switch to Splunk-only mode

  1. Record the current deployment configuration, including AGENT_DEPLOYMENT_MODE, the OpenTelemetry route, and the service-identity settings.
  2. Change AGENT_DEPLOYMENT_MODE from dual to otel.
  3. Keep the verified OpenTelemetry endpoint, protocol, service name, namespace, deployment environment, and other approved resource attributes unchanged.
  4. Do not remove or change Splunk AppDynamics Controller settings unless the documentation for the installed .NET combined-agent release explicitly requires that change.
  5. Restart or redeploy the application through the approved change process.
  6. Generate representative traffic.
  7. Complete the checks in Validate and Stabilize After Cutover.

For deployment-model details and rollback guidance, see Cut over or roll back.

If validation fails or a rollback trigger occurs, use Roll Back the Cutover.