What should you do if there are no requests showing for .NET services in Dynatrace?

Creating a custom service detection for .NET services is the appropriate action when no requests are showing for these services in Dynatrace. This is often necessary when the default service detection rules do not align with the specific setup or configuration of the .NET application. Custom service detection allows you to fine-tune the monitoring setup by defining what constitutes a service based on the unique endpoints, APIs, or behavior of your application.

By tailoring the service detection, you ensure that Dynatrace correctly identifies and monitors the activities of your .NET services, ultimately providing you with the necessary insights into performance, availability, and transaction data that may otherwise be missed. This proactive measure helps in maintaining robust observability for .NET applications, allowing for efficient troubleshooting and optimization.

In contrast, the other options may not directly address the root cause of the issue. While contacting support or checking network settings might be useful in certain situations, they do not specifically target the configuration problem at hand. Restarting the Dynatrace OneAgent might temporarily resolve the issue in some cases, but it is generally not a solution tailored towards configuring service detection logic specifically for .NET services.