Template configuration for Kafka can be found here.
You can also now include Snowplow Monitoring in the application. This is setup through an optional section at the bottom of the config. You will need to ammend:
monitoring.snowplow.collectorUriinsert your snowplow collector URI here.
monitoring.snowplow.appIdthe app-id used in decorating the events sent.
If you do not wish to include Snowplow Monitoring please remove the entire
monitoring section from the config.
You will also need a JSON configuration for the Iglu resolver used to look up JSON schemas. A sample configuration is available here.
You may wish to use Snowplow's configurable enrichments. To do this, create a directory of enrichment JSONs. For each configurable enrichment you wish to use, the enrichments directory should contain a .json file with a configuration JSON for that enrichment. When you come to run Stream Enrich you can then pass in the path to this directory using the --enrichments parameter.
Example configurations could be found at GitHub repository.
See the documentation on configuring enrichments for details on the available enrichments.
Configuration in DynamoDB
When using with Kinesis, it’s possible to store the configuration of the resolver and/or enrichments in DynamoDB. In this case
dynamodb: prefix needs to be used in place of
--resolver dynamodb:eu-west-1/configuration_table/resolver \
In this case it’s assumed that the enrichments and resolver are stored in a table named
configuration_table in eu-west-1, that the key for that table is
id, that the resolver JSON is stored in an item whose key has value
resolver, and the enrichments are stored in items whose keys have values beginning with
In the example above
configuration_table is a table with 2 columns :
There must be one line with
id and the content in the
enrichment_ is the prefix used in the
id column to configure an enrichment, and then the content must be put in the
json column. Here is the list of all the enrichments (with
enrichment_ prefix) in
id column :