fixes #24386 grpc service logging in console. (#24503)

* fixes #24386 grpc service logging in console.

* Update aspnetcore/tutorials/grpc/grpc-start.md

Co-authored-by: Rick Anderson <[email protected]>

Author: smandia

aspnetcore/tutorials/grpc/grpc-start.md

@@ -289,6 +289,15 @@ info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
       Request finished in 78.32260000000001ms 200 application/grpc
 ```
 
+Update the *appsettings.Development.json* file by adding the following lines:
+
+ ```
+ "Microsoft.AspNetCore.Hosting": "Information",
+ "Microsoft.AspNetCore.Routing.EndpointMiddleware": "Information"
+  ```
+
+
+
 > [!NOTE]
 > The code in this article requires the ASP.NET Core HTTPS development certificate to secure the gRPC service. If the .NET gRPC client fails with the message `The remote certificate is invalid according to the validation procedure.` or `The SSL connection could not be established.`, the development certificate isn't trusted. To fix this issue, see [Call a gRPC service with an untrusted/invalid certificate](xref:grpc/troubleshoot#call-a-grpc-service-with-an-untrustedinvalid-certificate).
 

aspnetcore/tutorials/grpc/grpc-start/sample6/GrpcGreeter/appsettings.Development.json

@@ -2,7 +2,9 @@
   "Logging": {
     "LogLevel": {
       "Default": "Information",
-      "Microsoft.AspNetCore": "Warning"
+      "Microsoft.AspNetCore": "Warning",
+      "Microsoft.AspNetCore.Hosting": "Information",
+      "Microsoft.AspNetCore.Routing.EndpointMiddleware": "Information"
     }
   }
 }