Base solution for your next web application
Open Closed

Logging - Any decisions made etc.? #885


User avatar
0
theedge created

Hi Halil,

As I have to revisit logging with what we do I was wondering if you had any further thoughts on the direction ABP will take:

<a class="postlink" href="https://github.com/aspnetboilerplate/aspnetboilerplate/issues/771">https://github.com/aspnetboilerplate/as ... issues/771</a>

I realise this may be a roadmap issue that is still under consideration so if no decision has been made, then all good.


4 Answer(s)
  • User Avatar
    0
    hikalkan created
    Support Team

    Hi,

    Are you asking for Serilog? If so, you can already use it within ABP. Can you extend your question if it's not that.

  • User Avatar
    0
    theedge created

    Hi Halil,

    From my post in that thread:

    Having to review how we do logging across all our applications, including new ones based on ABP this discussion comes at a very timeous point for me.

    +1 LibLog or something similair. I think the separation of the IoC from the logging provider is definitely the way to go. The fact that LibLog provides reflection support for common loggers keeps things loosely coupled.

    I understand why @hikalkan chose the ILogger abstraction out of Castle Windsor and if that is how the library continues then so be it, but a logging interface outside of Castle would also be my preference.

    This is the same reason why @johnkattenhorn is suggesting an ITelemetry, namely being able to do telemetry using an interface that ABP controls and that contributors can write providers for.

    My question is whether ABP will remain using Castle.ILogger or whether it will provide its own logging abstraction to address some of the requirements and concerns raised in the GitHub issue. Because at present we are also tied to a specific 1.x version of Log4Net because of the Castle dependency.

  • User Avatar
    0
    hikalkan created
    Support Team

    I want that but it's priority is not high. We can live with that a while more :)

    Castle's ILogger is already implemented by a few logging library. So, if I abstract logging myself, I also should implement them too, and currently I don't know all.

  • User Avatar
    0
    theedge created

    Hi Halil,

    Fair enough.... Maybe LibLog will be the ultimate way to go.... I have to look into this for my stuff so if anything good comes of that I will let you have the code.