As an example, the section header/label for service check thresholds is a hard-coded "THRESHOLDS" text string.
In the strictest sense, thresholds should be crossed before a service state changes, not just met.
In some cases, you may not want to focus on a threshold being crossed, but rather a specific external status being reached.
For example, if you're monitoring a remote web server you may wish to indicate in Long Service Output that receiving a 5xx server response code will result in a CRITICAL service check state, not crossing a threshold of a 5xx server response code.
To support those use cases (and many others), each section header/label should allow client code to specify what text values to use.
As an example, the section header/label for service check thresholds is a hard-coded "THRESHOLDS" text string.
In the strictest sense, thresholds should be crossed before a service state changes, not just met.
In some cases, you may not want to focus on a threshold being crossed, but rather a specific external status being reached.
For example, if you're monitoring a remote web server you may wish to indicate in
Long Service Outputthat receiving a 5xx server response code will result in a CRITICAL service check state, not crossing a threshold of a 5xx server response code.To support those use cases (and many others), each section header/label should allow client code to specify what text values to use.