Is it possible to alert when Channels DVR goes down?

I've just had my DVR instance (running on Synology) hard crash twice over the course of a few days. Setting aside the cause, this circumstance has made me realize that I'm missing some sort of alert system with which to monitor when Channels DVR goes down. I'm sure the nature of this problem is being amplified by the fact that it's the holiday weekend and I haven't been watching Channels DVR as closely as I normally do. But it would be nice to know that I'll get a heads up if something goes wrong while I am looking the other way. Have any of you implemented a notification method when things go wrong with Channels DVR?

1 Like

If the DVR goes down, how can it notify you?

What you are describing sounds like a watchdog, which is essentially some computer program/service that monitors things; when certain conditions are met (like your DVR server no longer running), then it takes a proscribed action (such as restarting the service, or sending you an email). You should look into the documentation for the system that is running your server to see what options are available to you.

These types of alerts often work better from the client end. I don't know wha options you have here but typically when a client can no longer reach a server it can be configured to send you a notification.

I wasn't trying to suggest Channels notify me when it goes down. Rather, I was hoping to get some suggestions from others on how they are monitoring their DVR environment.

Channels, for example, could provide a method for querying the state of the service like many other Web-based software products do. Then, using a monitoring software like Statuspage one could simply query Channels and, if the DVR server doesn't respond, mark your DVR server offline and send a notification. Statuspage is probably overkill for something like this, but other examples of this kind is what I am seeking.

1 Like

They already do this. GET /dvr will give you your DVR server's status, and GET /dvr/events/subscribe is a running status of all DVR events. It's up to you to connect your tools to Channels' existing API endpoints.

You could use a free service like uptimerobot to monitor that the port is listening from the internet if you’re using remote access. I use this to notify me if my NAS goes offline (and also if my internet goes down).

Try this one, Its free and works for all my servers and internet monitoring.

Please submit diagnostics so we can figure out the root cause of the crash

Can you publish a how to for using Uptime Robot to monitor the port for dvrs using remote access? I can't figure out how to configure the IP/Host/Port for my setup

This is a self-hosted option I use on the Synology itself: https://github.com/louislam/uptime-kuma

Do you have a static IP? Or are you using a dynamic DNS to create that public IP?

@rbritton, would you mind helping a docker novice? I'm running the docker install command in a terminal on my Synology. I'm getting the following error. Any advise on what I'm doing wrong?

$ docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1

docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create?name=uptime-kuma": dial unix /var/run/docker.sock: connect: permission denied.

Thanks! --Chris

You will need to run the container creation command as root. On Synology you can do that via the CLI with sudo or creating a root-owned scheduled task in the Synology UI. For the latter, you just uncheck it so it doesn't automatically run and instead run it manually.

You can actually use the channels url that you connect remotely with. Example
URL https://12345678fdce.u.channelsdvr.net
Custom Port 8089

Got the Docker command to run but when I try to start the container it immediately stops and the log says I'm missing an environment variable TA_USERNAME. I'm not finding anything about this ENV variable in the Github.

Nevermind. I was able to get Kusma running by first creating the volume then starting the container using the steps in the advanced configuration section of the Github 🔧 How to Install · louislam/uptime-kuma Wiki · GitHub