Our config file consists of the following sections:
server — General configuration parameters such as port, authorization, public_url, app logs path, etc.
log — EventNative logs all events locally and sends them to their destination in batches. This is where you configure your local temporary path and push frequency.
destinations — A set of targets where the final version of events will be stored.
synchronization_service — coordination service configuration. It is used in cluster EventNative deployments. see Scaling EventNative
notifications — notifier configuration. Server starts, system errors, and panics information will be sent to it. Currently, only Slack notifications are supported.
server:name: instance1.domain.comport: 8081auth: '193b6281-f211-47a9-b384-102cf4cd2d55'public_url: https://instances.domain.comlog:path: /home/eventnative/logs/metrics.prometheus.enabled: truegeo.maxmind_path: /home/eventnative/app/res/log:path: /home/eventnative/logs/eventsrotation_min: 5destinations:redshift:bigquery:synchronization_service:type: etcdendpoint: http://your_etcd_hostnotifications:slack:url: https://slack_web_hook_urlmeta:storage:redis:host: redis_hostport: 6379password: secret_password
All fields from the server section are optional:
Unique instance name. It is used in cluster deployments.
TCP port for the server to listen on.
see Authorization page.
Will be got from
Path to application logs. If not set, app logs will be in stdout.
Log files rotation minutes. If log.path is configured.
If an URL is set in auth section, authorization will be reloaded every auth_reload_sec seconds. see Authorization page.
If an URL is set in destinations section, destinations will be reloaded every destinations_reload_sec seconds. see Destinations.
see Admin Endpoints page.
see Application Metrics page.
Flag for disabling telemetry. EventNative collects usage metrics about how you use it and how it is working. We don't collect any customer data.
Flag for disabling log reminder banner about new EventNatvie versions availability.
EventNative supports destinations in streaming and batch modes. In the case of batch mode, all events are stored in JSON log files locally to path directory, and every rotation_min minutes they are processed and pushed to destinations. All fields from log section are optional:
Events log files path.
Log files rotation minutes.
Flag for debugging. If true - all events JSON data is written in app logs.