https://v1-18.docs.dapr.io/developing-applications/sdks/dotnet/dotnet-troubleshooting/Recent content in How to troubleshoot and debug with the Dapr .NET SDK on Dapr DocsHugoenhttps://v1-18.docs.dapr.io/developing-applications/sdks/dotnet/dotnet-troubleshooting/dotnet-troubleshooting-pubsub/Mon, 01 Jan 0001 00:00:00 +0000https://v1-18.docs.dapr.io/developing-applications/sdks/dotnet/dotnet-troubleshooting/dotnet-troubleshooting-pubsub/<h1 id="troubleshooting-pubsub">Troubleshooting Pub/Sub</h1> <p>The most common problem with pub/sub is that the pub/sub endpoint in your application is not being called.</p> <p>There are a few layers to this problem with different solutions:</p> <ul> <li>The application is not receiving any traffic from Dapr</li> <li>The application is not registering pub/sub endpoints with Dapr</li> <li>The pub/sub endpoints are registered with Dapr, but the request is not reaching the desired endpoint</li> </ul> <h2 id="step-1-turn-up-the-logs">Step 1: Turn up the logs</h2> <p><strong>This is important. Future steps will depend on your ability to see logging output. ASP.NET Core logs almost nothing with the default log settings, so you will need to change it.</strong></p>