Skip to content

Releases: signalfx/telegraf

v1.11.1.sfx1

26 Feb 15:48
4c13f7f
Compare
Choose a tag to compare
  • Improve error logging in signalfx exporter

v1.11.1.sfx0

01 Jul 18:57
Compare
Choose a tag to compare
  • Merge upstream changes from v1.11.1

1.7.1.sfx0

05 Jul 20:31
888c034
Compare
Choose a tag to compare
  • merge changes from upstream 1.7.1
  • enhanced test coverage for SignalFx output plugin
  • build with golang:1.9.7

v1.7.0.sfx1

27 Jun 23:36
e2e44a3
Compare
Choose a tag to compare
  • Resolve issue parsing metrics with fields named "value"

v1.7.0.sfx0

21 Jun 13:35
Compare
Choose a tag to compare
  • update fork to Telegraf 1.7.0

v1.6.3.sfx0

05 Jun 20:42
Compare
Choose a tag to compare
  • Update fork to Telegraf 1.6.3

1.6.0-sfx0

20 Apr 15:00
5e2b7d1
Compare
Choose a tag to compare
  • update fork to Telegraf 1.6.0
  • add option to disable process collection in the SignalFx metadata plugin
  • added comment to SignalFx utilization plugin config indicating that period must be 2x the collection interval

1.5.1.sfx2

13 Mar 21:21
b630d60
Compare
Choose a tag to compare
  • Minor bug fix in SignalFx output plugin. Metric types that cannot be mapped will default to gauge.

1.5.1.sfx1

16 Jan 16:14
625d9e5
Compare
Choose a tag to compare

This release fixes a minor bug in the SignalFx output plugin where metrics were emitted prematurely before filling the configured batch size during each collection interval.

v1.5.1.sfx0

12 Jan 14:51
e875f44
Compare
Choose a tag to compare
  • Rebase with upstream v1.5.1 release
  • Fixed bug in SignalFx Utilization plugin where disk.summary_utilization was reported without a hostname
  • Distribute SignalFx metadata and process info collection across multiple go routines
  • Batch metrics when outputting to SignalFx