Collecting logs from AVEVA System Platform and sending them to Solarwinds Loggly 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 Loggly 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 Solarwinds Loggly.
Sending logs to Solarwinds Loggly
Solarwinds Loggly is a cloud-based log analysis and monitoring service that provides complete visibility of log data from different sources. NXLog can be configured to send log data to Loggly in syslog format over TCP or via the Loggly API using HTTP(S).
- Loggly customer token
-
Loggly requires a customer token to be included with each event sent to its service. This token is an alpha-numeric string generated when creating a Loggly account. You can find your token on the Logs > Source Setup > Customer Tokens page of the web interface.
- Sending logs using TCP
-
Syslog is the most common way to send data to Loggly. The customer token and any custom tags need to be included in the structured data section of the syslog message. Logs can be sent securely to Loggly using TLS encryption. The Loggly certificate file must be downloaded and placed in a location that NXLog can access.
- Sending logs using HTTPS
-
As part of their API, Loggly provides two HTTP(S) endpoints that accept log data, one for sending single log records and another for sending logs in batches. Data can be sent as plaintext, JSON, or any log format supported by Loggly’s automated parsing. When logs are sent over HTTPS, the Loggly customer token and any custom tags must be included in the URL. The Loggly certificate file must be downloaded and placed in a location that NXLog can access.
For more information on configuring NXLog and sending logs to Solarwinds Loggly, see the Solarwinds Loggly integration guide in the NXLog User Guide.
