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

New Relic has to be enabled as win-service monitoring for ANY such monitoring to work. #967

Closed
mountaindude opened this issue Feb 1, 2024 · 0 comments · Fixed by #981
Closed
Labels

Comments

@mountaindude
Copy link
Collaborator

What version of Butler are you using?

9.4.0

What version of Node.js are you using? Not applicable if you use the standalone version of Butler.

18

What command did you use to start Butler?

node butler.js -c production.yaml

What operating system are you using?

Windows 10

What CPU architecture are you using?

x86_64

What Qlik Sense versions are you using?

2023-Nov

Describe the Bug

Current situation is as follows:

  • Detection of stopped Windows services will only be done if Butler.incidentTool.newRelic.serviceMonitor.monitorServiceState.stopped.enable is set to true
  • Detection of started Windows services will only be done if Butler.incidentTool.newRelic.serviceMonitor.monitorServiceState.running.enable is set to true

This is obviously wrong.
Those settings should only apply to New Relic as a destination for Windows services monitoring events.
Additionally, those settings should only be considered when also the Butler.serviceMonitor.alertDestination.newRelic.enable setting is true

Expected Behavior

Each destination for Windows services events should be enabled/disabled individually via the Butler.serviceMonitor.alertDestination.* settings.
In some cases additional settings may be available for destinations (e.g. New Relic).

To Reproduce

No response

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