DEV Community

Cover image for Building a System Health Tool That Actually Explains What's Wrong (Not Just "Error Code 0x0000004E")
Lohith Reddy
Lohith Reddy

Posted on

Building a System Health Tool That Actually Explains What's Wrong (Not Just "Error Code 0x0000004E")

#opensource #devops #systems #productivity

The Problem: Error Messages Are Useless 

Battery Health: 37715 Wh capacity detected
System Error: ACPI_BIOS_ERROR (0x0000004E) 
DCOM Event ID 10016
Python packages: 16 updates available
Enter fullscreen mode Exit fullscreen mode

Cool. What does any of that mean?

The Solution: Conversational System Intelligence

I built DivLens to translate system status into actionable insights.

![System health check screenshot]

What It Does Differently

Traditional monitoring tool:

Battery Capacity: 37,715 mWh
Design Capacity: 52,514 mWh
Cycle Count: 247
Enter fullscreen mode Exit fullscreen mode

DivLens:

⚠️ Battery Health: Your battery's maximum capacity has decreased 
to 37,715 Wh from a design capacity of 52,514 Wh. This means 
you're getting less battery life than when it was new.

[Check Battery Health Details]
Enter fullscreen mode Exit fullscreen mode

See the difference? It explains what the numbers mean for YOU.

Real-World Example

User asks: "Is there any issue in my system?"

DivLens responds:

⚠️ NEEDS ATTENTION

  1. Battery Health - Degraded to 72% (implications explained)
  2. System Errors - BIOS issues that could cause instability
  3. Outdated Packages - 16 Python packages (security risks noted)

✅ LOOKING GOOD

  1. CPU - Running at normal speed (2.61 GHz)
  2. RAM - 16GB available (sufficient for most tasks)
  3. Graphics - RTX 3050 ready for intensive work

Plus suggested follow-up questions:

  • "How can I improve my battery life?"
  • "What do those system errors mean?"
  • "How do I update my Python packages?"

Technical Approach

Data Collection:

  • Read system files (battery stats, process info, package managers)
  • Parse system logs (Windows Event Viewer, syslog, etc.)
  • Query hardware info (CPU, RAM, GPU specs)

AI Translation:

  • Context-aware explanations (not just generic definitions)
  • Severity assessment (is this critical or just FYI?)
  • Actionable recommendations (what should the user do?)

Privacy-First:

  • All analysis local (no cloud processing required)
  • No telemetry or tracking
  • Open about what data is accessed

Why This Matters for Developers

We're good at debugging code. We're bad at debugging our own systems.

How much time have you wasted:

  • Googling "DCOM Event ID 10016"
  • Cross-referencing outdated Stack Overflow answers
  • Checking if 16GB RAM is enough for [project]
  • Diagnosing why your laptop is suddenly slow

DivLens gives you that time back.

Try It

Free tier available. Works on Windows, macOS, Linux.

[https://www.divlens.in]

Open to feedback, especially from sysadmins and DevOps folks who deal with
system diagnostics daily.

Top comments (0)