After that, you can start to use this schema registry in your Snowplow Mini instance.
Configurable enrichments are an important part of Snowplow. We added custom enrichments to Snowplow Mini in the previous release.
With this release, we’re adding the ability to upload custom enrichments directly through the Control Plane, like so:
Another shortcoming we’re addressing with this release is the ability to add or change the internal Iglu schema registry’s API key, again through the Control Plane.
This replaces the cumbersome process of having to specify the initial API key through the user data script or changing it by SSHing into the box. Use the new functionality like so:
In 0.3.0, we made HTTP basic authentication for Snowplow Mini mandatory. We’re making changing those credentials available in the Control Plane with this release:
Lastly, we’re improving on the TLS support introduced in 0.3.0, by letting you specify the the Snowplow Mini’s domain name via the Control Plane, thus:
Up until this release, we were using Unix named pipes for inter process communication. Even though they are easy and straightforward to use, they were causing unexpected behaviors, and were difficult to debug and reason about.
Therefore, we decided to use NSQ instead of named pipes, making use of the new NSQ functionality released in R96 Zeugma. This migration will make the pipeline more robust; this change has not caused any user-visible changes.
Before this release, Snowplow Mini users had to create index mappings for their Snowplow data manually in Kibana. Creating those index mapping is now handled automatically during the Snowplow Mini setup; users will now start to see events appearing directly in Kibana.
Version 0.4.0 also includes some internal changes and minor enhancements under the hood, including:
To learn more about getting started with Snowplow Mini, check out the Quickstart guide.
If you run into any problems, please raise a bug or get in touch with us through the usual channels.