telegraf

Wow, that's massive. I guess it's inevitable that a popular piece of open-source software for end-users will be compelled to accrue dependencies due to popular demand for features that require them. I feel Telegraf made a good compromise: out of the box, it comes with a _ton_ of stuff[1] to monitor everything, but they make it possible to build only with pieces that you need via build tags, and even provide a tool to extract said tags from your telegraf config[2]. But lots of supply-chain security stuff assume everything in go.mod is used, so that can results in a lot of noise. [1] https://github.com/influxdata/telegraf/blob/master/go.mod [2] https://github.com/influxdata/telegraf/tree/master/tools/cus...

Telegraf can expose Prometheus-scrapable metrics and has a DNS plugin that can monitor several targets with a single config stanza - which was a problem with black box exporter according to TFA. Maybe it could be an alternative? https://github.com/influxdata/telegraf/blob/release-1.29/plu...

Back when I was using AWS CloudFormation, I found a need to use Troposphere [0] to do some logic that couldn't be done in CloudFormation itself. When I switched to Terraform most of those problems went away since there is even better ways to perform simple programming logic in it. Maybe there are some use cases where you still need to perform logic outside of Terraform where AsCode could be useful to some people. I've seen the Starlark configuration language used in other places, such as Telegraf [0], but I think this is an interesting use of it. [0] https://troposphere.readthedocs.io/en/latest/index.html [1] https://github.com/influxdata/telegraf/blob/master/plugins/p...

I would use telegraf (https://github.com/influxdata/telegraf) to gather the metrics you want from your servers. It has built-in functions to get metrics like disk usage, cpu, etc... From there I would export those metrics to a grafana+influxdb setup. But honestly this is because that's what I'm used to professionally. There might be simpler solutions around.

Note that you can gather and display logs with this same stack, Telegraf includes a plugin to consume syslog output: https://github.com/influxdata/telegraf/blob/release-1.14/plu... and then you can do something like this on Grafana: https://grafana.com/api/dashboards/12433/images/9004/image The one thing I would add to this guide is enabling HTTPS for the whole stack, if you are transmitting over the public internet. Fortunately, it is quite straightforward (and free) with Let's Encrypt.

see also https://github.com/grafana/grafana/issues/28097 right now it is streamed to the UI (not persisted), though we have hooks in place to allow persisting the live data into Grafana cloud offerings. a few days ago our PR for websocket output in telegraf was merged, and available in v1.19.0-rc0 :) https://github.com/influxdata/telegraf/pull/9188 https://github.com/influxdata/telegraf/releases/tag/v1.19.0-...

One of our active community members took over the effort to merge PostgreSQL/TimescaleDB support into telegraf here, so hopefully that can make progress: https://github.com/influxdata/telegraf/pull/8651

I'm currently using InfluxDB (v1 not v2) and I've looked into switching over to Timescale DB. Currently I'm stuck on figuring out how to get data into TimescaleDB. My company makes heavy use of Telegraf, which is a natural fit for InfluxDB, but not so much for TimescaleDB. The original pull request for the Telegraf plugin for Postgres/TimescaleDB was closed because the author was non-responsive: https://github.com/influxdata/telegraf/pull/3428 I can even write data to it using simple TCP or UDP tools like netcat or curl. And for some cases I have simple scripts that do exactly that. TimescaleDB, on the other hand, requires some sort of Postgres client. What do you, or other people, use for writing data into TimescaleDB?

InfluxDB has a template to aid with monitoring a postgres instances[0]. I wonder if the Telegraf Plugin[1] could be enhanced to use more of these metrics, and then the template could be enhanced as well? [0] https://github.com/influxdata/community-templates/tree/maste... [1] https://github.com/influxdata/telegraf/tree/master/plugins/i...

I was interested in using TimescaleDB, but I'd want to use Telegraf (or something good as it is) to feed data into TimescaleDB. The TimescaleDB folks say that the pull-request for their Telegraf plugin just needs to be merged, but that doesn't seem to be the case. The pull request needs changes and the original submitter is unresponsive. Now the pull request is labeled as "help wanted". [1] What do people use to send metrics into TimescaleDB? [1] https://github.com/influxdata/telegraf/pull/3428

I've been using InfluxDB, but not satisifed with limited InfluxQL, or over-complicated Flux query languages. I love Postgres so TimescaleDB looks awesome. The main issue I've got is how to actually get data into TimescaleDB. We use telegraf right now, but the telegraf Postgres output pull request still hasn't been merged: https://github.com/influxdata/telegraf/pull/3428 Any progress on this?

telegraf supports some summarization https://github.com/influxdata/telegraf#aggregator-plugins

How does this compare to telegraf? https://github.com/influxdata/telegraf Biggest thing that pops out to me is LUA engine (seems amazing :) )

I recently opened a PR to add support for pushing metrics to Cortex from Telegraf, so you don't need Prometheus as the agent: https://github.com/influxdata/telegraf/pull/5003 NB I'm the main author of Cortex...