locked
SignalR server side logging doesn't work RRS feed

  • Question

  • User-1946684416 posted

    Try to follow the instructions on 

    Enabling SignalR Tracing page for server side logging. And added everything in our web.config

    Nothing shows up on the logging path.

    Also, as stackover flow suggested,  I tried to add the Owin.Diagnosis from Nuget, and add the app.UseErrorPage(); at front of the app.MapSignalR() method.

    It doesn't work. The differences is that the post suggested add at the front of the app.mapHub. We don't use it. So, we use app.MapSignalR.

    Any hints or anything I go missing?

    The whole signalR is working, just the server side logging is not there.

    Thursday, October 8, 2015 7:23 PM

All replies

  • User61956409 posted

    Hi zmen001,

    Welcome to ASP.NET forum.

    Do you refer to this link?

    http://www.asp.net/signalr/overview/testing-and-debugging/enabling-signalr-tracing#server

    and this link may be helpful for you to trace on the server side.

    https://github.com/SignalR/SignalR/wiki/Tracing-on-the-server-side

    Best Regards,

    Fei Han

    Thursday, October 8, 2015 9:47 PM
  • User-1946684416 posted

    Thanks for your posting.

    And that's what I did already for the first link.

    I also tried to follow the second link as well. The only differences is that on the IIS, when I clicked on the "Failed Requests Tracing Rules", I only got one enable checkbox with a path.

    I did enable that checkbox and keep eyes on that path.

    Once start my site again, nothing happens as well.

    What I just tired again was using the process monitor to see what's happening.

    It tries to find my root directory/signalr/connect/web.config. I added one web.config with signalR related lines only in that web.config.

    Restart my IIS, it still doesn't work.

    Any more hints?

    Thanks,

    Thursday, October 8, 2015 11:55 PM