Menu

Driving Our Error Log to Zero (Without a Single Customer Complaint)
📰

Driving Our Error Log to Zero (Without a Single Customer Complaint)

DEV Community: elasticsearch·Elisha Sterngold·1 day ago
#BXetriy7
#devtoelasticsearch#devto#dev#error#work
Long article (1896 words) — no AI summary yet.
Reading 0:00
15s threshold

The Shipbook server's error log was full. Bright red, thousands of errors a day, some hours hitting a wall.

Not a single customer had complained.

That should already be the strange part. Most teams treat "no support tickets" as the only signal that matters. If users are not complaining, the system is fine. Move on. There is always something more urgent than cleaning up a log nobody is looking at.

I do not think that is true. And the month I just spent driving our error log down to zero — with no one asking me to, and ending up redesigning a chunk of our Elasticsearch architecture I had not planned on touching — is the reason I do not think that.

What a Crowded Error Log Actually Costs You

The first thing a noisy error log costs you is the ability to read it. When the page is red, every error is a red error.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.