influxdata / influxdata/influxdb

Prometheus data writes too many data tags remotely, resulting in high memory usage. I hope to control the tag where the monitoring data is written.

Open
#19,895 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

__Proposal:__
Support distinguishing tags and fields when calling prometheus remote write

__Current behavior:__
Now all tags are treated as tags, except for label "value".

__Desired behavior:__
Provide a configuration to control whether the labelsin the prometheus monitoring data are set to tags when they are written

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

The issue names no files or tests. Start by locating the Prometheus remote-write path and its configuration handling; determine how label-to-tag behavior is currently applied. Done means a configuration controls which labels become tags during remote writes and the resulting memory-heavy behavior is addressed.

Written by the indexing model from the issue text.

Assessment

Domain
databases, observability-sre
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.