By Jamie Taylor
You can now trigger workflow executions from Performance Counter notifications and evaluate Name, Category and Instance in conditions to build even more customizable workflows for your IT processes.
By Jamie Taylor
You can now create interactive, conditional troubleshooters that can be used to ask questions, provide answers, and run self remediation scripts and tasks based on user input. Pulseway's Client Portal can be used to standardize IT processes, empower end-users and reduce the workload on your support team.
I am trying to configure Pulseway on my Ubuntu Server 20.04 LTS machine, but I'm having issues getting it to recognise systemd services.
The services I want to monitor are smbd, plexmediaserver and clamav-freshclam. Regardless of what configuration I use, none of these services are even recognised by Pulseway let alone monitored. I have also tried setting each service as "NONE", "UPSTART" and "SYSVINIT" but nothing seems to work.
The strange part is that ssh is monitored despite the fact that it's configuration is identical to the others.
Here is a screenshot of my configuration:
Can someone please help me out here? Is there something I'm missing?
EDIT: Never mind. It suddenly started working after I posted this.
Hi, i want to know how i can monitor the dropbox daemon on linux, i'v tried things with workflow but when i stop the service manualy it won't send me a notification or try to restart the service, and that is bothering me becaus on our servers we need to have dropbox running all the time for our application, i know that dropbox is weird on linux, it won't show with systemctl, but it's still like a daemon.
I'm running debian buster machine all up to date with the last pulseway agent
I was in the process of configuring my Pulseway agent on a VPS running Ubuntu Server 20.04 and I ran in this interesting bug.
Even using the sample config provided by the agent, uncommenting the Ping Responses bloc throws this error in the log, and prevents the service from starting.
vps pulseway: Starting Pulseway Daemon version 6.5 (2019082205) vps pulseway: Configuration: Values for 'Milliseconds' attribute at 'PingResponse' node 10.6.0.53(1) should be between 1 and 1000 vps systemd: pulseway.service: Main process exited, code=exited, status=1/FAILURE
The PingResponse bloc in /etc/pulseway/config.xml looks like this:
<PingResponses> <PingResponse Address="10.6.0.53" Milliseconds="1500" Minutes="1" PriorityOnSlowResponse="1" PriorityOnNoResponse="1" Alias="vps DNS notif" Enabled="true"/> </PingResponses>
So then I tried many Milliseconds values between 1 and 1000 but the same exact error always comes back.
Is this a known issue or is there anything wrong with my setup?
Many thanks to anyone who can help,