influxdata/telegraf

Variable schema for postgressql output plugin

Open

#16,747 opened on Apr 9, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (4,161 forks)batch import
feature requesthelp wantedsize/s

Repository metrics

Stars
 (9,892 stars)
PR merge metrics
 (Avg merge 2d 12h) (136 merged PRs in 30d)

Description

Use Case

I have a PostgresSQL DB with several schemas. schemaA, schemaB, etc., in which I feed data from sensors through the mqtt_consumer plugin.

After a bit of processing, the measurement names look like "correspondingSchema_sensorName"

Expected behavior

I would like to be able to set the schema-name from a tag, which I would drop afterwards.

Actual behavior

Right now I have to define several outputs, one for each schema:

[[outputs.postgresql]]
namepass = ["schemaA_*"]
schema = "schemaA"

[[outputs.postgresql]]
namepass = ["schemaB_*"]
schema = "schemaB"

Additional info

No response

Contributor guide

Research direction
Examine the postgresql output plugin code to understand how the schema configuration is currently implemented and propose a method to allow dynamic schema from a tag.
Tech stack
go
Domain
backenddatabase
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoPostgreSQLTelegraf plugin development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60