Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Unhealthy status used for failure rather than the configured failure status #2225

Open
thompson-tomo opened this issue Jun 1, 2024 · 0 comments · May be fixed by #2226
Open

Unhealthy status used for failure rather than the configured failure status #2225

thompson-tomo opened this issue Jun 1, 2024 · 0 comments · May be fixed by #2226

Comments

@thompson-tomo
Copy link

Please, fill the following sections to help us fix the issue

What happened:
The Failure status of the health check is not being used but is instead always showing as unhealth

What you expected to happen:
The Failure status i configured to be used, is used

How to reproduce it (as minimally and precisely as possible):
Review code in linked PR

Anything else we need to know?:

Environment:

  • .NET Core version: Net 8
  • Healthchecks version: Latetst
thompson-tomo added a commit to thompson-tomo/AspNetCore.Diagnostics.HealthChecks that referenced this issue Jun 1, 2024
@thompson-tomo
Xabaril#2225 Use failure status rather than default of unhealthy
3719e8e
@thompson-tomo thompson-tomo linked a pull request Jun 1, 2024 that will close this issue
Open
4 tasks
thompson-tomo added a commit to thompson-tomo/AspNetCore.Diagnostics.HealthChecks that referenced this issue Jun 1, 2024
@thompson-tomo
Xabaril#2225 Use failure status rather than default of unhealthy
15d7695
thompson-tomo added a commit to thompson-tomo/AspNetCore.Diagnostics.HealthChecks that referenced this issue Jun 1, 2024
@thompson-tomo
Xabaril#2225 Use failure status rather than default of unhealthy
c8f615a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@thompson-tomo