Parse error

[varchar66]

Hi,

I've got multiple errors related to Backgrounder plugin:

Details on first 25 reported errors:
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-1.log.2022-06-04`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-2.log.2022-06-04`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-0.log.2022-06-04`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-5.log.2022-06-04`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-7.log.2022-06-04`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-3.log.2022-06-05`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-1.log.2022-06-05`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-5.log.2022-06-05`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-6.log`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-4.log.2022-06-05`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-0.log.2022-06-05`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-4.log`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-1.log`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-2.log.2022-06-05`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-0.log`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-6.log.2022-06-04`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-7.log`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-2.log`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-6.log.2022-06-05`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-5.log`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-4.log.2022-06-04`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-7.log.2022-06-05`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-3.log`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node3/backgrounder_0.20221.22.0516.17201670076967931717314/logs/backgrounder-instrumentation-metrics_node3-3.log.2022-06-04`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`
--> File: `node2/backgrounder_0.20221.22.0516.1720799865994567249969/logs/backgrounder-instrumentation-metrics_node2-7.log.2022-06-05`. Line: 1. Reported by: `BackgrounderPlugin`. Error: `Failed to parse backgrounderId from filename. All events from this file will have null id`

And ClusterControllerPlugin:

      Details on first 25 reported errors:
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log.2022-06-04`. Line: 21. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log`. Line: 21. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log.2022-06-04`. Line: 55. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log`. Line: 55. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log.2022-06-04`. Line: 98. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log`. Line: 89. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log.2022-06-04`. Line: 132. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log`. Line: 123. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log.2022-06-04`. Line: 166. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log`. Line: 157. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log.2022-06-04`. Line: 200. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log`. Line: 200. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log.2022-06-04`. Line: 234. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log`. Line: 234. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log.2022-06-04`. Line: 268. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log`. Line: 268. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log.2022-06-04`. Line: 311. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log`. Line: 302. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log`. Line: 336. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log.2022-06-04`. Line: 345. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log.2022-06-04`. Line: 379. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log`. Line: 370. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log`. Line: 404. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log.2022-06-04`. Line: 413. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`
      --> File: `node3/clustercontroller_0.20221.22.0516.172014037389283593743125/logs/clustercontroller.log`. Line: 438. Reported by: `ClusterControllerPlugin`. Error: `Failed to parse Cluster Controller DiskSpaceMonitor event from log line`

It's something relating to parsing. If I'm not mistaken, it started after upgrading Tableau Server to 2022.1.2.

LogShark version: 4.2.2.0
Processed zip file compressed size: 7,601 MB
Additional tags returned by plugins: '2022.1.2';'20221.22.0516.1720'

Could you please suggest a fix for this?