Great video, thank you for sharing. How did you get the maintenance tool menu and network menu on the right side of the screen? I only have the Device, Presence and Event options.
Can you maybe give me a timestamp as to where in the video as it is two different apps and lots of different views? Both of mine are fairly standard I think, and both hosted in Docker containers.
@@GadgeteerZA Danie thank you for your quick response. Here are the timestamps. I'm running my Pi.Alert on a Raspberry Pi also. Timestamp 13:08 - Shows Device, Presence, Events, Network, Maintenance and Help/FAQ 19:19 - Shows information under the Network menu option 19:31 - Shows information under the Maintenance menu option 20:27 - Shows information under the Help/FAQ menu option. My setup of Pi.Alert doesn't have the Network, Maintenance and Help/Faq menus. Thank you.
OK sorry about that confusion as I thought you meant the right side of the screen. OK very interesting as it seems those functions are not in the original Pi.Alert with Raspberry install at github.com/pucherot/Pi.Alert. Someone has logged an issue at github.com/pucherot/Pi.Alert/pull/186 to contribute that additional info to the original. So others, like the Docker version I'm using are actually forks with improvements. I got the Docker version instructions from registry.hub.docker.com/r/jokobsk/pi.alert. So you probably have two choices: 1. Wait and see if updates do bring that functionality. 2. Do a simple install of Docker on the Pi, and then install the Docker version I'm using and try it. You can leave your original Pi.Alert install on the Pi, just to try this one out, and then decide which you want to stick with.
awesome, Danie, do you know if it is possible set up notifications only, for example, devices marked like Favourites or added in group "always on"? I'd like use this in enterprise enviroment but I receive tons of emails with new, connected or disconnected devices, all of them. thanks
I think it can be achieved as there are two ways to configure alert notifications: 1. Settings/Notify On: Specifies which events trigger notifications. Remove the event type(s) you don't want to get notified on. This setting overrides device-specific settings in the UI. Typically, categories appear such as Internet (WAN IP changes), new_devices, down_devices, events, ports, etc. Can't see that you can actually add new options here (maybe from the config file?). 2. Per device you can enable or disable all events, alert down, new device (you disable new device alert for a device you have identified after it was alerted as a new identified device. 'Alert down' option would be ticked for an always -on device you want an alert for. So you could come right with the above tweaks, or by sorting the view order on the GUI, but another option is to otherwise log an issue request at their project at github.com/pucherot/Pi.Alert/issues. It may be worth also just installing it and testing it with just a few devices.
@@GadgeteerZA thanks for the advice man, it works better now I just had to deselect of the other devices (scan cycle -> don't scan, alert all events -> un marked, new device -> unmarked) and I left only the more important devices and I get only notification of these ones. For now works very well for me, but I would like that the App had an option to less time of scan cycle, because 5 minutes is a long time and probably I'll notice when the devices down after all users do. thank again
@@ginsanhertz9788 Glad you came right. Yes it is open source so may be possible to alter that scan time in the code even. I also noted though that the Docker version is slightly different from the normal install version, so you may want to dig a bit further into that too.
Hi Danie, Greetings from Grand Duchy of Luxembourg .. ;-) Thanks for this video ... I have Pi.Alert for few weeks up and running on my Synology as a docker container .. Works fine .. ;-) I saw in your video that you do use some container "Ressource Stats" to monitor per container on a graphical view, the consumed resources .. What is this tool you do use .. I was not able to find out ... Thanks in advance ... Luc
Hi there Luc, and greetings to you from a cold overcast Cape Town. The only thing coming to mind right now on containers was the Glances service that also runs in a container. Can't remember if I did a video about it on its own. That shows what containers are running and how much resources they are using. EDIT: I see here was a mention about Glances but it was really displaying widgets in the Dashy app, that drew data from Glances - ruclips.net/video/JW2YJp34SQw/видео.html. Looks like I must still do a video about Glances.
@@GadgeteerZA Hi Daniel. Thanks for your response. I use both! Glances and Dashy .. and the widget connecting both .... ;-) .... I will take a closer look, to find out, where I can see the same information as you do display in your video ..... Because this is a valuable info, to see visually what every single container is “consuming” .... Thanks so far .... and greetings back to Cape Town ... (“only” 13.000 km physically, but a few milliseconds digitally .distant 😉....
Not that I can recall. It is intended to run in a Raspberry Pi or in a Linux container mostly as it runs 24/7. It is perfectly viewable though from any browser on a Windows machine though.
Great video, thank you for sharing. How did you get the maintenance tool menu and network menu on the right side of the screen? I only have the Device, Presence and Event options.
Can you maybe give me a timestamp as to where in the video as it is two different apps and lots of different views? Both of mine are fairly standard I think, and both hosted in Docker containers.
@@GadgeteerZA
Danie thank you for your quick response. Here are the timestamps. I'm running my Pi.Alert on a Raspberry Pi also.
Timestamp
13:08 - Shows Device, Presence, Events, Network, Maintenance and Help/FAQ
19:19 - Shows information under the Network menu option
19:31 - Shows information under the Maintenance menu option
20:27 - Shows information under the Help/FAQ menu option.
My setup of Pi.Alert doesn't have the Network, Maintenance and Help/Faq menus.
Thank you.
OK sorry about that confusion as I thought you meant the right side of the screen. OK very interesting as it seems those functions are not in the original Pi.Alert with Raspberry install at github.com/pucherot/Pi.Alert. Someone has logged an issue at github.com/pucherot/Pi.Alert/pull/186 to contribute that additional info to the original. So others, like the Docker version I'm using are actually forks with improvements. I got the Docker version instructions from registry.hub.docker.com/r/jokobsk/pi.alert.
So you probably have two choices:
1. Wait and see if updates do bring that functionality.
2. Do a simple install of Docker on the Pi, and then install the Docker version I'm using and try it. You can leave your original Pi.Alert install on the Pi, just to try this one out, and then decide which you want to stick with.
awesome, Danie, do you know if it is possible set up notifications only, for example, devices marked like Favourites or added in group "always on"? I'd like use this in enterprise enviroment but I receive tons of emails with new, connected or disconnected devices, all of them. thanks
I think it can be achieved as there are two ways to configure alert notifications:
1. Settings/Notify On: Specifies which events trigger notifications. Remove the event type(s) you don't want to get notified on. This setting overrides device-specific settings in the UI. Typically, categories appear such as Internet (WAN IP changes), new_devices, down_devices, events, ports, etc. Can't see that you can actually add new options here (maybe from the config file?).
2. Per device you can enable or disable all events, alert down, new device (you disable new device alert for a device you have identified after it was alerted as a new identified device. 'Alert down' option would be ticked for an always -on device you want an alert for.
So you could come right with the above tweaks, or by sorting the view order on the GUI, but another option is to otherwise log an issue request at their project at github.com/pucherot/Pi.Alert/issues. It may be worth also just installing it and testing it with just a few devices.
@@GadgeteerZA thanks for the advice man, it works better now I just had to deselect of the other devices (scan cycle -> don't scan, alert all events -> un marked, new device -> unmarked) and I left only the more important devices and I get only notification of these ones.
For now works very well for me, but I would like that the App had an option to less time of scan cycle, because 5 minutes is a long time and probably I'll notice when the devices down after all users do.
thank again
@@ginsanhertz9788 Glad you came right. Yes it is open source so may be possible to alter that scan time in the code even. I also noted though that the Docker version is slightly different from the normal install version, so you may want to dig a bit further into that too.
Hi Danie,
Greetings from Grand Duchy of Luxembourg .. ;-)
Thanks for this video ... I have Pi.Alert for few weeks up and running on my Synology as a docker container .. Works fine .. ;-)
I saw in your video that you do use some container "Ressource Stats" to monitor per container on a graphical view, the consumed resources .. What is this tool you do use .. I was not able to find out ...
Thanks in advance ...
Luc
Hi there Luc, and greetings to you from a cold overcast Cape Town. The only thing coming to mind right now on containers was the Glances service that also runs in a container. Can't remember if I did a video about it on its own. That shows what containers are running and how much resources they are using.
EDIT: I see here was a mention about Glances but it was really displaying widgets in the Dashy app, that drew data from Glances - ruclips.net/video/JW2YJp34SQw/видео.html. Looks like I must still do a video about Glances.
@@GadgeteerZA Hi Daniel. Thanks for your response. I use both! Glances and Dashy .. and the widget connecting both .... ;-) .... I will take a closer look, to find out, where I can see the same information as you do display in your video ..... Because this is a valuable info, to see visually what every single container is “consuming” .... Thanks so far .... and greetings back to Cape Town ... (“only” 13.000 km physically, but a few milliseconds digitally .distant 😉....
@@GadgeteerZA UPDATE: I found details, similar to your in the portainer docker I have installed .... ;-) .. So all good for now ....
Windows Version?
Not that I can recall. It is intended to run in a Raspberry Pi or in a Linux container mostly as it runs 24/7. It is perfectly viewable though from any browser on a Windows machine though.
I would like to thank you. u make me fix my shoutrr address
Very glad to hear that - thanks for letting me know