CONNECT feedback portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about CONNECT products and services. All of the feedback you share here is monitored and reviewed by the CONNECT 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 CONNECT. For links to our other feedback portals, please see RESOURCES below.

ADD A NEW IDEA

Clear

Ideas

    Configurable Hostname/IP Identifier for OMF Health Egress

    The health tags and AF structure is created with the following naming pattern by default: <machine hostname>.<adapter type> To support modern containerized deployment models, please consider adding a configurable field that allows cust...
    Guest 8 months ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

    Support System States for the Adapter for Azure Event Hubs

    The data passed through the Adapter for Azure Event Hubs can be very dynamic in its configuration. It would be useful to be able to send system states to indicate bad data, and possibly the nature of that bad data. In the same way that interfaces ...
    Mike Horrocks over 2 years ago in AVEVA™ Adapters / AVEVA Adapter for Azure Event Hubs 2 No status

    PI to CONNECT credentials

    I’d like to be able to setup the agent using a pre-created clientId and clientSecret along with my tenantId – our servers require that we login with a different account than our normal user account and since credentials we're trying to pass to CON...
    Guest about 4 years ago in PI to CONNECT 1 Tell us more

    Configure PI to CONNECT metadata to sent to CONNECT

    I would like to be able to select which fields to send to CONNECT as meta data from PI. Currently the options include High, Medium, Low. none. I would like a 5th option that allows me to pick and choose which fields are important to me to send.
    Guest about 4 years ago in PI to CONNECT 1 No status

    Include information from Json body in the stream name created by the MQTT Adapter

    As a system admin I would like to send mqtt messages from multiple devices to a single topic on an mqtt broker. Each message would contain data for the device along with a field to say which device the data has come from. Then I would like to use ...
    Guest about 4 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

    Stream-level debugging

    As a PI System Administrator, I'd like to be able to trace values being received, and subsequently being sent by the Adapter, similar to PI Interfaces. Having the ability to trace/log timestamps and values for specific streams would greatly help ...
    Guest about 4 years ago in AVEVA™ Adapters / General 0 Future consideration

    provide a sample dataset

    Enable a new user to explore an existing dataset and get ideas for their own implementation
    Glenn Moffett about 2 years ago in Streams / Sequential Data Store (SDS) 0 No status

    Provide additional features to support debugging

    When first setting up the agent, there can be scenarios where there a number of errors to work through - for example tag not found. Summarization of errors and an alternative to event viewer would aid debugging.
    Glenn Moffett almost 3 years ago in PI to CONNECT / General 0 No status

    Adapters using Text parser be able to dynamically generate the stream name or ID based on fields of the text parsed

    This could be a good feature for any adapters that uses the text parser. MQTT, SDF, Azure Event Hubs. When using JsonPath or Xpath to parse a file or payload the stream name and stream id have to be hardcoded their value cannot be based on a the v...
    Randy Giguere almost 3 years ago in AVEVA™ Adapters / General 0 No status

    Improve the message for performing on demand History Recovery on datacollectionmode: "CurrentWithBackfill" and "CurrentOnly"

    Running edgecmd to perform HR on demand on the datasource: datacollectionmode of Non HistoryOnly. will return the following error: Operation Failed: NotFound (404)Unexpected error: Unexpected character encountered while parsing value: 0. path '", ...
    Ee Sheing Lee about 2 years ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status