https://docs.protegrity.com/10.2/docs/aog/architecture/Recent content in Architectures onHugoenhttps://docs.protegrity.com/10.2/docs/aog/architecture/esa_logging_architecture/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/10.2/docs/aog/architecture/esa_logging_architecture/<h2 id="architecture-overview">Architecture overview</h2> <p>Logging follows a fixed routine. The system generates logs, which are collected and then forwarded to Insight. Insight stores the logs in the Audit Store. The Audit Store holds the logs and these log records are used in various areas, such as, forensics, alerts, reports, dashboards, and so on. This section explains the logging architecture.</p> <p><img src="https://docs.protegrity.com/10.2/docs/images/logging_arch_10_2_0.png" alt="" title="Architecture: Overview"></p> <ul> <li> <p><strong>ESA:</strong></p> <p>The ESA has the <strong>td-agent</strong> service installed for receiving and sending logs to Insight. Insight stores the logs in the Audit Store that is installed on the ESA. From here, the logs are analyzed by Insight and used in various areas, such as, forensics, alerts, reports, dashboards, visualizations, and so on. Additionally, logs are collected from the log files generated by the Hub Controller and Membersource services and sent to Insight. By default, all Audit Store nodes have all node roles, that is, Master-eligible, Data, and Ingest. A minimum of three ESAs are required for creating a dependable Audit Store cluster to protect it from system crashes. The architecture diagram shows three ESAs. Legacy protectors send logs to the ESA using the Log Facade.</p>https://docs.protegrity.com/10.2/docs/aog/architecture/iag_log_intro/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/10.2/docs/aog/architecture/iag_log_intro/<h2 id="overview-of-logging">Overview of logging</h2> <p>Protegrity software generates comprehensive logs. The logging infrastructure generates a huge number of log entries that take time to read. The enhanced logging architecture consolidates logs in Insight. Insight stores the logs in the Audit Store and provides tools to make it easier to view and analyze log data.</p> <p>When the user performs some operation using Protegrity software, or interact with Protegrity software directly, or indirectly using a different software or interface, a log entry is generated. This entry is stored in the Audit Store with other similar entries. A log entry contains valuable information about the interaction between the Protegrity software and a user or other systems.</p>