Skip to content

Latest commit

 

History

History
56 lines (35 loc) · 2.43 KB

config.md

File metadata and controls

56 lines (35 loc) · 2.43 KB
Raw

Configuration

You can use environment vars for configuration or a configuration file (/etc/perseo-core.properties). If the two methods are used, the environment variables will have priority over the values of the configuration file.

Moreover in case of use docker container then entrypoint is also have in account. In this case the environment variables will have priority over the values docker entrypoint, and docker entrypoint will have priority over the values of of the configuration file.

Configure Perseo-core with environment vars

You can set the next environment variables:

PERSEO_FE_URL is the Perseo-fe URL. When a rule is fired, the actions will be sent to `<PERSEO_FE_URL>/actions/do

Example:

PERSEO_FE_URL=http://perseo-fe-example:9090

MAX_AGE is the expiration time for dangling rules in milliseconds.

Example:

MAX_AGE=6000

INTERNAL_TIMER_MSEC_RESOLUTION is the length of the interval (resolution) of the timer thread.

Example:

INTERNAL_TIMER_MSEC_RESOLUTION=100

Configure Perseo-core with configuration file

The configuration file is /etc/perseo-core.propeties. It a Java properties file. In this version there is not way of using other path.

# This file should be copied by deployment process
# into /etc/perseo-core.properties, with the appropiate permissions

# URL for invoking actions when a rule is fired
action.url = http://127.0.0.1:9090/actions/do

# Time in milliseconds (long) to "expire" a "dangling" rule
rule.max_age= 60000

# Length of the interval (resolution) of the timer thread
internal_timer_msec_resolution = 10

The action.url field is the URL used to make a POST in the case of a rule being fired by an incoming event. The content POSTed is the JSON representation of the derived ("complex") event.

The rule.max_age field is the value in milliseconds used as a threshold for the age of a rule to deleted safely in case of a PUT request over the rules resource does not contain the rule. All the rules older than rule.max_age will be deleted if they are not in the new set. If a rule is younger than rule.max_age it will be kept despite not being in the set sent by the PUT request.

The internal_timer_msec_resolution Length of the interval (resolution) of the timer thread. More detail in esper