Copied to clipboard

Flag this post as spam?

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


  • jake williamson 207 posts 872 karma points
    Feb 21, 2020 @ 00:52
    jake williamson
    0

    implementing a log viewer in v8 (documentation is out of date!)

    hey out there,

    we've added a serilog sink to a site so it can log to azure table storage:

    https://github.com/serilog/serilog-sinks-azuretablestorage

    it works and the logs are being written to an azure blob storage table, however we need to be able to see the logs in the backoffice...

    according to the documentation this is possible:

    https://our.umbraco.com/documentation/Getting-Started/Backoffice/LogViewer/

    (no idea why this is in the getting started section, it feels a bit advanced?!)

    the problem we're facing at the moment is that the code supplied in the documentation doesn't work with what's in the current v8 core...

    looking at the LogViewerSourceBase class the two GetLogs methods are either protected or not virtual meaning they can't be overridden...

    this is a bit of a major problem! has anyone figured out how to do this?!

    cheers,

    jake

  • Sam Gooch 24 posts 116 karma points
    Dec 04, 2020 @ 14:13
    Sam Gooch
    0

    Hi Jake

    I don't suppose you got this sorted? I'm facing the same issue.

    Thanks, Sam

  • jake williamson 207 posts 872 karma points
    Dec 09, 2020 @ 01:07
    jake williamson
    0

    hey sam,

    you're not watching me are you?! i've been doing a load of stuff to do with logging over the last couple of days including getting using sql server for log storage!

    re getting the log viewer hooked up in the backoffice take a look at this post:

    https://our.umbraco.com/forum/umbraco-8/97245-umbraco-8-serilog-and-serilog-sinks#comment-321674

    the major hangup that comes with the above set up is that the paging is inefficient making storing logs in azure table storage virtually unusable...

    the issue is that the code gets every log entry and then uses skip/take in a for loop - which is truly terrible as on the overview screen it gets every log entry for all the stats (pie graph etc).

    you can do paging with azure table storage but it requires storing and passing a token back and forth which isn't possible with the umbraco core code...

    so the big thing we've been working on is getting the sql server side of things working as then we can use a stored procedure with efficient paging to get the logs and fingers crossed that'll mean we can store as much logging info as we want without the whole section falling over in the backoffice...

    it's very much work in progress but if we get it nailed, i'll post back here ;)

Please Sign in or register to post replies

Write your reply to:

Draft