influxdata/telegraf

OPC UA doesn't support LocalizedText Datatype.

Open

#16,194 建立於 2024年11月16日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)Go (9,892 star) (4,161 fork)batch import
feature requesthelp wantedsize/m

描述

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

貢獻者指南

技術棧
go
領域
backenddata
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
GoOPC UATelegraf plugin structure
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
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.
OPC UA doesn't support LocalizedText Datatype. · influxdata/telegraf#16194 | Good First Issue