[Kollner]

I am a Pingdom customer and I think the thing that could make me shift is an enhanced form of custom check - like what Pingdom has today but better.

In my setup I made a public service where external tools can retrieve some realtime stats like current number of users, queue lengths, number of jobs processing etc. Pingdom uses this service in different custom checks and it kinda works, but I can't use the stats or graphs for anything. Not all checks should be described in a status code and response time - a simple number would be great. Make graphs with that and allow users to set a threshold for when alerts should be sent.

Another thing missing is support for basic authentication.

As others have noted your front page is not really getting the message through.

[moomerman]

That is a very interesting use case. I was thinking about allowing users to create scriptable tests and then provide reporting around that, I think it could meet your requirements. I will add the basic authentication stuff.

[Kollner]

Scripting. I am not quite sure what you mean by that, but please make it simple. Pingdoms custom checks are simple because site owners just need to make an endpoint that prints out an xml snippet.

Fx. I have a service here: http://api.convert.io/realtime.svc/pingdom/queue-length which prints out: <pingdom_http_custom_check><status>OK</status><response_time>2</response_time></pingdom_http_custom_check>

How about you offer the same, but add a few more check types. One with the status/response time and another with just a single number.

<nimbu_http_custom_check><check_value>2</check_value></nimbu_http_custom_check>