3 ms·
Looks good. There are two things that will be really important: - How is data imported? It would be great to be able to set up custom SQL queries, CSV imports,
by CGamesPlay 12y ago
Looks good. There are two things that will be really important:
- How is data imported? It would be great to be able to set up custom SQL queries, CSV imports, and other service gateways to do analytics on.
- How do I define graphs? I'll want to be able to do time-series, but easily switch between day/week/month/year resolution, and create trailing period averages without having to think about it.
I signed up for the beta. I'd love to play around and do some deep diving on stats we have collected.
- viggity 12y agoRight now we only support CSVs they get served directly from blob storage to the browser (without going through our webserver). We obviously want to expand on those options, but CORs makes serving from internal company data sources a PITA. We could use our domain as a proxy to the relevant info, but that has its own issues (auth, perf). I'm sure we'll be able to work it out though. Automated CSV imports will probably be the best way to do things initially. When you import your CSV, we take educated guesses about the data in each column (number, category, date), but you can change it if necessary (sometimes numbers should be treated like categories). We give you the ability to group dates by day of week and month. Month-year isn't in there yet, but should be by launch. It works best one un-aggregated source data (since we do so all the fine level aggregation ourselves in the browser). Dealing with weighted averages is possible and we've done it a lot in custom work, but machete doesn't yet have support for it. Thanks for the kind words :)