Configuring Siren ML
When you first run SirenML the default configuration file is placed in /etc/sirenml/sirenml.yml
.
The following table outlines and describes the attributes which are configurable within the SirenML config. Properties in bold are required.
Property | Description | Type | Default |
---|---|---|---|
| URI for the Elasticsearch instance to read data from and write machine learning data to | URI |
|
| Sets the logging level to the console. Set to |
|
|
| Username used to communicate with Elasticsearch (only include if Elasticsearch is run with security enabled) | string |
|
| Password used to communicate with Elasticsearch (only include if Elasticsearch is run with security enabled) | string |
|
| Name of the security plugin used to secure Elasticsearch (only include if Elasticsearch is run with security enabled) |
|
|
| Boolean flag indicating if Siren ML should be run over | boolean |
|
| Path to the SSL certificate used by the Siren ML server | path |
|
| Path to the SSL key used by the Siren ML server | path |
|
| Boolean flag indicating if Elasticsearch is being run over | boolean |
|
| Path to the SSL certificate used in the requests to a secure Elasticsearch instance (only used if | path |
|
| Path to the SSL key used in the requests to a secure Elasticsearch instance (only used if | path |
|
| Boolean flag indicating if the certificates should be verified (only used if | boolean |
|
| Maximum number of models that can be trained in parallel (additional model trainings jobs are queued until one of the running model trainings is complete) | int |
|
| Maximum number of model activations that can run in parallel (additional model activation jobs are queued until one of the running model activations is complete) | int |
|
| Maximum number of historical detections that can run in parallel (additional historical detection jobs are queued until one of the running historical detections is complete) | int |
|