Yali
Throughput from each microservice aggregated into a clear overview of the overall pipeline health and topology over time.
Use anomaly detection on the data in-stream to identify likely failure to track events.
Enable customers to easily test data models locally during development. Test changes to existing data models that are already deployed to production via data modeling UI.
Support for running Snowplow natively in Azure
Update the enriched event format to make it much easier to work with in different storage target. Include: * Improved serialization e.g. Avro, Protobuf * CloudEvent support
It is possible to specify one or more entities are required with individual events. The presence of these entities is enforced by the pipeline at the validation step.
Change-log would include: * Updates to microservices deployed * Changes to configuration e.g enrichments, new destinations * Scaling events * Schemas published to development and production
In-stream identity resolution carried out as an (optional) part of the Snowplow pipeline. Identity stitching logic should be configurable and transparent.
Neo4J complains about the maximum number of file opens on loading / restarting: ``` vagrant@precise64:/etc/init.d$ sudo ./neo4j-service restart * Restarting Neo4j Graph Database neo4j WARNING: Max 1024 open files allowed,...
This is needed to run emr-cli