influxdata/telegraf

Feature request for mqtt_consumer: ignore retained messages

Open

#10,824 opened on Mar 16, 2022

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (4,161 forks)batch import
area/mqttfeature requesthelp wantedsize/l

Repository metrics

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

Description

Feature Request

When using the MQTT consumer input plugin, you can subscribe to topics that have a retained value. At the moment, retained messages are treated as any other message and their value it stored.

Proposal:

Add a configuration setting to allow the mqtt_consumer input plugin to ignore retained messages.

Current behavior:

  1. Telegraf starts
  2. mqtt_consumer subscribes to configured topics
  3. Broker sends the retained messages for the configured topics
  4. Telegraf stores the values in configures output.

Desired behavior:

  1. Telegraf starts
  2. mqtt_consumer subscribes to configured topics
  3. Broker sends the retained messages for the configured topics
  4. Telegraf checks the config for the plugin, and if the option to ignore retained messages is set, it will NOT store the retained values.

Use case:

I have sensors that publish their data to MQTT with the retain flag set. Currently, every time I restart telegraf, it stores the retained value again when I only want it to update when new messages arrive.

Contributor guide

Research direction
Add a configuration option to the MQTT consumer input plugin to ignore retained messages. Look at the existing plugin code in plugins/inputs/mqtt consumer. You need to add a boolean config field, check the retained flag on incoming messages, and skip processing if the option is set.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65