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
{{ message }}
Repository navigation
Commit b6993da
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/configuration.rst
+11-2Lines changed: 11 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -234,7 +234,10 @@ To entirely skip the anomaly detection phase, you can set ``inspector_module_nam
234
234
- A unique name amongst the detector configurations top identify the detector instance.
235
235
* - inspector_name
236
236
-
237
-
- The name of the inspector configuration the detector consumes data from. The same inspector name can be referenced in multiple detector configurations.
237
+
- The name of the inspector configuration the detector consumes data from. The same inspector name can be referenced in multiple detector configurations. Omit this or set ``consume_from: detector`` when the detector consumes from another detector.
238
+
* - consume_from
239
+
- ``inspector``
240
+
- Set to ``detector`` for detector instances that consume from the detector-to-detector topic instead of an inspector.
238
241
* - detector_module_name
239
242
-
240
243
- Name of the python file in ``"src/detector/plugins/"`` the detector should use.
@@ -255,7 +258,13 @@ To entirely skip the anomaly detection phase, you can set ``inspector_module_nam
255
258
- Threshold for the detector's classification.
256
259
* - produce_topics
257
260
- ``(empty)``
258
-
- (Optional) Comma-separated list of topic suffixes to produce alerts to. If left empty, defaults to the ``generic`` topic.
261
+
- (Optional) Comma-separated list of alerter topic suffixes to produce alerts to. If left empty, defaults to the ``generic`` alerter topic. Use ``send_to_alerter: false`` or ``produce_topics: []`` for intermediary detectors that should not produce to an alerter.
262
+
* - next_detectors
263
+
- ``(empty)``
264
+
- (Optional) Comma-separated list of detector instance names that should receive this detector's suspicious output on detector-to-detector topics.
265
+
* - send_to_alerter
266
+
- ``true``
267
+
- Set to ``false`` to disable the detector-to-alerter Kafka output while still allowing detector-to-detector forwarding.
Copy file name to clipboardExpand all lines: docs/pipeline.rst
+11-2Lines changed: 11 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -749,13 +749,22 @@ You may use the provided, pre-trained models or supply your own. To use a custom
749
749
- `model`: model name
750
750
- `checksum`: SHA256 digest for integrity validation
751
751
- `threshold`: probability threshold for classifying a request as malicious
752
-
- `inspector_name`: name of the inspector configuration for input
752
+
- `inspector_name`: name of the inspector configuration for input. Omit this or set `consume_from: detector` when consuming from another detector.
753
+
- `consume_from`: use `detector` to consume from the detector-to-detector topic for this detector instance
753
754
- `detector_module_name`: name of the python module the implementation details reside
754
755
- `detector_class_name`: name of the class in the python module to load the detector implementation details
755
-
- `produce_topics`: (Optional) Comma-separated list of topic suffixes to produce alerts to. If left empty, alerts are sent to the ``generic`` alerter topic.
756
+
- `produce_topics`: (Optional) Comma-separated list of topic suffixes to produce alerts to. If left empty, alerts are sent to the ``generic`` alerter topic. Use `send_to_alerter: false` or `produce_topics: []` for intermediary detectors that should not produce to an alerter.
757
+
- `next_detectors`: (Optional) Comma-separated list of detector instance names that receive this detector's suspicious output.
756
758
757
759
These parameters are loaded at startup and used to download, verify, and load the model/scaler if not already cached locally (in temp directory).
758
760
761
+
Detector Chaining
762
+
-----------------
763
+
764
+
Detector instances can be chained by setting ``next_detectors`` on the upstream detector and ``consume_from: detector`` on the downstream detector. Detector-to-detector topics use the naming pattern ``[detector_to_detector_prefix]-[detector_name]``.
765
+
766
+
For intermediary detectors that should only forward suspicious output to another detector, set ``send_to_alerter: false`` or ``produce_topics: []``.
0 commit comments