Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Winsvc monitoring: Each svc status check takes long time, adds up for several services on same server #912

Closed
mountaindude opened this issue Dec 12, 2023 · 0 comments · Fixed by #899 or #981

Comments

@mountaindude
Copy link
Collaborator

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:

  1. For all hosts
    1. For all services on a particular host
      1. Get status for all services on target host
      2. 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:

  1. For all hosts
    1. Get status for all services on target host
    2. For all services on target host
      1. Check status of the service at hand

Expected Behavior

No response

To Reproduce

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment