Skip to content
This repository has been archived by the owner on Oct 15, 2024. It is now read-only.

Warning state #4

Closed
mikehale opened this issue Jun 1, 2012 · 1 comment
Closed

Warning state #4

mikehale opened this issue Jun 1, 2012 · 1 comment

Comments

@mikehale
Copy link
Contributor

mikehale commented Jun 1, 2012

In nagios we currently have many checks with warning and critical thresholds. Currently umpire only provides a way to check for ok vs not-ok states. Does it make sense to provide a way to define warning thresholds and return a distinct http response code in that case?

@gorsuch
Copy link
Contributor

gorsuch commented Sep 28, 2012

I think we'll close this issue out for similar reasons to #5 - this tool is largely intended to be used with Pingdom, and that tool doesn't really deal with nuanced responses. Please re-open if you want to explore this further, though!

@gorsuch gorsuch closed this as completed Sep 28, 2012
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants