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

Make handling of log and user events sent from QS server more robust #806

Closed
mountaindude opened this issue May 19, 2024 · 0 comments · Fixed by #779 · May be fixed by #818
Closed

Make handling of log and user events sent from QS server more robust #806

mountaindude opened this issue May 19, 2024 · 0 comments · Fixed by #779 · May be fixed by #818

Comments

@mountaindude
Copy link
Collaborator

mountaindude commented 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

@mountaindude 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant