Expand | ||
---|---|---|
| ||
Look at the bottom of your Logs screen. You should see something like: You can physically examine how Iguana stores the log files. In Mac OS X:
In this way you can see how Iguana stores the logs for each component: Each component has its own directory. Each directory represents hexadecimal digits in Unix epoch time. Unix epoch time is the number of seconds since January 1st 1970. The structure of logs is design to facilitate fast random access to the data and makes it fast to dequeue and search the log data. |
Expand | ||
---|---|---|
| ||
From the Logs tab look down and click on the Manage link. |
Expand | ||
---|---|---|
| ||
With Iguana X is it no problem to clear the logs of each component individually. You can choose to get rid of test channel data or ‘chatty’ interfaces, while keeping important production data for decades. |
Expand | ||
---|---|---|
| ||
Locate Purging section of the Settings: This will show a set of rules that can be applied to your components to control how the automatic midnight purge affects their logs. Purge Rules must be alphanumeric, and can support glob expressions, for example a rule with #lab* will match #labtest as well as #labprocedure1. Purge Rules are matched in the order they appear in the table, if a component’s description contains multiple matches the first rule matched will apply. Set up rules:
A convenient way to limit the amount of logs stored by all components is to define a purge rule with * and configuring it to purge after a set number of days. |
...
title | STEP 5: Test out your purge rules by clicking the test rules button |
---|
Now that some purge rules are defined, and components have been given hashes, test out what would happen if a purge was done now by clicking Test Rules.
You can sort the columns in the Testing purge rules table to efficiently view the rules affects.
...
Iguana’s Logs contain service information, user activity, and all transactions which can contain sensitive data. Log management is crucial as the logs are integral to Iguana's operations.
Info |
---|
For proper log management, it’s important to understand how the logging and queueing system works and how the logs are stored and structured. |
Expand | ||
---|---|---|
| ||
Logs are stored in the log directory. If required, you can change the Log Directory. Configure a separate folder for logs on a designated partition or drive with good read/write speeds for low latency. Add additional layers of security on your log directly by implementing:
|
Expand | ||
---|---|---|
| ||
Avoid interruptions that can be caused if Iguana cannot write to the log storage because it is out of space.
|
Expand | ||
---|---|---|
| ||
Logs contain all transactions and play a key role in troubleshooting integrations. The Logs directory should be backed up regularly. See Backing up Iguana for backup procedure best practices. |