Govern, transform, filter, and route your logs & analytics events
to multiple destinations from your applications via remote configuration.
to multiple destinations from your applications via remote configuration.
Website | Documentation | Issues | Contributing | Changelog
Three simple steps to visualize it:
- Manage your Eventvisor project in a Git repository
- Build and upload datafiles (static JSON files) to your CDN or custom server
- Fetch the datafile, and start tracking events with the SDK
- A Git repository for managing your project declaratively
- A CI/CD pipeline (like GitHub Actions) for building and uploading the datafiles
- A CDN or custom server for serving the generated datafiles
Eventvisor SDKs will take care of the rest for you.
There are several use cases where Eventvisor can be useful, especially if you are a medium to large product engineering organization:
- Governance of analytics events
- Conditionally routing events to different vendors
- Migrating from one vendor to another with ease incrementally
- Validation warnings for tracking events in wrong shapes
- Deprecating events safely for multiple teams
- Bringing order in a microfrontends architecture
- Saving data ingestion costs via advanced filtering and sampling
- Marketing pixels with engineering oversight
Visit the website to learn more: https://eventvisor.org
MIT © Fahad Heylaal

