influxdata/telegraf

Support for graphite pickle output

Open

#6,575 建立於 2019年10月24日

在 GitHub 查看
 (9 留言) (5 反應) (1 負責人)Go (9,892 star) (4,161 fork)batch import
area/graphitefeature requesthelp wantedplugin/serializersize/l

描述

Feature Request

Opening a feature request kicks off a discussion.

Proposal:

Implement graphite's pickle output protocol support

Current behavior:

Telegraf's graphite output plugin only supports plaintext (default TCP 2003) communications

Desired behavior:

Support graphite's pickled protocol (default TCP 2004)

Use case:

Graphite's pickled communications are much faster and more efficient for a large number of metric datapoints being submitted in one go, allowing batched submissions.

貢獻者指南

技術棧
go
領域
backenddata
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Go programming languageTelegraf plugin developmentBinary protocol understanding
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
To implement graphite pickle output, first study the existing graphite plaintext output plugin in telegraf/plugins/outputs/graphite. Understand the pickle protocol format (Python's pickle) and its batching mechanism. Then extend the plugin to support sending metrics via TCP with the pickle serialization, optionally adding a configuration option for the protocol type.
Support for graphite pickle output · influxdata/telegraf#6575 | Good First Issue