Currently, the Analytics Engine data storage is three months. Can the storage duration be extended b
Currently, the Analytics Engine data storage is three months. Can the storage duration be extended by payment in the future?
Vthe only AE limit I've seen increased is the 25 rows per invocation :/
面Will the data from three months ago not be cleared?
Vanalytics-engine (Individually, per data point) Once an data point goes past 92 days, it will get deleted
VThe team is currently tracking feedback for longer retention, but no plans if or when at this moment
VFor now or If they do, until that point, I would suggest have a daily cron searching for data points past the 1 or 2 month mark and save it to a DB (like D1) for longer storage. Or (depending on your use case) flatten it into a daily json file (all the data points in a day) an save into object storage (like R2)
RThanks!! 
WI can't activate the Analytics Engine, does anyone know how to solve this?
workers-and-pages-helpCannot enable Worker Analytics Engine (Code:1000, Internal Server Error)
workers-and-pages-helpCannot enable Worker Analytics Engine (Code:1000, Internal Server Error)
Wty, DMed you
WYep looks good to me, you could also just avoid the blobs and know the index 0 is reads and index 1 is writes
But really up to you
But really up to you
Dblobs are also just columns, you can store eg. strings in them, like a country code, username or anything else
MI recently discovered Workers Analytics Engine. Can someone explain to me why it is so expensive? $0.25 seems a bit high for 1 Million write-requests, especially when compared to D1!
UNot to mention 1 insert query on D1 != 1 write but equals 1 + all indexes so it will be quite a bit cheaper for writes
RAre there any limitations on 'writeDataPoint' per second?
EHow has the feedback been so far?
3 Months is fine for non-important data (such as referral link tracking), but for anything else we'd still need to maintain our Kafka -> Druid
3 Months is fine for non-important data (such as referral link tracking), but for anything else we'd still need to maintain our Kafka -> Druid
ESimply paying e.g. for GB/mo on everything older than 3 months would be amazing from client perspective, since it doesn't represent the increase in load for the read requests it's probably not a real solution though
Mthis would be great
JIs there any way to accomplish using AE?
JIt seems to just throw right now
JGROUP BY ?
JOh huh, yeah that'll work nicely, thanks
OIs there any way to transfer data from one dataset to another?
HUnfortunately, no. You cannot manipulate data, only insert it via the Binding
OGot it thanks. Do you have it in the backlog or something? Its not critical but nice feature to have
HI’m not sure, tbh(I’m not on the AE team). I can try to check, but not sure if/when I can get a response back
ORoger that 
thank you for clarifications!
thank you for clarifications!
HIt shouldn't require a waitlist?
HHave you clicked the setup button on the dashboard?
UIt is a bit hidden yeah but also open beta = no waitlist. Wouldnt be very open if it was waitlisted 
Wyes
WWrite sampling is per index
WI'd recommend reading this though: https://developers.cloudflare.com/analytics/faq/wae-faqs/#could-i-just-use-many-unique-index-values-to-get-better-unique-counts
WLots of info in the docs, highly recommend the read
Ihow can you build event system or audit system production grade with 3month retention ... makes little sense
RHey, how long is the data stored?