trickstercache / trickster

Open Source HTTP Reverse Proxy Cache and Time Series Dashboard Accelerator
https://trickstercache.org
Apache License 2.0
1.98k stars 177 forks source link

AWS Timestream support #684

Open ppbrown opened 1 year ago

ppbrown commented 1 year ago

AWS Timestream is not on the list of officially support timeseries databases. Any plans? Alternatively, any specific plans to exclude it?

jnichols-git commented 1 year ago

To the best of my knowledge, the team doesn't have immediate plans to develop AWS Timestream support. If we take steps into AWS, the first stop is likely to be CloudWatch, since it sees significant use on any stack including AWS. Timestream isn't specifically excluded, but it's also not currently a priority.

ppbrown commented 1 year ago

fair enough. it is a priority to Me though, so i’ll probably try to port it myself :)

Any pointers appreciated.

On Wed, Jul 19, 2023 at 8:39 PM Jake Nichols @.***> wrote:

To the best of my knowledge, the team doesn't have immediate plans to develop AWS Timestream support. If we take steps into AWS, the first stop is likely to be CloudWatch, since it sees significant use on any stack including AWS. Timestream isn't specifically excluded, but it's also not currently a priority.

— Reply to this email directly, view it on GitHub https://github.com/trickstercache/trickster/issues/684#issuecomment-1643055270, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANEV6POLYEKV6U5JC35R33XRCR75ANCNFSM6AAAAAA2PEHQOY . You are receiving this because you authored the thread.Message ID: @.***>

jnichols-git commented 1 year ago

Right, sorry, I should have used more descriptive language! I can't speak for individuals on the team, but generally, we've got our sights on specific enhancements that we'd like to make, and our personal time goes towards those. We always have an eye out for contributors and contributions, and will happily help support development efforts.

Much of the platform support revolves around interpretation and transformation of requests. Trickster needs to be able to take a query for the last 24h of data, determined that it cached the first 12h of those, and then modify the query to only request the other half (for example). I'd strongly suggest reading through the implementations of a few TSDBs to see how this is accomplished in production use-cases.

Feel free to ask further questions here; I'll provide support as I'm able.