Sending logs to MS's LogAnalyzer about serilog-sinks-http

[FantasticFiasco]

The sink supports custom implementations of a HTTP client, which means that you should be able to set your headers as you please. The payload format is also fully configurable, which means whatever format LA expects, you should be able to provide with some configuration.

[justSteve]

Thanks for the quick reply - makes sense. So the HTTP client would be constructed during the page's lifetime as opposed to being placed in the config.

[FantasticFiasco]

Can you elaborate on what you mean by page? I most situations the logs are sent from the backend, but you seem to indicate that the logs will be sent from the frontend?

[justSteve]

Sorry for the confusion - a poor choice of words. I've been focused on an MVC app and spend most of my time logging within methods that produce 'pages'.

[FantasticFiasco]

Ok, it seems like server generated HTML seems to get some traction again, always nice to see!

Regardless of whether the HTML is generated on the server or the app is a SPA, I would advice to setup the logging once when the web server is started. Nicholas Blumhardt, the author of Serilog, has written an article describing how one would setup logging in .NET Core. Configuring Serilog.Sinks.Http should be done here, thus your custom implementation of a HTTP client should be defined here as well, and the lifetime of that HTTP client would match the lifetime of the web server, not the lifetime of the page rendering.

Does this answer your question?

[justSteve]

Many thanks for the details and the links. On the topic of configuring logging (and specifically to the DI perspective) you might find this interesting: https://stackify.com/net-core-loggerfactory-use-correctly/

…

On Fri, Nov 3, 2017 at 10:57 AM, Mattias Kindborg @FantasticFiasco < ***@***.***> wrote: Ok, it seems like server generated HTML seems to get some traction again, always nice to see! Regardless of whether the HTML is generated on the server or the app is a SPA, I would advice to setup the logging once when the web server is started. Nicholas Blumhardt, the author of Serilog, has written an article <https://nblumhardt.com/2017/08/use-serilog/> describing how one would setup logging in .NET Core. Configuring Serilog.Sinks.Http should be done here as well, thus your custom implementation of a HTTP client should be defined here as well, and the lifetime of that HTTP client would match the lifetime of the web server, not the lifetime of the page rendering. Does this answer your question? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#35 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGVUMwqIbj_PXVQntoWQDY0P5bkNP9yks5syzfPgaJpZM4QQeeP> .

[FantasticFiasco]

Nice, thanks! I will definitely read that one.

Hope your endeavour with Serilog turn out to be successful. If you are having any issues with this sink, please get in touch with me and we'll try to work it out.

Have a nice weekend!