influxdb

How does one upgrade from v2 beta to the latest v2? The docs for doing that seem to no longer exist https://github.com/influxdata/influxdb/issues/24393

https://github.com/influxdata/influxdb The non-reddit link target

Who's upstream? Open source project and publicly accessible upstream? Yep. They're likely MIT licensed in accordance with the CLA. Internal company copy of an MIT project? Unlikely unless legal says they are. If the organization that I worked for made an internal copy of Influxdb ( https://github.com/influxdata/influxdb ), my contributions to the private and internally hosted copy are not inherently MIT licensed too and furthermore don't need to be redistributed. If those changes were submitted upstream to the influxdata/influxdb repo, and I signed the CLA with them - then yes they would be. What's more, if I left the organization, then I don't necessarily have a right to the contributions that I made to the private and internally hosted copy's codebase.

ListenBrainz dev here. We wanted stuff like the ability to do stuff like "DELETE FROM measurement where field = blah" and that support didn't exist last time we looked. [0] Another thing that's not mentioned in the post but was a pain point for us was that it's not easy to query for fields with "null" values [1]. I figure a lot of our pain might be because we're not as good at Influx as we are at PostgreSQL. We've been running MusicBrainz[2] for ~18 years on PostgreSQL, that knowledge will hopefully transfer over a little with Timescale. [0]: https://github.com/influxdata/influxdb/issues/3210 [1]: https://github.com/influxdata/docs.influxdata.com/issues/717 [2]: https://musicbrainz.org

Does TimescaleDB support automated downsampling using various functions (min/max/mean/avg) and then during querying automatically picking the correct downsampled data? This is the biggest issue that I and others have with InfluxDB, that it doesn't do that, so the only convenient way to use it is just to expire all data outside the retention policy. Ticket here: https://github.com/influxdata/influxdb/issues/7198

if err != nil return err if err != nil return err if err != nil return err https://github.com/docker/cli/search?q=%22if+err+%21%3D+nil%... https://github.com/kubernetes/kubernetes/search?q=%22if+err+... https://github.com/coreos/etcd/search?q=%22return+err%22&uns... https://github.com/influxdata/influxdb/search?q=%22if+err+%2... The reality of Go's error handling is that you just implement exactly what exception bubbling does painfully by hand.

After running InfluxDB in production for a bit more than year, here's some issues from top of my mind we ran have into: # Common - All: Various documentation issues - Including versioning in the documents - Influx/Kapacitor: Cannot join values in Influx, but you can Kapacitor (but not dynamically) - Available in InfluxDB 1.6. now! # InfluxDB - Influx: GroupTag not grouping https://github.com/influxdata/kapacitor/pull/1773 - Influx: last() is really slow https://github.com/influxdata/influxdb/issues/8997 - Influx: Cannot update / edit tags https://github.com/influxdata/influxdb/issues/3904 - Apparently you can have tags and fields with the same names which bump up the query times by 1000x times, without ever knowing what's wrong (fixable by adding ::tag to the value) - Cannot incrementally restore incrementally backed up databases (w

Honest question: how do people use influxdb for monitoring and alerting? Our metrics feed into influx, and I cannot get answers to simple questions like “what is the failure rate” because arithmetic across measurements isn't possible [0]. I could shoehorn things into a schema to make it work, but in the limit I end up with one mega measurement. [0]: https://github.com/influxdata/influxdb/issues/3552

I shouldn't have said data corruption, I just meant time corruption: https://github.com/influxdata/influxdb/issues/8424 I was never able to fix this.

Granted, they don't have a link to the GitHub page on the blog post itself, but it's open source software. https://github.com/influxdata/influxdb/releases

The implication of an MIT license is that anyone can use or sell your work with attribution. If the contributor was not happy with that, or unhappy with getting a free db worked on by other people, they simply wouldn't contribute. Since they did contribute on those terms, we have no reason to think they want to be paid. https://github.com/influxdata/influxdb/blob/master/LICENSE

Yep, we're very focused on solving the cardinality problem now. See these for some details about how we're thinking about it: https://github.com/influxdata/influxdb/pull/7175 https://github.com/influxdata/influxdb/pull/7174 https://github.com/influxdata/influxdb/pull/7186 https://github.com/influxdata/influxdb/pull/7264