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 SOS.
20
What command did you use to start Butler SOS?
What operating system are you using?
Linux
What CPU architecture are you using?
x86_64
What Qlik Sense versions are you using?
2024-May IR
Describe the Bug
Similar to #805, tighten the filters for the log Log4Net XML appenders included with Butler SOS, so the log appender file for proxy service only forwards QS proxy log entries, the log appender for repository only forwards those QS log entries, and the log appender for the scheduler service only forwards the scheduler's log messages.
Same thing for user events/user log appenders.
Also add verification of data types before creating InfluxDB datapoints.
I.e. ensuring that Sense ID fields are indeed valid UUIDs, that date fields are valid dates etc.
Expected Behavior
No response
To Reproduce
No response
The text was updated successfully, but these errors were encountered:
mountaindude
changed the title
Make handling of log events sent from QS server more robust.
Make handling of log and user events sent from QS server more robust
May 19, 2024
What version of Butler SOS are you using?
10.0.0 alfa
What version of Node.js are you using? Not applicable if you use the standalone version of Butler SOS.
20
What command did you use to start Butler SOS?
What operating system are you using?
Linux
What CPU architecture are you using?
x86_64
What Qlik Sense versions are you using?
2024-May IR
Describe the Bug
Similar to #805, tighten the filters for the log Log4Net XML appenders included with Butler SOS, so the log appender file for proxy service only forwards QS proxy log entries, the log appender for repository only forwards those QS log entries, and the log appender for the scheduler service only forwards the scheduler's log messages.
Same thing for user events/user log appenders.
Also add verification of data types before creating InfluxDB datapoints.
I.e. ensuring that Sense ID fields are indeed valid UUIDs, that date fields are valid dates etc.
Expected Behavior
No response
To Reproduce
No response
The text was updated successfully, but these errors were encountered: