-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🎨 Healtcheck diagnostics sensor is now optional #6327
🎨 Healtcheck diagnostics sensor is now optional #6327
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6327 +/- ##
=========================================
+ Coverage 84.5% 88.2% +3.6%
=========================================
Files 10 1499 +1489
Lines 214 62005 +61791
Branches 25 2065 +2040
=========================================
+ Hits 181 54725 +54544
- Misses 23 6964 +6941
- Partials 10 316 +306
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very nice thanks!
|
What do these changes do?
Logs from production revealed that the webserver was unnecessarily restarting due to delays in the Directorv2 service. These restarts did not resolve the issue and instead caused system degradation, leading to lost requests.
Based on an analysis of the production logs, we've determined that the health check based on diagnostics is no longer effective in addressing the problem. Therefore, this pull request introduces a new environment variable,
DIAGNOSTICS_HEALTHCHECK_ENABLED
, which allows toggling this health check functionality. By default, this variable is set toFalse
, effectively disabling the health check unless explicitly enabled.Related issue/s
How to test
Dev-ops checklist⚠️
DIAGNOSTICS_HEALTHCHECK_ENABLED