influxdata / influxdata/telegraf

feat(outputs.influxdb_v2): report total amount of bytes sent, number of retries, number of failures

Open
#17,275 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
Go
Stars
17.8k
Forks
5.8k
Avg merge
1d 20h
Merged PRs (30d)
161

Description

### Use Case

We are interested in seeing how much data we send over the satellite exactly. Right now, we have a rough estimate, but we would like to see this more precisely. Even nicer would be per bucket/address.

I propose to add a selfstat counter that keep track of how much data was sent.

Second, some counters should also be added to keep track of failures and retries

### Expected behavior

There is a metric `internal_influxdb2,bucket=destination,url=http://localhost:8086 bytes_sent` that reports how many bytes of data have been sent to the destination, per bucket and per url. This counter also includes any failed writes.

### Actual behavior

Not available

### Additional info

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the outputs.influxdb_v2 plugin and its existing selfstat instrumentation. Trace how writes are assembled and sent, then review any nearby tests before defining coverage for bytes sent, retries, and failures, including bucket and URL labels. Done means the requested counters are reported and failed writes are included in bytes_sent.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.