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:
Copy the location
Open the Finder application
Use the Shift + ⌘ + G to open a window lets you change the directory which you can copy paste the logs location into:
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.
From the Logs tab look down and click on the Manage link.
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.
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 are matched in the order they appear in the table, if a component’s description contains multiple matches the first rule matched will apply.
Setting up rules:
Click EDIT at the top right of the page. Then make a rule that all your components with #prod Never have their data purged and click Save:
Iguana X supports glob expression (*), boolean(and/or), or regular expressions (regex) with Tags to create matching rules. To use regex, simply enclose the expression in slash characters /<regex>/. The table below provides an overview of example pattern matching techniques you can combine to create a matching rule.
Type | Example | Description |
|---|---|---|
Wildcard | * | Apply to all components. |
#dev* | Apply to components with #dev followed by 0 or more characters | |
OR | #prod #dev | Apply to components with either #prod OR #dev tags. |
AND | “#prod #dev“ | Apply to components with both #prod AND #dev tags. |
Negation | -#prod | Apply to all components without the #prod tag. |
“#prod -#dev” | Apply to all components with the #prod tag AND without #dev. |
Make another Purge Rule that channels with #device will be purged when they have 30 days of logs because they are chatty and click Save:
Make another Purge Rule for all your test components to be purged daily:
The first thing to do is label your test components with #test, to do this navigate to your Source and Destination component cards by double clicking them on the dashboard.
Edit the Tags field in the Component Card to add the #test rule (Make sure your Component is OFF).
Repeat the same 2 steps for the Source Component as well.
Go back to Purging in the Settings.
Add the rule for #test components to be purged daily and click Save:
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.
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.
