File channel
The File channel collects log server events directly to a file in either the CSV format or the translated format (default setting), which writes the log in a human-readable format. The log data is defined in the corresponding event definition.
CSV files simply contain the event data; consequently, they are difficult to decipher. However, because these comma-delimited files maintain a consistent field structure across events, you can import these files into spreadsheet programs like Microsoft Excel to query the log data.
The following is a sample from a CSV log file:
2130706433,1250570029,1250570029,\VED\Engines\Jupiter\TLS Protect,1245202,Info,0,,,10000,0,,
2130706433,1250570029,1250570029,\VED\Engines\Jupiter\TLS Protect,1245197,Info,0,\VED\Policy\Import\cert1.venafi.com,10/05/2009 03:49:24,0,0,,
On the other hand, translated log files are more human-friendly. They can be visually scanned for content. However, it is difficult to generate reports from translated log files because there is no delimited field structure. They get their main content from the Translation field in the event definition. (In the event definition table view, this field is just called Log.)
The following is a sample from a translated log file:
127.0.0.1, 17/08/2024 22:17:42: The Venafi Encryption Trust Protection Platform service manager for the engine Jupiter is running in 32 bit mode.
127.0.0.1, 17/08/2024 22:17:42: The engine \VED\Engines\Jupiter is loading the service module \VED\Engines\Jupiter\TLS Protect.
127.0.0.1, 17/08/2024 22:17:42: The certificate management service module for the engine Jupiter is examining certificates for expiration.
127.0.0.1, 17/08/2024 22:17:42: The certificate management service module for the engine Jupiter is examining certificates for notification.
127.0.0.1, 17/08/2024 22:17:42: The certificate manager for Jupiter has found 10000 certificates for renewal expiration consideration.
127.0.0.1, 17/08/2024 22:17:42: The certificate manager for Jupiter has found 0 work to do requests for consideration.
The Venafi Log server can use the file channel to create specialized log files for specific types of events.
WARNING! If you are using a file channel, you should strongly consider only using a single log server. If you are using multiple log servers, and if your file output is saved locally on each Venafi server, you will have incomplete logs on each server. You would need to manually combine all log files for an accurate, complete log. If your file output is saved on a shared network drive, your log servers will constantly be competing to write to the file, which will result in errors and incomplete logs.