influxdata/telegraf

Support for graphite pickle output

Open

#6575 opened on Oct 24, 2019

View on GitHub
 (9 comments) (5 reactions) (1 assignee)Go (9,892 stars) (4,161 forks)batch import
area/graphitefeature requesthelp wantedplugin/serializersize/l

Description

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.

Contributor guide

Tech stack
go
Domain
backenddata
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programming languageTelegraf plugin developmentBinary protocol understanding
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
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.