#serilog — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #serilog, aggregated by home.social.
-
Логирование с Serilog: как повысить отказоустойчивость и скорость
Когда логов становится слишком много, а сеть или облачный приёмник начинает тормозить, даже самый надёжный логгер может превратиться в источник проблем. Наша команда столкнулась с тем, что память забивалась логами, и это приводило к OutOfMemoryException и аварийному закрытию приложений. В статье разбираю, как устроен процесс логирования в Serilog, почему асинхронная отправка логов не всегда безопасна, как протестировать систему на устойчивость к задержкам и какие настройки и архитектурные приёмы помогут сохранить стабильность под нагрузкой.
-
Логирование с Serilog: как повысить отказоустойчивость и скорость
Когда логов становится слишком много, а сеть или облачный приёмник начинает тормозить, даже самый надёжный логгер может превратиться в источник проблем. Наша команда столкнулась с тем, что память забивалась логами, и это приводило к OutOfMemoryException и аварийному закрытию приложений. В статье разбираю, как устроен процесс логирования в Serilog, почему асинхронная отправка логов не всегда безопасна, как протестировать систему на устойчивость к задержкам и какие настройки и архитектурные приёмы помогут сохранить стабильность под нагрузкой.
-
Логирование с Serilog: как повысить отказоустойчивость и скорость
Когда логов становится слишком много, а сеть или облачный приёмник начинает тормозить, даже самый надёжный логгер может превратиться в источник проблем. Наша команда столкнулась с тем, что память забивалась логами, и это приводило к OutOfMemoryException и аварийному закрытию приложений. В статье разбираю, как устроен процесс логирования в Serilog, почему асинхронная отправка логов не всегда безопасна, как протестировать систему на устойчивость к задержкам и какие настройки и архитектурные приёмы помогут сохранить стабильность под нагрузкой.
-
Логирование с Serilog: как повысить отказоустойчивость и скорость
Когда логов становится слишком много, а сеть или облачный приёмник начинает тормозить, даже самый надёжный логгер может превратиться в источник проблем. Наша команда столкнулась с тем, что память забивалась логами, и это приводило к OutOfMemoryException и аварийному закрытию приложений. В статье разбираю, как устроен процесс логирования в Serilog, почему асинхронная отправка логов не всегда безопасна, как протестировать систему на устойчивость к задержкам и какие настройки и архитектурные приёмы помогут сохранить стабильность под нагрузкой.
-
@nblumhardt Look, #JetBrainsRider learned a new #OpenTelemetry trick and it works pretty well with #SeriLog
I wish there would be a similar @seq plugin for Rider that would just spin up a local dev Seq instance for me and sow the logs directly in the IDE. -
@nblumhardt Look, #JetBrainsRider learned a new #OpenTelemetry trick and it works pretty well with #SeriLog
I wish there would be a similar @seq plugin for Rider that would just spin up a local dev Seq instance for me and sow the logs directly in the IDE. -
@nblumhardt Look, #JetBrainsRider learned a new #OpenTelemetry trick and it works pretty well with #SeriLog
I wish there would be a similar @seq plugin for Rider that would just spin up a local dev Seq instance for me and sow the logs directly in the IDE. -
@nblumhardt Look, #JetBrainsRider learned a new #OpenTelemetry trick and it works pretty well with #SeriLog
I wish there would be a similar @seq plugin for Rider that would just spin up a local dev Seq instance for me and sow the logs directly in the IDE. -
@nblumhardt Look, #JetBrainsRider learned a new #OpenTelemetry trick and it works pretty well with #SeriLog
I wish there would be a similar @seq plugin for Rider that would just spin up a local dev Seq instance for me and sow the logs directly in the IDE. -
Blogged: .NET Azure Functions in isolated-worker model, Serilog and App Insights.
https://david.gardiner.net.au/2025/02/functions-serilog-appinsights.html
-
Blogged: .NET Azure Functions in isolated-worker model, Serilog and App Insights.
https://david.gardiner.net.au/2025/02/functions-serilog-appinsights.html
-
Blogged: .NET Azure Functions in isolated-worker model, Serilog and App Insights.
https://david.gardiner.net.au/2025/02/functions-serilog-appinsights.html
-
Blogged: .NET Azure Functions in isolated-worker model, Serilog and App Insights.
https://david.gardiner.net.au/2025/02/functions-serilog-appinsights.html
-
Blogged: .NET Azure Functions in isolated-worker model, Serilog and App Insights.
https://david.gardiner.net.au/2025/02/functions-serilog-appinsights.html
-
@nblumhardt I am using Microsoft.Extension.Logging and System.Diagnostics.Activity for logging and #Serilog just for the sinks. Now I would like to log to #Seq (`WriteTo.Seq()`) and also enable traces and spans. Is there a place where I can see/learn how to do this?
-
@nblumhardt I am using Microsoft.Extension.Logging and System.Diagnostics.Activity for logging and #Serilog just for the sinks. Now I would like to log to #Seq (`WriteTo.Seq()`) and also enable traces and spans. Is there a place where I can see/learn how to do this?
-
@nblumhardt I am using Microsoft.Extension.Logging and System.Diagnostics.Activity for logging and #Serilog just for the sinks. Now I would like to log to #Seq (`WriteTo.Seq()`) and also enable traces and spans. Is there a place where I can see/learn how to do this?
-
@nblumhardt I am using Microsoft.Extension.Logging and System.Diagnostics.Activity for logging and #Serilog just for the sinks. Now I would like to log to #Seq (`WriteTo.Seq()`) and also enable traces and spans. Is there a place where I can see/learn how to do this?
-
@nblumhardt I am using Microsoft.Extension.Logging and System.Diagnostics.Activity for logging and #Serilog just for the sinks. Now I would like to log to #Seq (`WriteTo.Seq()`) and also enable traces and spans. Is there a place where I can see/learn how to do this?
-
Quick blog article, On Logging; just a quick post about choosing logging strageies in different environments (and
some discussion on WHY you log differently in different circumstances) https://www.mostlylucid.net/blog/onlogging
#aspnetcore #serilog -
Quick blog article, On Logging; just a quick post about choosing logging strageies in different environments (and
some discussion on WHY you log differently in different circumstances) https://www.mostlylucid.net/blog/onlogging
#aspnetcore #serilog -
Quick blog article, On Logging; just a quick post about choosing logging strageies in different environments (and
some discussion on WHY you log differently in different circumstances) https://www.mostlylucid.net/blog/onlogging
#aspnetcore #serilog -
Quick blog article, On Logging; just a quick post about choosing logging strageies in different environments (and
some discussion on WHY you log differently in different circumstances) https://www.mostlylucid.net/blog/onlogging
#aspnetcore #serilog -
Quick blog article, On Logging; just a quick post about choosing logging strageies in different environments (and
some discussion on WHY you log differently in different circumstances) https://www.mostlylucid.net/blog/onlogging
#aspnetcore #serilog -
Following yesterday's write-up of #Serilog 4.1 fallback sinks, here's a tiny test harness you can use to explore the new batch retry algorithm, along with an example run: https://nblumhardt.com/2024/10/retry-time-limit/
-
Following yesterday's write-up of #Serilog 4.1 fallback sinks, here's a tiny test harness you can use to explore the new batch retry algorithm, along with an example run: https://nblumhardt.com/2024/10/retry-time-limit/
-
Following yesterday's write-up of #Serilog 4.1 fallback sinks, here's a tiny test harness you can use to explore the new batch retry algorithm, along with an example run: https://nblumhardt.com/2024/10/retry-time-limit/
-
Following yesterday's write-up of #Serilog 4.1 fallback sinks, here's a tiny test harness you can use to explore the new batch retry algorithm, along with an example run: https://nblumhardt.com/2024/10/retry-time-limit/
-
Following yesterday's write-up of #Serilog 4.1 fallback sinks, here's a tiny test harness you can use to explore the new batch retry algorithm, along with an example run: https://nblumhardt.com/2024/10/retry-time-limit/
-
Serilog fallback sinks and failure listeners: https://nblumhardt.com/2024/10/fallback-logging/ #serilog
-
Serilog fallback sinks and failure listeners: https://nblumhardt.com/2024/10/fallback-logging/ #serilog
-
Serilog fallback sinks and failure listeners: https://nblumhardt.com/2024/10/fallback-logging/ #serilog
-
Serilog fallback sinks and failure listeners: https://nblumhardt.com/2024/10/fallback-logging/ #serilog
-
Serilog fallback sinks and failure listeners: https://nblumhardt.com/2024/10/fallback-logging/ #serilog
-
Today's second blog post. Seq for ASP.NET Logging - Tracing with SerilogTracing
https://www.mostlylucid.net/blog/selfhostingseqpt2
#seq #serilog #aspnetcore -
Today's second blog post. Seq for ASP.NET Logging - Tracing with SerilogTracing
https://www.mostlylucid.net/blog/selfhostingseqpt2
#seq #serilog #aspnetcore -
Today's second blog post. Seq for ASP.NET Logging - Tracing with SerilogTracing
https://www.mostlylucid.net/blog/selfhostingseqpt2
#seq #serilog #aspnetcore -
Today's second blog post. Seq for ASP.NET Logging - Tracing with SerilogTracing
https://www.mostlylucid.net/blog/selfhostingseqpt2
#seq #serilog #aspnetcore -
Today's second blog post. Seq for ASP.NET Logging - Tracing with SerilogTracing
https://www.mostlylucid.net/blog/selfhostingseqpt2
#seq #serilog #aspnetcore -
My org has some #dotnet logging going to a "not quite ELK" Elasticsearch logging stack. We use #Serilog, but we're still on ES 7.17.x which means we're stuck between deprecated index templates and the newer composable ones that don't work with the ES Serilog sink.
I've always struggled with getting the lifecycles set up correctly for rollover, so I set up a demo project to radically speed up the feedback cycle from weeks to minutes. Hope this helps someone else.
-
My org has some #dotnet logging going to a "not quite ELK" Elasticsearch logging stack. We use #Serilog, but we're still on ES 7.17.x which means we're stuck between deprecated index templates and the newer composable ones that don't work with the ES Serilog sink.
I've always struggled with getting the lifecycles set up correctly for rollover, so I set up a demo project to radically speed up the feedback cycle from weeks to minutes. Hope this helps someone else.
-
My org has some #dotnet logging going to a "not quite ELK" Elasticsearch logging stack. We use #Serilog, but we're still on ES 7.17.x which means we're stuck between deprecated index templates and the newer composable ones that don't work with the ES Serilog sink.
I've always struggled with getting the lifecycles set up correctly for rollover, so I set up a demo project to radically speed up the feedback cycle from weeks to minutes. Hope this helps someone else.
-
My org has some #dotnet logging going to a "not quite ELK" Elasticsearch logging stack. We use #Serilog, but we're still on ES 7.17.x which means we're stuck between deprecated index templates and the newer composable ones that don't work with the ES Serilog sink.
I've always struggled with getting the lifecycles set up correctly for rollover, so I set up a demo project to radically speed up the feedback cycle from weeks to minutes. Hope this helps someone else.
-
My org has some #dotnet logging going to a "not quite ELK" Elasticsearch logging stack. We use #Serilog, but we're still on ES 7.17.x which means we're stuck between deprecated index templates and the newer composable ones that don't work with the ES Serilog sink.
I've always struggled with getting the lifecycles set up correctly for rollover, so I set up a demo project to radically speed up the feedback cycle from weeks to minutes. Hope this helps someone else.
-
TBH, going from #dotnet #serilog with Serilog.Exceptions to OTEL felt like step a backwards in one respect: recording structured exceptions.
.NET exceptions are structured data: public fields have names and typed value, and can be recorded as such.
.NET typed exceptions have custom data: Put the orderId in the orderId prop, not in message text.
.NET exceptions are recursively structured due to inner ex.
Embracing this in telemetry leads to better exception design