Troubleshooting .NET tracing

Select the appropriate troubleshooting guide based on where your .NET application is deployed:

• Troubleshooting .NET tracing on AWS Lambda

  Troubleshoot .NET tracing issues for serverless applications on AWS Lambda, including missing traces, Lambda layer configuration problems, cold start issues, and timeout errors.

• Troubleshooting .NET tracing on Azure

  Troubleshoot .NET tracing issues for applications hosted on Azure platforms (App Services, Container Apps), including missing traces, site extension problems, environment variable configuration, and agent connectivity issues.

• Troubleshooting .NET tracing on Docker

  Troubleshoot .NET tracing issues on Docker containers, including missing traces, container networking issues, environment variable configuration, and connectivity to the Instana agent.

• Troubleshooting .NET tracing on IIS

  Troubleshoot .NET tracing issues for applications hosted on Internet Information Services (IIS), including application pool configuration, missing traces, and IIS-specific environment variable setup.

• Troubleshooting .NET tracing on Kubernetes

  Troubleshoot .NET tracing issues on Kubernetes, including problems with the AutoTrace webhook, missing traces, application crashes, and tracer attachment issues.

• Troubleshooting .NET tracing on Linux or Alpine Linux

  Troubleshoot .NET tracing issues on Linux systems, including missing traces, application crashes, agent detection problems, and high CPU usage.

• Troubleshooting .NET tracing on Windows

  Troubleshoot .NET tracing issues on Windows systems, including missing traces, application failures, agent detection problems, and high CPU usage for InstanaPCP or applications.

• Troubleshooting .NET tracing on z/OS

  Troubleshoot .NET tracing issues on z/OS systems with manual instrumentation using Instana SDK or OpenTelemetry SDK, including missing traces, application failures, and SDK configuration issues.