AVEVA Product Feedback
PI system logging is currently fragmented across multiple location. This makes troubleshooting and log correlation difficult.
Solution:
Make logging consistent across all PI system applications. (ex: all logs stored in windows event log; all logs stored as readable text files).
Ability to write logs out to a centralized location (ex: Datadog, ElasticSearch, DynaTrace, GrayLog, Splunk etc).
Each application would have a configurable endpoint to egress logs out from the PI system to the centralized logging environment.
Application |
log location |
PI Data archive |
Log directory stored as .DAT files. Only accessible via PI tools |
PI Asset framework |
Windows event viewer |
PI analytics/Notifications |
analytics/Notifications log directory |
PI Vision |
Windows event viewer |
PI WebAPI |
Windows event viewer |
PI Interface |
Log directory stored as .DAT files. Only accessible via PI tools |
Use case for improved, modern Product logging:
Customer has a very large (millions of points) PI System implementation and would like to be able to view all PI Product logs in a centralized place. This allows them to review logs daily to identify and address issues proactively. Currently, logs are written to various locations - ex: PI Message Log, Event Viewer, etc. This fragmentation makes it difficult to get a comprehensive view of the health of their system.
Customer also requests that error messages written are actionable. Having clear, easy to understand error messages would result in fewer calls to technical support looking for guidance on a specific message.