Server response feature

Some of our customers have asked for a new feature for testing servers on different levels, if they are active or not. A feature suited perfectly for our build-in three-state template.

Ping, port, API, service or whatever

Reporting allows for check on ping, port, network availability, service status, API or whatever the server has setup for testing its status. In either case, the response will be transformed to one of the 3 possible values in the three-state template:

• True = Everything is alright
• False = There is a problem
• Neutral = No response yet

The "Neutral" value is used only for when the server has not been polled for a status yet, typically when you start monitoring it.

Below is an example of how a "positive" response is shown in the three-state template display. The talkback will contain the timestamp of when the response was received.

Incidents

The three-state already contains the ability to report an incident to the user, so we needed to do no coding for that.

Below is an example of how a "negative" response is shown. In this event, the talkback can contain further information about any problems with the server, if the server returns this in the response.

So what's next?

Customers really like the three-state implementation. And the fact that they can customize the use of it in an easy way.

Above example took less than 1 hour to implement in the monitoring cycle. So next move will most likely be our customers coming up with new things, they want to use the three-state implementation for.