From 2cd5b3cb498ca5511b0120b4a007512837e1558f Mon Sep 17 00:00:00 2001
From: KernelDeimos <eric.alex.dube@gmail.com>
Date: Thu, 22 May 2025 15:18:36 -0400
Subject: [PATCH] fix: prevent health check from surpressing traces

Stack traces aren't logged when a health check failure occurs. This was
caused by interfacing with AlarmService directly instead of using the
error service.
---
 src/backend/src/modules/core/ServerHealthService.js | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/backend/src/modules/core/ServerHealthService.js b/src/backend/src/modules/core/ServerHealthService.js
index 69d5ace5..efa0be16 100644
--- a/src/backend/src/modules/core/ServerHealthService.js
+++ b/src/backend/src/modules/core/ServerHealthService.js
@@ -172,6 +172,8 @@ class ServerHealthService extends BaseService {
                         { error: err }
                     );
                     check_failures.push({ name });
+                    
+                    this.log.error(`Error for healthcheck fail on ${name}: ` + e.stack);
 
                     // Run the on_fail handlers
                     for ( const fn of chainable.on_fail_ ) {