fix(sequence): failures support captures

Author: mbehr1

docs/fishbone/docs/sequences.md

@@ -134,6 +134,41 @@ the sequence `SW Update` will fail with error `crash` if a log message from `SYS
 Only a started sequence gets aborted with any of the defined failures. If the failures occur without a started sequence they are ignored.
 :::
 
+#### failure capturing data
+
+Failure filters can capture data similar to [context](#context):
+
+E.g. for
+```jsonc {7,8,12}
+/get/docs/0/filters?
+sequences=[
+  {
+    "name": "SW Update",
+    "steps":[ // one object per step...
+    ],
+    "failures":{
+      "crash":{ // a dlt filter definition like:
+        "type":3, // event
+        "apid":"SYS",
+        "ctid":"JOUR",
+        "payloadRegex":"^process '(?<crash_process>.*?)' crashed with signal (?<crash_signal>.*)"
+      }
+    }
+  }
+]
+```
+
+A message like
+```
+SYS JOUR process 'foo' crashed with signal 6
+```
+
+will lead to a failure
+
+`crash: "crash_process":"foo", "crash_signal": "6"`
+
+and `crash_process` and `crash_signal` are added to the [context](#context) as well.
+
 ### `kpi` definition
 
 A `kpi` has the following attributes:

package.json

@@ -146,7 +146,7 @@
   },
   "dependencies": {
     "@vscode/extension-telemetry": "^0.9.8",
-    "dlt-logs-utils": "0.13.2",
+    "dlt-logs-utils": "0.13.3",
     "jju": "github:mbehr1/jju#3aa4169df926e99083fdd511d7c20b5bd9ba789f",
     "js-yaml": "^4.1.0",
     "json5": "2.2.3",

src/webview/package.json

@@ -13,7 +13,7 @@
     "@testing-library/jest-dom": "^5.16.5",
     "@testing-library/react": "^13.4.0",
     "@testing-library/user-event": "^14.4.3",
-    "dlt-logs-utils": "0.13.2",
+    "dlt-logs-utils": "0.13.3",
     "dompurify": "^2.4.0",
     "jju": "github:mbehr1/jju#3aa4169df926e99083fdd511d7c20b5bd9ba789f",
     "js-yaml": "^4.1.0",

src/webview/yarn.lock

@@ -4259,10 +4259,10 @@ dir-glob@^3.0.1:
   dependencies:
     path-type "^4.0.0"
 
-[email protected].2:
-  version "0.13.2"
-  resolved "https://registry.yarnpkg.com/dlt-logs-utils/-/dlt-logs-utils-0.13.2.tgz#02321141fbf0c01f6918203ff5f7793b4ab36779"
-  integrity sha512-1daxUv0JUGu+gTHv/aqex0XqNwNXWByXeCTxF4T/jMgZkpwYXmfG3AxeI1DznDHBe4DTIEFSWWOpFwKaOrQjXw==
+[email protected].3:
+  version "0.13.3"
+  resolved "https://registry.yarnpkg.com/dlt-logs-utils/-/dlt-logs-utils-0.13.3.tgz#ae24ca795273ab1e1f4cd9f539c0e3d4e4d64b49"
+  integrity sha512-5daTvEi6v3K0muo1Izqozz4OPCl1fp6YOfBEnB+DdE0oJBDKtbTA707vn59qJvuhKJ5QdJgh8ix3gq6GRbQ/Vw==
 
 dlv@^1.1.3:
   version "1.1.3"

yarn.lock

@@ -2283,10 +2283,10 @@ dir-glob@^3.0.0, dir-glob@^3.0.1:
   dependencies:
     path-type "^4.0.0"
 
-[email protected].2:
-  version "0.13.2"
-  resolved "https://registry.yarnpkg.com/dlt-logs-utils/-/dlt-logs-utils-0.13.2.tgz#02321141fbf0c01f6918203ff5f7793b4ab36779"
-  integrity sha512-1daxUv0JUGu+gTHv/aqex0XqNwNXWByXeCTxF4T/jMgZkpwYXmfG3AxeI1DznDHBe4DTIEFSWWOpFwKaOrQjXw==
+[email protected].3:
+  version "0.13.3"
+  resolved "https://registry.yarnpkg.com/dlt-logs-utils/-/dlt-logs-utils-0.13.3.tgz#ae24ca795273ab1e1f4cd9f539c0e3d4e4d64b49"
+  integrity sha512-5daTvEi6v3K0muo1Izqozz4OPCl1fp6YOfBEnB+DdE0oJBDKtbTA707vn59qJvuhKJ5QdJgh8ix3gq6GRbQ/Vw==
 
 doctrine@^3.0.0:
   version "3.0.0"