influxdata/telegraf

OPC UA doesn't support LocalizedText Datatype.

Open

#16194 opened on Nov 16, 2024

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

Description

Use Case

Having a OPC UA server where all strings are LocalizedText Values, Telegraf doens't log the text but only returns Quality Good.

Expected behavior

Expected would be that the text value is outputted by Telegraf

Actual behavior

Telegraf doens't log the text but only returns Quality Good.

Additional info

This issue is heavily inspired by https://github.com/influxdata/telegraf/issues/12006

Contributor guide

Tech stack
go
Domain
backenddata
Issue type
bug
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-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
GoOPC UATelegraf plugin structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate how Telegraf's OPC UA plugin currently handles data types, focusing on the conversion of LocalizedText values. Look at the referenced issue #12006 for prior context. Files to examine are in plugins/inputs/opcua/ directory, especially those dealing with data type mapping and value extraction. Consider how to add support for LocalizedText by extending the existing type handling logic.