Configuration Guide

There are two parts to the configuration of this system:

  • The Event Notification Server configuration - typically /etc/zm/zmeventnotification.ini
  • The Machine Learning Hooks configuration - typically /etc/zm/objdetect.ini and/or /var/lib/zmeventnofication/mlapi/mlapiconfig.ini

The ES comes with a sample ES config file which you should customize as fit. The sample config file is well annotated, so you really should read the comments to get an erstanding of what each parameter does. Similarly, the ES also comes with a sample objdetect.ini file which you should read as well if you are using hooks. If you are using mlapi, read its config.

Secret Tokens

All the config files have a notion of secrets. Basically, it is a mechanism to separate out your personal passwords and tokens into a different file from your config file. This allows you to easily share your config files without inadvertently sharing your secrets.

Basically, this is how it works:

You add an attribute called secrets to the [general] section of either/both config files. This points to some filename you have created with tokens. Then you can just use the token name in the config file.

For example, let’s suppose we add this to /etc/zm/objectconfig.ini:

# This is an optional file
# If specified, you can specify tokens with secret values in that file
# and onlt refer to the tokens in your main config file


And /etc/zm/secrets.ini contains:

# your secrets file

Then, while parsing the config file every time a key value is found that starts with ! that means it’s a secret token and the corresponding value from the secrets file will be substituted.

The same concept applies to /etc/zm/zmeventnotification.ini and /var/lib/zmeventnofication/mlapi/mlapiconfig.ini

Obviously this means you can no longer have a password beginning with an exclamation mark directly in the config. It will be treated as a secret token. To work around this, create a password token in your secrets file and put the real password there.