feature request: local HTTP port monitoring

mikeysoft · 2019-06-15 11:11

Hi, firstly thanks for this great tool.

I use this to be able to remotely reboot a CCTV server (at home) that periodically crashes, and which is only fixable by restarting the machine (restarting the software doesn't work).

Currently I monitor for HTTP on a port using an external monitoring service (uptimedoctor), and when I get a notification that the port is no longer serving HTTP, I use shutter's web interface to reboot the machine (I'm often away from home so using Remote Desktop isn't so convenient - shutter web interface on my phone is).

Ideally, I'd like Shutter to have a HTTP monitoring (on a local port) function, so it could automatically reboot the machine!

Thanks
Mike

Last edited by mikeysoft (2019-06-15 11:12)

den4b · 2019-06-16 13:06

Yes, this feature can be added to Shutter.

Are you interested in checking that a particular port on a particular host is accepting connections, regardless of the of the higher level protocol like HTTP, FTP, etc?

Or you are interesting specifically in receiving a valid HTTP response, e.g. HTTP 200 OK status code?

mikeysoft · 2019-06-16 13:44

Hi, wow, that would be amazing!

Either - whichever you think would be most flexible and useful for other users...

I could've selected a TCP port check rather than an HTTP check at uptimedoctor, as I don't need to get a 200 status code - it's a simple alive/dead on the server behind the port that I'm after (accepting connections). I'm sure some people would find a 200..299 status code useful though!

Thanks again!

mikeysoft · 2020-11-06 16:18

Hi, I was just wondering if this is likely to be included in the near future? Thanks! :-)

den4b · 2020-11-08 10:37

mikeysoft wrote:

Hi, I was just wondering if this is likely to be included in the near future? Thanks! :-)

There was a minor set back in the implementation, which put it on the back log.

It should get finished at least by the end of the year

mikeysoft · 2020-11-09 00:19

den4b wrote:

mikeysoft wrote:
Hi, I was just wondering if this is likely to be included in the near future? Thanks! :-)
There was a minor set back in the implementation, which put it on the back log.
It should get finished at least by the end of the year

Thanks for the update :-)

den4b · 2020-12-29 20:13

The new Port event has been implemented.

It currently has two trigger types:

1. Port closed
2. Port open

It also has options for defining the polling frequency and the connect timeout.

The question is whether this even should have additional trigger types similar to those found in the Ping event, which would trigger when the state persists for a certain period of time, rather than instantaneously.

mikeysoft · 2021-03-07 17:09

Hi, thanks very much for doing that! This will be very useful for my situation.

On the question of "which would trigger when the state persists for a certain period of time, rather than instantaneously" - yes, I think this would offer even more flexibility and prevent potential looping of the event trigger.

Thanks again
Mike

den4b · 2022-03-19 11:18

This feature is available in Shutter 4.5.

Here is an updated screenshot:

den4b Forum

#1 2019-06-15 11:11

feature request: local HTTP port monitoring

#2 2019-06-16 13:06

Re: feature request: local HTTP port monitoring

#3 2019-06-16 13:44

Re: feature request: local HTTP port monitoring

#4 2020-11-06 16:18

Re: feature request: local HTTP port monitoring

#5 2020-11-08 10:37

Re: feature request: local HTTP port monitoring

#6 2020-11-09 00:19

Re: feature request: local HTTP port monitoring

#7 2020-12-29 20:13

Re: feature request: local HTTP port monitoring

#8 2021-03-07 17:09

Re: feature request: local HTTP port monitoring

#9 2022-03-19 11:18

Re: feature request: local HTTP port monitoring

Board footer