Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by Jaapyse

  1. Hey Forum,

    We have a lot of notification pairs that are hardly relevant because they are pairs. E.g.: a ping doesn't respond for ten minutes and than it comes back again. Personally I don't mind these because it gives me a better understanding of what's going on in my networks, but my employer heard from the reseller that a simple script can delete the notifications when a pair forms. I do have to admit that it would be nice if rebooting a server wouldn't make such a mess of these notifications. I was told to look into implementing it, but I can't quite find it. Does anybody have any suggestions? Is this even a real thing?

    - Jaapyse

  2. Hey Marius,

    I seem to recall that there was some way to limit which devices are allowed to connect and monitor/manage the systems but now that I try to find out how to set it up I can't find it at all. Am I mistaken or did I just overlook this in the settings?

    - Jaapyse

  3. Hey Pulseway,

    Just a small thing: when "Collect historical data for charts" is enabled and you go to the graph in the web interface, it shows the incorrect unit when hovering over the line. If I go to a ping graph and then to the temperature graph it says "38 ms"; If I go to the network adapter graph and then to the temperature graph it says "38 B"; I even got it to say "38 Connection failures" from a performance counter, but never 38 °C.

    I think you get the point, it's minor, but it's still a bug.

    - Jaapyse

  4. Hey Pulseway,

    I think there was another topic about this, but I can't find it any more, but is it possible to make notifications disappear (archive) automatically when the problem that caused them is gone? E.g.: A ping is missing for a little while and then comes back (2 notifications), a system is too hot and cools down (1 notification), a disk too full (2 notifications), memory usage peeks (we get this all the time), a network loses network connection for five minutes (many many notifications if it happens). The result of these problems is that we get spammed full of notifications every night when really only a small part of that is relevant to the well-being of our customers' systems. Can notifications automatically be archived so we just view the relevant stuff? There's archiving and syslog anyways!

    - Jaapyse

  5. Hey forum,

    It's me again (how could two weeks go by without me asking any questions...;)). The problem I'm facing is every once in a while I open a remote desktop connection and when ordering the command "Ctrl+alt+del" it doesn't respond. Clicking the accessibility doesn't do anything either. Usually I can Pulseway RDP into another server in the network and from there MS RDP into the server I'm trying to reach but that is obviously not the way. For the moment it's not too much of a problem, but one of these days I'm going to run into a network with only one monitored device and no MS RDP available and by then I'm in trouble...

    I hope I'll have a response before then.

    - Jaapyse

  6. Hey mario and others,

    We have tested placing the enterprise server in front of the reverse proxy and the results were indeed positive! I would like to add however that, in case this doesn't solve the problem for you, disabling hardware acceleration can make a huge difference. For some of our systems it made the difference of lagging with one frame per second to being fluent enough to work with it flawlessly. I thought I'd let you know.

    - Jaapyse

  7. Hey Pulseway,

    I don't want to be an ass about small things but I noticed that in the Web App => Server Admin => Overview => Notifications History the "7 days ago" marker is off by a day. It shows it 6 days ago. Same story with the 15 day marker, which is at 14 days ago and so on.

    I thought I'd just let you know, since it caught my attention.

    - Jaapyse


  8. Hey forum,

    The problem has been solved and I would like to share the solution with the community.

    This was the problem: two systems within the same network were going online and offline (according to Pulseway) at random times. Usually for roughly 40 minutes, but sometimes half an hour or less and sometimes over an hour. Never were they both offline, but sometimes they were both online.

    This was a / the solution. This network is unique relative to our other customers’ networks in that DNS is done by the DrayTek router.  All the other networks have either DrayTeks and a Windows server doing DNS or the default router the ISP provides. I noticed that clearing the DNS cache once or twice always resulted in the system coming back online within seconds. Therefore I added (more like enabled) a rule to clear the DNS cache whenever anything appears in it, and since then the systems have been online the whole time.

    If anybody runs into this problem, I hope this topic / post can help you.

    - Jaapyse

  9. Hey Calin and others,

    I am experiencing a similar problem. I am pinging the routers of our customers to see if the networks are reachable. After setting it up I got 23 critical errors, basically each router. I checked the ping from that particular server via cmd, but all (except 3) seemed fine. There is something strange going on here and I would like to know what...

    I'd like to hear from you soon.

    - Jaapyse

  10. Hey forum,

    I recently had the whole thing running rather well in testing phase, so we decided to go for real. This meant getting different accounts to set the rights properly. This is what I did:

    puls.connect to connect the agents to the enterprise server.
    puls.adm to to manage everything (the only admin account).
    puls.myname to manage all the systems.
    puls.mycolleaguesname just like me.

    I linked all of the systems from connect to the others as associated accounts and gave all rights and notifications on.

    Here is the problem: I am getting almost no notifications whatsoever. I have no idea why, they should be there. Does anybody have any idea?

    - Jaapyse

  11. Hey mario,

    That's a whole lot of tips in a very short message! Amazing! We have an enterprise server behind a reverse proxy, so that might indeed help. I will ask around and see if my team can help this problem. Thank you very very much!

    - Jaapyse

  12. Hey Forum,

    Due to security issues our company has recently decided to close all Windows RDP ports and switch to using the Pulseway remote desktop feature, as we were already using Pulseway on (almost) all of our customers' systems. However, these connections seem extremely slow and laggy, even when we had a good connection using Windows RDP. Is this a known problem that we can fix? Is there maybe a workaround?

    I'm looking forward to your response,

    - Jaapyse

  13. Hey forum,

    We're experiencing some trouble using the HTTP-GET feature. Our old monitoring system (Nagios) is able to monitor the availability of web sites, more specifically login pages for access points, perfectly well. However, when using Pulseway it gives a notification when it reaches the AP because it has HTTP basic authentication. This is not a problem, if we get that response we know that it is reachable. This should not be seen as a problem and should not give a notification? Could you fix this? Is there a workaround at the moment?

    - Jaapyse

  14. Hello forum,

    Lately I encountered a machine that couldn't monitor CPU-temp. There were just no devices in the hardware list when I tried to set the notification. The machine in question is an HP ProLiant DL380 G4 and the OS is installed directly on the machine, not using Hyper-V or similar software that could mess up these kind of sensors.

    Any ideas?

    - Jaapyse

  15. Hey forum,

    When I click "Next" to start the installation of an agent on a certain machine, I immediately get the error "The installer was interrupted before Pulseway could be installed. You need to restart the installer to try again." However, it doing it again does not change anything.

    Any ideas?

    - Jaapyse

  16. Update:

    We now have multiple networks with multiple agents successfully running, one of them being a very similar system (one Hyper-V and a Windows server on it). Interesting fact: the system that is giving me trouble had also been used for testing before I got to set it up. I tried to give it a fresh install, but the settings remained. I now have uninstalled the agent, deleted the Pulseway folder in C:\Program Files and deleted all the MMSoft registry keys. After that, installed Pulseway again and the problem was not solved. I presume some of the information above will be useful.

    - Jaapyse

  • Create New...