InfluxDB 1.0 GA Released: A Retrospective and What’s Next • Hacker News Board

Re: InfluxDB 1.0 GA Released: A Retrospective and What’s Next

#81

Post by scrollaway » Fri, Sep 09, 2016, 4:45 PM UTC

boduh wrote: post #79

scrollaway wrote: post #19

Influx is absolutely amazing. We're using it along with grafana to store and display our desktop and web apps' analytics (it completely replaced GA), store and display HTTP health analytics (piping custom uwsgi request logger into UDP input), and do continuous analysis of Hearthstone games. It's incredibly fast and the grafana/influx/telegraf stack is really cool to play with. Highly recommended.

I am new to InfluxDB but I am interested in using it for some desktop app analytics. Are there any resources that you would recommend I start with? Maybe some from your own experience? How hard was for you to start using it for desktop app analytics?

Logging datapoints into influx is pretty straightforward. For example, logging every time your app is started, adding a tag for the platform, the region, logging datapoints whenever some important settings are toggled, etc.

Once you have this data, set up grafana and build some graphs to query it. Grafana has a graphical query builder, and internally it's essentially a sql-like. There's good tutorials in the influx/grafana docs for all that.

Re: InfluxDB 1.0 GA Released: A Retrospective and What’s Next

#82

Post by brazzledazzle » Fri, Sep 09, 2016, 8:46 PM UTC

dozzie wrote: post #77

brazzledazzle wrote: post #75

Earlier quoted context omitted.

You can't rebuild a server from backups? No snark, just wondering what I'm missing.

First, you need to predict that you'll need to backup software . Typically people back up their data , as software can be reinstalled (until it can't, because package retention policies). Then you need to ensure you either have enough backup space or don't store 30 copies of the same thing, one for each server (it quite often happens that OS and software weigh much more than data they host). Second, restoring from ba…

Sorry, I assumed you were talking about rebuilding a local mirror repository that you use to provide software for your other hosts. That would just be one backup of the packages and meta data that you can restore. Is there a reason you can't mirror the packages and repositories you use?

Re: InfluxDB 1.0 GA Released: A Retrospective and What’s Next

#83

Post by dozzie » Fri, Sep 09, 2016, 9:46 PM UTC

brazzledazzle wrote: post #82

dozzie wrote: post #77

Earlier quoted context omitted.

First, you need to predict that you'll need to backup software . Typically people back up their data , as software can be reinstalled (until it can't, because package retention policies). Then you need to ensure you either have enough backup space or don't store 30 copies of the same thing, one for each server (it quite often happens that OS and software weigh much more than data they host). Second, restoring from ba…

Sorry, I assumed you were talking about rebuilding a local mirror repository that you use to provide software for your other hosts. That would just be one backup of the packages and meta data that you can restore. Is there a reason you can't mirror the packages and repositories you use?

Just mirroring doesn't change the retention policy (unless the term has changed its meaning in recent fifteen years), so it won't do. But this is moves the discussion to spoken language semantics, which I don't feel like pushing too far.

My point with the packages is that you need your own copy that you have control over, so they don't disappear unexpectedly. Pulling already-built packages from some other repository would be fine from this standpoint, though I prefer rebuilding them myself and keeping along with source packages.