Consider arbitrary monitor entries when evaluating server availability #4
Assignees
Labels
Comments
braveulysses
added a commit
that referenced
this issue
May 18, 2018
The status servlet now takes a 'monitor' extension argument, which provides criteria for evaluating availability based on an entry in the cn=monitor backend. This resolves #4.
braveulysses
added a commit
that referenced
this issue
May 18, 2018
Labeled product-specific configuration examples. This resolves #3.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should add an optional extension argument that allows the user to specify one or more names of cn=monitor entries that the status servlet will use to evaluate the availability of some service.
The name of a monitor entry probably won't be sufficient on its own. For example, it may be necessary to provide the name of an attribute plus a set of values that together indicate an available state. E.g.
--set "extension-argument:monitor=My Service:status:running,readyThe text was updated successfully, but these errors were encountered: