{"version":"2.1.271","anchor":"error-log-sink-now-reports-events-dropped-before-it-attached","canonical_anchor":"error-log-sink-now-reports-events-dropped-before-it-attached","heading":"Error log sink now caps and reports events dropped before it attached","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/error-log-sink-now-reports-events-dropped-before-it-attached","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Error log sink now caps and reports events dropped before it attached\n\nThe queue of events buffered before the error-log sink attaches is now capped, and startup reports how many were dropped\n\n**What**\n\nBefore the error-log sink (the component that receives and records error\/log events) attaches, events are held in a buffer. That buffer now has a maximum size instead of growing without bound, tracked with a `droppedBeforeSink` counter for anything that overflows it.\n\nThe startup message for the error-log sink now reports whether any events were logged before it attached, and if so, how many of them were dropped.\n\n**Why**\n\nThis prevents unbounded memory growth from events piling up before logging is ready, while still letting you see at startup if you lost any early events and how many.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}