Hi @Subin Joseph ,
Enable Application Logging and Web server logging which you can find out more about under Enable diagnostics logging for apps in Azure App Service. If your swagger isn't working, seeing what's going on with the request should help. If you used the SwaggerGen fluent API, then you can change your logging level in your dotnet core to perhaps see what happens with the route. You can enable logging, HTTP logging, and W3C logging for starters.
There aren't any special commands tied to Kudu that I'm aware of so I'm thinking it's one of the various dotnet commands you may be referring to. However, you can leverage the App Service Diagnostics tools as well to investigate what's going on.