Provide "Point Last Accessed" information to determine clients' use of PI Points
It would be useful to be able to determine when (or even if) a PI Point was last accessed by a client application to retrieve its data. This would enable redundant points to be identified and removed.
Alternatively/additionally some form of...
Add option to clear buffer errors to the Buffering Manager
Currently users have to use the command line tools to clear buffer point errors. It would be useful and enhance O&M if these errors could be cleared directly from the UI rather than just viewed.Bonus points for allowing users to clear all, mul...
Users want to be able to view the contents of a log file from the PI System Health tool to assist when troubleshooting an interface or other data flow problem.
Prevent piarchss from logging messages about overflow record insertion
When backfilling historical data, piarchss logs messages like this one:
Inserting overflow record 4035947. Point: 41455, archive start: 4-Jan-17 20:34:10, first event time: 25-Jan-17 09:49:00, record event count: 100, overflow count: 98
When a la...
Performance Counter for Critical, Error, and Warning messages.
In addition to a performance counter for total messages sent into the PI log, it would be very useful to have performance counter to determine which of these messages are Critical, Error, or Warning messages. This way, users can monitor specifical...
An option to suppress "[-15011] PIvalue Type is Not Numeric" when there is a non-numeric OOO event (e.g. string or digital value) between the pibufss last compressed event and snapshot event. While these messages are only informational they can qu...
Tech support often asks customers for message logs in bulk. The PISDKUtility and SMT are not good for this because they run out of memory if you try to load too many messages. The only way to export the logs is to use the command line pigetmsg uti...