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.
No response
What command did you use to start Butler?
N/A
What operating system are you using?
Windows, macOS
What CPU architecture are you using?
x86_64
What Qlik Sense versions are you using?
2021-Aug
Describe the Bug
When Butler sends reload failures and events and log entries to New Relic, it does this check:
I.e. checks if either of those two config entries exist.
That is incorrect.
It is only if both those config entries exist that the custom property's value should be used as destination for events / log entries.
Note that this applies to both New Relic events and log entries.
Expected Behavior
No response
To Reproduce
No response
The text was updated successfully, but these errors were encountered:
mountaindude
changed the title
Incorrect check for config items when sending reload failures to New Relic§
Incorrect check for config items when sending reload failures to New Relic
Dec 2, 2022
What version of Butler are you using?
8.6.0
What version of Node.js are you using? Not applicable if you use the standalone version of Butler.
No response
What command did you use to start Butler?
N/A
What operating system are you using?
Windows, macOS
What CPU architecture are you using?
x86_64
What Qlik Sense versions are you using?
2021-Aug
Describe the Bug
When Butler sends reload failures and events and log entries to New Relic, it does this check:
I.e. checks if either of those two config entries exist.
That is incorrect.
It is only if both those config entries exist that the custom property's value should be used as destination for events / log entries.
Note that this applies to both New Relic events and log entries.
Expected Behavior
No response
To Reproduce
No response
The text was updated successfully, but these errors were encountered: