Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

influxdata.com

Post reply on HN
Print view View original

21–30 of 83 posts

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

#21

Post by fabian2k »

I played around with InfluxDB, Telegraf and Grafana a while ago, and it worked very nicely for the basic stuff I tried.

One thing in Telegraf where I didn't figure out a good solution was a way to parse arbitrary log files and generate data points and/or annotations from them.

There is a particularly annoying log file format from a proprietary application containing data I like to monitor which contains time series values in a multiline format as well as error messages. What I'd like to do is to have Telegraf tail the log file and pass it through a script that generates actual influxdb data from that. So something similar like the telegraf tail plugin, but with a data transformation in between.

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

#22

Post by pauldix »

fabian2k wrote: post #21

I played around with InfluxDB, Telegraf and Grafana a while ago, and it worked very nicely for the basic stuff I tried. One thing in Telegraf where I didn't figure out a good solution was a way to parse arbitrary log files and generate data points and/or annotations from them. There is a particularly annoying log file format from a proprietary application containing data I like to monitor which contains time series v…

We added log parsing to Telegraf a month or so ago. See here for more details:

https://github.com/influxdata/telegraf/tree/master/plugins/i...

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

#23

Post by joshpadnick »

pauldix wrote: post #22
fabian2k wrote: post #21

I played around with InfluxDB, Telegraf and Grafana a while ago, and it worked very nicely for the basic stuff I tried. One thing in Telegraf where I didn't figure out a good solution was a way to parse arbitrary log files and generate data points and/or annotations from them. There is a particularly annoying log file format from a proprietary application containing data I like to monitor which contains time series v…

We added log parsing to Telegraf a month or so ago. See here for more details: https://github.com/influxdata/telegraf/tree/master/plugins/i...

I'm wondering if Telegraf is a legit replacement for logstash or fluentd for shipping logs. I couldn't find this info from docs, so do you know if:

- it supports multi-line logs (e.g. java stack traces)

- it can output to elasticsearch (didn't see an output plugin)

- there's any solution for reading docker logs (looks like docker metrics are supported)

- any other critical logstash functionality missing?

If it doesn't support the classic Elasticsearch output, where are telegraf log users typically outputting logs to?

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

#24

Post by zenlot »

While talking about InfluxDB people should not forget about their beta release of clustering to attract more users and then making it just enterprise. And no, it's not an argument that this is the only way to get paid in open source. Users should be careful while adopting InfluxDB as Influxdata does not clearly elaborate their plans on the product.

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

#26

Post by pauldix »

gorodetsky wrote: post #25

I still don't quite understand Chronograf: I know that you want to own the stack but are there any major advantages over Grafana? Sorry if I'm being ignorant but I couldn't find anything that would've made me think one way or another.

We're working on a re-envisioned Chronograf. The goal is to have something that's complementary to Grafana. Most of our users love Grafana and that's good.

The next version of Chronograf, coming later this year, will be a re-envisioned and fully open source version. It won’t be about dashboards, it’ll be about an out of the box user experience for monitoring containers, Kubernetes, and Docker Swarm.

We're actually looking for early testers that want to walk through wireframes and work with us on making a great out of the box experience for what will be a fully open source monitoring stack.

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

#27

Post by zenlot »

pauldix wrote: post #26
gorodetsky wrote: post #25

I still don't quite understand Chronograf: I know that you want to own the stack but are there any major advantages over Grafana? Sorry if I'm being ignorant but I couldn't find anything that would've made me think one way or another.

We're working on a re-envisioned Chronograf. The goal is to have something that's complementary to Grafana. Most of our users love Grafana and that's good. The next version of Chronograf, coming later this year, will be a re-envisioned and fully open source version. It won’t be about dashboards, it’ll be about an out of the box user experience for monitoring containers, Kubernetes, and Docker Swarm. We're actually lo…

Until you'll decide to make some of the features just for enterprise, as you did with InfluxDB?

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

#29

Post by pauldix »

joshpadnick wrote: post #23
pauldix wrote: post #22

Earlier quoted context omitted.

We added log parsing to Telegraf a month or so ago. See here for more details: https://github.com/influxdata/telegraf/tree/master/plugins/i...

I'm wondering if Telegraf is a legit replacement for logstash or fluentd for shipping logs. I couldn't find this info from docs, so do you know if: - it supports multi-line logs (e.g. java stack traces) - it can output to elasticsearch (didn't see an output plugin) - there's any solution for reading docker logs (looks like docker metrics are supported) - any other critical logstash functionality missing? If it doesn'…

Telegraf users are generally parsing the logs into structured metrics and events that go into InfluxDB.

Not sure that it supports multi-line logs or docker logs. I'll have to look into it, but both should probably be done if they're not already there.

For ES output, we're happy to take PRs for other output plugins. There are people using Telegraf that aren't using InfluxDB. That's fine and we're happy to have an open source collector that others use and contribute to.

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

#30

Post by aleksi »

> We had been grappling with what we should do for most of August 2013 and had another idea that I planned to debut at Monitorama in Berlin in late September. The conference was all about monitoring and I thought it would be a good place to find a receptive audience for a new monitoring product.

What was it?

Post reply on HN