Collecting logs from Schneider Electric EcoStruxure Process Expert and sending them to Solarwinds Loggly could be complex due to this unique combination of log source and SIEM. In this post, we will look at how you can forward log data from Process Expert to Loggly using NXLog.
Process Expert is a scalable multi-engineering environment and distributed control system (DCS) from Schneider Electric. It is based on a client-server architecture that can easily adapt to the needs and scope of your plant. Process Expert provides numerous advantages, substantially reducing maintenance and engineering costs by centralizing its hardware and software configuration. It does not only reduce human error but also increases plant efficiency by simplifying installation and system design. Due to its unique model and multiuser environment, collaborating on projects is more concurrent, giving engineers the power to work on various tasks simultaneously.
The main components of Process Expert work together seamlessly to play an integral role in monitoring plant operation. The system server manages system data and client requests. The operation clients provide a user-friendly interface for monitoring system components during runtime, while the Engineering clients provide a user interface to access specific software resources. Virtual machines offer software participant services, and the database stores and manages user data.
Process Expert is used in the oil and gas, power generation, chemicals, water, and mining industries.
Process Expert provides valuable information about its operation from the logs it generates. Some of these logs are available through Windows Event Log and network monitoring, but most of them are in the format of flat files.
Due to the critical nature and scope of the systems Process Expert controls, there is no room for error. Its stable, uninterrupted operation is crucial for plant safety. However, this valuable information can sometimes remain hidden in the logs it collects due to excessive log noise. Another challenge is the lack of consistent log formats. The ability to parse data from various log formats is an absolute necessity.
NXLog Enterprise Edition is a lightweight, modular log collection tool capable of tackling the most complex cases log collection may pose. Due to its rich features, it can read almost any log format and parse fields to produce structured data for further processing. It is the perfect tool for monitoring and collecting Process Expert logs for these reasons.
- Collecting Schneider Electric EcoStruxure Process Expert logs from Windows Event Log
Windows Event Log is the logging subsystem on the Windows platform. The logs generated by Process Expert include the Data Access log, sysInfo log, Servertrace log, and Communication log. NXLog can easily read and collect these events by specifying a Process Expert source name or event ID from the Application channel of Windows Event Log. A special, lightweight module that can natively read data from WEL provides this functionality.
- Collecting Schneider Electric EcoStruxure Process Expert logs from file
Schneider Electric EcoStruxure Process Expert file-based logs include Server log, ServerTrace log, Engineering client log, and Operation log. These logs are stored in the
C:\Users\<Username>\AppData\Roaming\Schneider Electric\Process Expert 2020 R2\Logsdirectory but do not follow a consistent formatting scheme. NXLog’s rich set of features can efficiently read and parse such file-based logs and reliably forward them to your preferred SIEM solution.
- Schneider Electric EcoStruxure Process Expert network monitoring
NXLog can passively monitor network traffic and generate logs for most network protocols. This ability to log network communication from Schneider Electric EcoStruxure Process Expert, and integrated devices, can provide another valuable log source.
NXLog can also normalize and aggregate Schneider Electric EcoStruxure Process Expert logs. With its ability to collect logs from literally any file, in any format, NXLog is ideally suited for integrating with Process Expert’s wide variety of log types and file formats.
For more information on integrating NXLog with Schneider Electric EcoStruxure Process Expert, see the Schneider Electric EcoStruxure Process Expert integration guide.
The log sources mentioned above and NXLog’s features play an important role in normalizing logs to be accepted by 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.