Jitsu is an open-source Segment alternative. Fully-scriptable data ingestion engine for modern data teams. Set-up a real-time data pipeline in minutes, not days
[!NOTE] Upgrading from Jitsu 2.4 requires infrastructure changes. Details below.
We've made a couple of significant changes:
Redis is no longer in the picture.
For Live Events, we didn't set up a migration path because we see it as a nice-to-have, not a must-have.
If Persistent Storage is part of your setup, enable "double reading" by setting up both MONGODB_URL
and REDIS_URL
. Jitsu will read from both but only write to MongoDB. This way, you won't lose any data during the transition. After a while, when all your data is happily living in MongoDB, you can say goodbye to Redis.
It's best to switch to MongoDB and ClickHouse sooner rather than later. We're planning to drop Redis support after a few more releases, so keep an eye out.
For detailed configuration instructions and further assistance, please se the configuration guide or the reference Compose file.
This hotfix release includes the following changes:
console
: fixed bug with Sign In page not working on some setupsconsole
: Live Events now has the toggle to enable Functions debug logsGTM destination
fix for GTM tag initializationrotor
: another fix for graceful shutdownThis hotfix release includes the following changes:
console
: fixed bug in anonymous telemetry system that could cause error and timeout on some UI operations.rotor
: token authorization can be enabled for rotor endpointsrotor
: graceful shutdown now must work properly@jitsu/js
. Jitsu processing queue now accepts arrays in addition to callbacksAUTH_TOKENS
for all components.This hotfix release includes the following changes:
0.0.0.0
) - may be necessary for productions setupsThis release offers a refinement to self-hosted deployment process among with bunch of other fixes and improvements.
Due to number of changes migration from previous docker-compose setup is not supported
Here is the list of the most significant changes:
✅ Event Ingestion API was moved to the dedicated service written in Go language: jitsucom/ingest
✅ GitHub OAuth app is no longer required to setup Jitsu
✅ Improved performance of jitsucom/rotor
service. Now it supports concurrent execution of multiple functions
✅ Simplified setup of Connector Syncs with much shorter Minikube example
✅ jitsucom/console
image was significantly reduced in size, from 900M
to 172M
✅ Kafka image upgraded to the fresh one bitnami/kafka:3.6.0
This hotfix release includes the following changes:
This hotfix release includes the following changes:
17
. Now API version can be overridden with environment variable FACEBOOK_MARKETING_API_VERSION
This hotfix release includes the following changes:
This hotfix release includes the following changes:
This hotfix release includes the following changes:
In multi-project setups it is now possible to select a 'global destination' that will capture events from all API keys in all projects. Read more