Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Richard Waite 9 posts 77 karma points
    Jun 11, 2021 @ 14:16
    Richard Waite
    0

    View trace logs with flexible load balancing

    I am using umbraco 7.15.6, with a load balanced setup on azure - one webapp for the backoffice, and one for front end requests.

    In the trace logs in backoffice, I can only see the logs for the backoffice server. To view the front end logs I have to use the App Service editor or Kudu console to connect to view the logfile.

    Is there any way that I can view the trace logs from the front end web app on the master backoffice web app?

    Thanks!

  • Dan Diplo 1554 posts 6205 karma points MVP 5x c-trib
    Jun 11, 2021 @ 14:22
    Dan Diplo
    0

    Sorry, I don't believe that is possible. The logs are generated as physical files on the server on a per-server basis. So the front-end server will generate logs and the backoffice server will generate logs - but these will be on different servers. One doesn't have any access to the other.

    I guess you might be able to install the log viewer on the front-end server, if you can access the backoffice for that?

  • Richard Waite 9 posts 77 karma points
    Jun 11, 2021 @ 14:47
    Richard Waite
    0

    Thanks for the quick reply! I want to avoid accessing the backoffice from the front end server if possible.

    I'm wondering if I could configure log4net to store the logs in a central location, such as azure blob storage, then the trace log viewer would be able to load them from there for both servers?

  • Dan Diplo 1554 posts 6205 karma points MVP 5x c-trib
    Jun 11, 2021 @ 16:18
    Dan Diplo
    0

    Not that I'm aware of, I'm afraid. I don't think you can move the log files and, even if you did, I don't think my package would be aware of the new location. It might be possible in newer versions of Umbraco, but not in 7. Sorry!

Please Sign in or register to post replies

Write your reply to:

Draft