AVEVA™ Data Hub Feedback Portal

Welcome to our new feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA Data Hub. For links to our other feedback portals, please see RESOURCES below.

Add a new idea Subscribe
Status Future Consideration
Product PI Adapters
Categories AVEVA Adapter for MQTT
Created by Guest
Created on Aug 16, 2022

RELATED IDEAS

Allow PI Adapter for MQTT to log the raw json payload received from the broker

For troubleshooting, it can be very helpful to see the raw json payload that the adapter has received from the broker, rather than just the error response from the attempted parsing. It can be difficult to know why a parsing attempt has failed without seeing the raw json payload for comparison. Being able to opt into this logging would be very helpful, whether at either the topic level or the data selection item level.
  • Attach files
  • Guest
    Reply
    |     Aug 16, 2022
    If you are interested in seeing raw data from MQTT brokers, there are third-party client tools available that you could use without having to create a Python script. One tool that we have suggested to customers is MQTT.fx. There is a license fee associated with the latest version of the tool but older versions of this tool are still accessible. Please try this out and let us know if it still does not meet your needs.
  • Guest
    Reply
    |     Aug 16, 2022
    For remote assets or containerized implementation, using an additional client tool to log the payload can be very difficult. A logging level to print out payloads that could not be parsed would allow this to be logged in the context of the PI Adapter operations