Process LogShip

Consolidate AVEVA log data from every node into one pane of glass.

All products

Diagnosing a multi-node problem across an AVEVA estate usually means checking out or remoting into one server after another. Process LogShip collects the logs centrally so you can search the whole estate at once.

What it does

  • Reads AVEVA and Wonderware logs directly. The Collector parses the proprietary binary aaLOG files written by the System Management Console (or Operations Control Management Console) and stores structured records in SQL Server.
  • Modular structure of four components, one pipeline. Collector and Replicator sit in the OT network, the Receiver (web front-end) sits in the DMZ or IT network, and the CloudReplicator forwards logs onward.
  • One-way flow, OT to IT to cloud. Traffic goes out over HTTPS with API key authentication. Nothing connects inward to the OT network.
  • Ships to the platform you already use. SQL Server and Power BI or Seq, Grafana Loki.
  • Does not drop records. Infinite retry with backoff means a network outage delays delivery rather than losing data.
  • Search and export. The Receiver has a web dashboard with log search, CSV export, and per-source status showing which nodes have gone quiet.
  • Keeps the volume manageable. Deduplication at each stage, filtering by source and log level, repeated-message suppression, and configurable purging.
  • SQL Express is fine. Built-in protection against the 10 GB database limit, plus disk space monitoring that pauses and resumes collection.
Process LogShip Receiver log viewer, filtered across sources and replicators, showing warning entries from several AVEVA nodes
Process LogShip Receiver sources page listing six AVEVA nodes with collector and replicator versions, last message time and total log counts
Every collector reporting in, with per-node message counts and staleness at a glance.

Talk to us about Process LogShip

We'll scope your project and propose an approach. No hard sell.

Start a conversation