A unique text string used to identify this connection. This label is used to identify the connection when configuring store and forward, and to create the database name or retention policy in some historians, like InfluxDB. The label can contain only letters, numbers and the underscore ( _ ) character.

The PI Web API endpoint. This will be https://hostname[:port]/piwebapi, where hostname is the host name or IP address of the server running PI. If the PI Web API service is configured to use a port other than 443, you must also include a colon followed by the port number. E.g., https://192.168.1.17:8080/piwebapi

The user name used to authenticate this connection. You must configure users and passwords in the PI Server.

The password associated with the User name.

The maximum number of values that will be read in a single transaction. By default, PI limits reads to not more than 150,000 values. You can set this to a lower number to reduce the chance that a large query will cause delays in the PI Server. If necessary, the DataHub instance will use multiple read transactions to fully retrieve data over a period.

This is the maximum number of values that the DataHub instance will write in a single transaction. If the DataHub instance has more values waiting to be transmitted, it will break the values into multiple transactions of this size or less.

The number of milliseconds that the DataHub instance will buffer data in memory before sending it to PI. Setting this value to zero means that no accumulation time will be enforced, in which case Maximum # of buffered values will determine how frequently data is written..

The maximum number of values that the DataHub instance will buffer in memory before transmitting them to PI. Setting this value to zero means that values will not be buffered, but instead will be sent as soon as they are available.

The DataHub instance buffers values before transmitting them to PI to improve network efficiency. The two options, Accumulation time and Maximum # of buffered values, represent alternate ways to express the limit on that buffering. The DataHub instance will transmit accumulated values when either the maximum number of buffered values or the accumulation time is reached, whichever comes first.

Prevents the DataHub instance from writing to OSIsoft PI.

Checking this option causes messages regarding successful writes to the database to be logged at the Information level in the DataHub Event Log. If this is not checked then these messages are logged at the Debug level and are therefore normally hidden from the user.