Guy Steels

Another +1

Why is the "computer is started" notification not available as workflow trigger? I understand the "System offline" + "System back online" triggers in cases where you monitor servers with Pulseway (which are supposed to be online all the time). In our case we monitor remote workstations that get booted up and shut down daily. If we could use "computer is started" as trigger it would be ideal to run eg. an automation script once a system is booted up.

We recently started using notifications for the (+-50) systems we monitor. I was wondering how long the history will be kept for. We have a more atypical setup as the systems aren't servers but video editing workstations which come online/offline quite often, so the amount of notifications will grow quite rapidly. Regards, Guy.

Every self-respecting developer these days uses source code management. It would be nice if Pulseway would provide some sort of integration between a few major SCM platforms (Github, Gitlab, Bitbucket, ...) and the scripts section in the Pulseway management system. All (automation) scripts I currently use are SCM'ed in Gitlab but the only option currently to make them available in Pulseway is a dumb copy/paste. Regards, Guy

The web application has a "Session Timeout" setting. Since a few weeks this setting has no effect anymore. The setting we use is 120 minutes but we are always logged out of the web application after +- 5 15 minutes of inactivity. I'm not 100% sure but it seems this issue popped up since the enhanced 2FA update which was released a few weeks ago.

Thank you Chris. I had overlooked that config. This already helps a lot.

We would like to increase the time a loggedin session is active in the web application. Currently, you get logged out after +- 30 minutes of inactivity. As far as I know there is no config available that can be modified in the webapp itself (we currently have a team account). I tried to fix it using a browser addon/extension ("Staying alive" for Chrome or "Session alive" for Firefox) but I didn't succeed in configuring it correctly to make it work. A background request on the main url (eg. ...pulseway.com/app/main/systems) did not refresh the session. If anyone has some pointers how I should configure the stay alive extensions it would be appreciated.

While inputting notes through the webapp I noticed that only 256 characters of notes are saved, allthough the interface itself accepts more input. The GUI should somehow show that there's a character limit. On the other hand, it would be nice if we could save more than 256 characters.