The roadmap for Trickster in 2025 focuses on delivering Trickster versions 2.0 and 2.1, as well as supporting new time series applications and cloud native integrations. Additional details for Q3 and Q4 will be provided as the year progresses.
- Trickster v2.0 Beta 3 Release
- Common Time Series Format used internally for all TSDBs
- Universal HTTP Health Checker Package
- YAML config support
- Purge object from cache by path or key
- Short-term caching of non-timeseries read-only queries (e.g., generic SELECT statements)
- Support Zstd and Brotli encoding over the wire and as a cache compression format
- Ability to parallelize large timerange queries by scatter/gathering smaller sections of the main timerange.
- Cache Chunking
- Application Load Balancer
- Performant HTTP Router designed specifically for Proxies
- Resolve all known Race Conditions
- Docker & Helm Charts overhauled for Trickster 2.0
- Additional Rules Engine capabilities for more complex request routing
- Extended support for ClickHouse
- Support for InfluxDB 2.0 and Flux query syntax / payloads
- Trickster v2.0 GA Release
- Overhaul Documentation for Trickster 2.0
- Updated Grafana Dashboard for Trickster Metrics
- Trickster v2.1 Beta Release
- Kube Gateway API support
- More easily-importable Trickster packages by other projects
- Support for MySQL as Time Series
- Support for InfluxDB 3.0
- Support for Autodiscovery (e.g., Kubernetes Pod Annotations)
You can help by contributing to Trickster, or trying it out in your environment.
By giving Trickster a spin, you can help us identify and fix defects more quickly. Be sure to file issues if you find something wrong. If you can reliably reproduce the issue, provide detailed steps so that developers can more easily root-cause the issue.
If you want to contribute to Trickster, we'd love the help. Please take any issue that is not already assigned as per the contributing guidelines, or check with the maintainers to find out how best to get involved.
We are so excited to share the Trickster with the community. This is only possible through our great community of contributors, users and supporters. Thank you for all you in making this project a success!