Jump to content

Chris

Staff
  • Posts

    1347
  • Joined

  • Last visited

Posts posted by Chris

  1. Hi Esteve,

    Currently Pulseway can notify you about all failed login attempts, if you configure the Event log filter (open the Pulseway Manager -> Notifications -> Event Log -> tick the checkbox -> Add and configure it) to notify you about these notifications an select option (allow repeating notifications) or notify you only once, if you do not select this option.

    Why don't you simply block the access to this server from unknown IP addresses? You can configure this using Firewall or ACL's.

  2. Hi Diego,

    You can monitor your printer via SNMP (if your printer supports this option).

    Regarding how to configure it - this article will give you a general idea how to configure SNMP monitoring.

  3. Hi,

    Yes, you are correct the Ping server option is one per agent. If you enable this option, then from your mobile device or Pulseway WebApp you will be able to see the chart  which shows the network connections performance.

    Quote

    However, I am unable to get the ping response to cause a notification.  When a response is slow or does not return my priorities are working if I look under "Ping Responses" in my dashboard.  But even when a ping response notifies at priority 0 and it goes red I do not get a notification or an alert.

    Is it possible that the Pulseway agent is registered using different Pulseway user account and you are using a different user account to logon to the Pulseway WebApp or on your mobile device. If so, then you need to configure the associated account for the system.

  4. Hi Brandon,

    If the Pulseway service fails to start at startup, then at first you will need to look for the entries related to the Pulseway service into the Windows event log -> System and find out why the . If the message from Service Control Manager is that the Pulseway service failed to start in 30 seconds or didn't respond in a timely manner, then you can try to increase the startup timeout by running built in script 'Increase Windows Service Timeout at Startup' (You can adjust the timeout interval. In this script it is set to 60000ms [60 seconds]). Our customers get the best results if they set the timeout to 9000 (90 seconds), but you will need to test it.

    Also. please check other windows event log logs, whether there are no other event entries related to the Pulseway service at the startup.

     

    But if the Pulseway service is running and suddenly stops, then please enable diagnostic logging from the Pulseway Manager -> Settings -> Diagnostic and then send the trace.log file from the Pulseway's installation folder to support@pulseway.com.

  5. Hi Darrell,

    Thank you for your suggestion, we will consider the possibility to introduce this option into the future, but meanwhile, in order to scan other subnets, you will need to change the subnet mask on the system which is marked as a probe.

  6. Hi,

    In order to do this, you will need to configure the workflow from the Admin section -> Business Process -> Workflow -> New -> and configure it to assign all the tickets to you (create a Trigger - Created By: AnyOne and Update - Primary Technician: select your account)

     

  7. Hi,

    You can configure the Scan exclusions and trusted applications from the Pulseway WebApp -> Antivirus -> Policies -> select required policy -> Antivirus Protection -> General -> Scan Exclusions and add the folder here. Also, you can configure this application as a 'Trusted Application' to exclude it from the scan.

  8. Hi,

    Regarding Pulseway manager and tray icon - yes, we have this as a confirmed feature, but unfortunately it hasn't been implemented as of yet.

    Regarding desktop icon and shortcut name - I don't see any problem doing this. The only thing that you will need to do it manually.

    Rename the folder and service - it is possible, but if you will rename it, then you will need to register Pulseway service manually with a different name.

  9. Hi, 

    Unfortunately Pulseway can't notify you if the IP address is not reachable. But in order to solve your issue you will need to create a PowerShell script which will ping the device and return exit code 0 - success , exit code 1 - failure. And then you can run this script as an automated task every 1...5 minutes and get the notification based on the exit code. Read more about the Automation from here. https://intercom.help/pulseway/features/automation

     

×
×
  • Create New...