You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of Node.js are you using? Not applicable if you use the standalone version of Butler.
What command did you use to start Butler?
What operating system are you using?
WinSrv
What CPU architecture are you using?
Intel
What Qlik Sense versions are you using?
2023-Aug
Describe the Bug
Currently Butler's win svc checking works like this:
For all hosts
For all services on a particular host
Get status for all services on target host
Check status for the service at hand
As each call to la remote host may take tens of seconds, the above approach will result in minutes of delays if there are many services that should be monitored.
If there are several to-be-monitored services on each host (which is a likely scenario) this approach could be used instead, most likely saving significant time:
For all hosts
Get status for all services on target host
For all services on target host
Check status of the service at hand
Expected Behavior
No response
To Reproduce
No response
The text was updated successfully, but these errors were encountered:
What version of Butler are you using?
9.3.1
What version of Node.js are you using? Not applicable if you use the standalone version of Butler.
What command did you use to start Butler?
What operating system are you using?
WinSrv
What CPU architecture are you using?
Intel
What Qlik Sense versions are you using?
2023-Aug
Describe the Bug
Currently Butler's win svc checking works like this:
As each call to la remote host may take tens of seconds, the above approach will result in minutes of delays if there are many services that should be monitored.
If there are several to-be-monitored services on each host (which is a likely scenario) this approach could be used instead, most likely saving significant time:
Expected Behavior
No response
To Reproduce
No response
The text was updated successfully, but these errors were encountered: