Sending AVEVA System Platform logs to Sumo Logic

Collecting logs from AVEVA System Platform and sending them to Sumo Logic could be complex because of the unique combination of the log source and the desired destination. This post will show you how to forward log data from AVEVA System Platform to Sumo Logic by incorporating the NXLog log collection tool.

AVEVA System Platform

AVEVA System Platform is a modular and scalable industrial software platform for software solutions focused on industrial automation and engineering personnel, including SCADA, HMI, IIoT, and Manufacturing Execution Systems (MES). AVEVA System Platform supports both the supervisory control layer and the manufacturing execution system (MES) layer, presenting them as a single information source.

Collecting AVEVA System Platform logs

AVEVA System Platform produces a wide variety of logs concerning its operations. Some of those logs are available through Windows Event Log and network monitoring, but most exist as flat files.

AVEVA System Platform controls systems of significant financial and security importance. In mission-critical settings, the timely collection and processing of AVEVA System Platform logs is crucial to the reliability and security of the systems it controls. Even a brief interruption of normal operations could result in catastrophic consequences. However, the sheer diversity of log formats and data structures, and the noise that some of these logs contain, pose severe challenges to most logging software.

NXLog Enterprise Edition is a lightweight, modular log collection tool capable of tackling the most challenging cases log collection may pose. Its rich features allow it to read almost any log format and parse fields to produce structured data for further processing. It is the perfect tool for monitoring and collecting AVEVA System Platform logs.

Collecting AVEVA System Platform logs from Windows Event Log

Many applications send their logs directly to Windows Event Log, the preferred logging facility on the Windows platform. AVEVA System Platform sends its diagnostic and security-related events, such as user authentication, the state of system components, record modifications, and information about various other services to Windows Event Log. Logs can be read and collected using an Event ID related to AVEVA System Platform or by a given source name.

Collecting AVEVA System Platform logs from file

File-based AVEVA System Platform logs include logs from:

  • ArchestrA system

  • ArchestrA Logger and Log Viewer

  • Historian Search

  • Historian Configuration Exporter error

  • InTouch Access Anywhere

  • License Server

Collecting AVEVA System Platform logs from database tables

AVEVA System Platform reads information from database tables and provides insights into internal components and process-related data such as tag data, process alarms, and process events. Logs are collected from the following databases:

  • System Monitor

  • Runtime

  • Holding

  • Alarm

  • Records from history blocks

AVEVA System Platform Network Monitoring

AVEVA System Platform supports open platform communications (OPC) functionality, SuiteLink, DDE/FastDDE, and ArchestrA Message Exchange. NXLog can passively monitor network traffic and generate logs for most network protocols.

The easiest way to collect and normalize AVEVA System Platform logs is by deploying NXLog. With its unique capabilities, logs can be collected from literally any file in any format. Given the wide variation in format and structure of such log files, its versatility is ideal for these systems.

For more information on integrating NXLog with AVEVA System Platform, see the AVEVA System Platform integration guide.

The sources mentioned above and NXLog’s features play an important role in normalizing logs accepted by Sumo Logic.

Sending logs to Sumo Logic

Sumo Logic is a real-time SaaS platform that collects, manages, and analyzes log data while securing cloud-scale applications. NXLog can be configured to send log data to Sumo Logic in syslog format over TCP or via a custom HTTP endpoint. It can also be configured to send host metrics via HTTP.

Data collection

Sumo Logic accepts data from two types of collectors, installed or hosted. Installed collectors are set up by installing agent software provided by Sumo Logic, whereas hosted collectors are used to send data over TCP or HTTP(S) from agents like NXLog.

Sending logs using TCP

Sumo Logic accepts log data as syslog messages in IETF (RFC 5424) format and requires sending data using TLS v1.2 over TCP. A Cloud Syslog Source must be created in Sumo Logic to use this method. Syslog messages should fully comply with RFC 5424 guidelines, otherwise Sumo Logic will drop them. Also, it should be noted that messages larger than 64 KB will be truncated.

Sending logs using HTTPS

Logs and host metrics can be sent to Sumo Logic over HTTP(S) using a unique URL generated for each source. An HTTP Logs & Metrics Source must be created in Sumo Logic for NXLog to be able to send data over HTTPS.

Sumo Logic supports metrics in the Graphite, Carbon 2.0, and Prometheus formats. NXLog can be configured to convert data into practically any desired format. It can read and convert the data to another format on the fly while forwarding, without the need to create a temporary file.

For more information on configuring NXLog and sending logs to Sumo Logic, see the Sumo Logic integration guide in the NXLog User Guide.

GET STARTED TODAY:

NXLog Ltd. develops multi-platform log collection tools that support many different log sources, formats, transports, and integrations. The tools help administrators collect, parse, and forward logs so they can more easily respond to security issues, investigate operational problems, and analyze event data. NXLog distributes the free and open source NXLog Community Edition and offers additional features and support with the NXLog Enterprise Edition.

This document is provided for informational purposes only and is subject to change without notice. Trademarks are the properties of their respective owners.