News for hackers. Stuff that matters.
Re:Be cautious about using Chartio (or at least, don’t follo... by gkoberger on Saturday May 11, 2013 @01:21AM (#5689775)
Of course giving out access is probably a bad idea -- so what would be a good alternative for them to do instead?
Re:Be cautious about using Chartio (or at least, don’t follo... by swisspol on Saturday May 11, 2013 @02:00AM (#5689839)
In our case we set up a dedicated cheap database server only for ChartIO. Then we have a script that copies to it analytics data from our production servers every few hours (while also anonymizing what needs to be just to be extra safe).
Re:Be cautious about using Chartio (or at least, don’t follo... by john_w_t_b on Saturday May 11, 2013 @02:11AM (#5689863)
This is a good approach. I work with ERP systems for large companies, and it's typical to separate the transactional database (OLTP) from the analytics database (OLAP). There's usually a replication process to copy transactions into the reporting system.
Re:Be cautious about using Chartio (or at least, don’t follo... by thingsilearned on Saturday May 11, 2013 @02:13AM (#5689867)
Great use case! We don't support an API that you can push data to, but that's because whatever API we build, it would never be easier to learn or have as much language support than just spinning up a PostgreSQL instance and writing the data to it. Quite a few of our customers use us this way.
Re:Be cautious about using Chartio (or at least, don’t follo... by swisspol on Saturday May 11, 2013 @02:35AM (#5689910)
You guys should really suggest this approach in the setup guide (it can be phrased in a way not to scare potential users). The alternative of directly accessing production database servers is really risky.
Re:Be cautious about using Chartio (or at least, don’t follo... by thingsilearned on Saturday May 11, 2013 @02:47AM (#5689939)
Agreed. I'll work on it.
Re:Be cautious about using Chartio (or at least, don’t follo... by rdl on Tuesday May 14, 2013 @07:01AM (#5704055)
This seems like what you'd do just to protect your production server from some crazy load/etc. issues from analysis, too. I can't imagine giving read-only access to a core rw database server to anything which didn't need it.
Re:Be cautious about using Chartio (or at least, don’t follo... by tixocloud on Saturday May 11, 2013 @07:42AM (#5690340)
+1 for getting non-operational stuff off of the production servers. In my opinion, production servers should be left untouched by analytics and what not. I'd prefer not tying up resources that could better serve customers.
Re:Be cautious about using Chartio (or at least, don’t follo... by aiiane on Saturday May 11, 2013 @02:25AM (#5689886)
Yep. That's the kind of approach I'd like to see Chartio recommending (or at least, providing suggestions for).
Re:Be cautious about using Chartio (or at least, don’t follo... by kodablah on Saturday May 11, 2013 @01:27AM (#5689785)
These types of services just can't be SaaS. Ideally they would provide a prebuilt VM to drop in your environment (like GitHub Enterprise does). I had been struggling with the same quandry with regards to a code review system and a monitoring system I have been working on.
Re:Be cautious about using Chartio (or at least, don’t follo... by btown on Saturday May 11, 2013 @01:43AM (#5689807)
One might argue that a self-updating prebuilt VM is functionally equivalent to a SaaS offering.
Re:Be cautious about using Chartio (or at least, don’t follo... by thingsilearned on Saturday May 11, 2013 @02:04AM (#5689848)
Sadly the alternative is data warehousing (which all of our competitors do). Its the worst solution as it

1. gives a copy of your data to someone else 2. is legally questionably still your data 3. is stagnant (as you usually only backup once a week) 4. there is no way to track where that data goes

Re:Be cautious about using Chartio (or at least, don’t follo... by swisspol on Saturday May 11, 2013 @02:43AM (#5689930)
Well, I'd say 1, 2 and 4 also apply to ChartIO ;) We like your service after comparing various ones but for us the advantage vs data warehousing is a much easier setup and UX.