Note that this release also bumps Iglu Server to
0.3.0 which introduced a new configuration parameter
repo-server.baseURL meaning that our users should upload their own Iglu Server config file with
repo-server.baseURL set to
<snowplow-mini-deployment-address>/iglu-server, if they want to use Swagger UI of Iglu Server. Note that you should omit the protocol (i.e. http(s)://), because Swagger UI will automatically prepend that.
Most of the recent issues we faced with Snowplow Mini were mostly due to running very old versions of Elasticsearch (1.7.5) and Kibana (4.0.1). Although we considered renewing them before, there was a tradeoff between heavier resource usage and having brand-new Elasticsearch stack. We finally made the call and decided to bump their versions to
6.3.1 at the expense of using more resource, RAM especially.
Until today, Snowplow Mini was being used inside AWS’s
t2.medium instances and it served well for demonstration purposes. However, we observed that Snowplow Mini started exceeding its initial motivation and machine resources started to become an obstacle, causing issues with Elasticsearch etc. This is why,
0.6.0 is available at 3 different sizes.
large: Same image published so far. Elasticsearch has
4gheap size and Snowplow apps has
xlarge: Double the large image. Elasticsearch has
8gheap size and Snowplow apps has
xxlarge: Double the xlarge image. Elasticsearch has
16gheap size and Snowplow apps has
What’s more, as part of bumping Elasticsearch version to
6.x, we had to remove Head plugin since site plugins are removed from Elasticsearch as of
5.x. However, Head plugin can be used as Google Chrome extension.
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 join our gitter room or get in touch with us through the usual channels.