The system generates detailed logs of all operations to assist with monitoring, troubleshooting, and auditing. These logs are invaluable for diagnosing issues but can consume significant storage over time.
Log Types
The system generates three categories of logs with different levels of importance:
Information logs: Standard operational events and routine processing information
Examples: License refresh, Engagement record creation, Stage updates, Reactivation events
Volume: Highest of all log types (typically 80-90% of logs)
Retention needs: Generally lowest priority for long-term retention
Warning logs: Potential issues that don't disrupt functionality but may require attention
Examples: Deactivation of picklist values used in configuration, empty attribution fields, performance degradation
Volume: Moderate (typically 5-15% of logs)
Retention needs: Medium priority for retention
Error logs: Critical issues that impact application functionality or data integrity
Examples: Failed Engagement creation, trigger execution failures, licensing issues
Volume: Lowest (typically <5% of logs in a healthy system)
Retention needs: Highest priority for long-term retention
Storage Impact
Logs can consume significant storage space, particularly in high-volume organizations:
A typical organization might generate 500-2,000 log records per day
Each log record consumes approximately 2-4KB of storage
Without proper retention settings, logs could consume 30-240MB of storage per month
Permissions
Before you get started, ensure you have the required permissions.
Configuration Steps
Navigate to Integrous Admin Settings > Logger Settings
Specify the retention period (in days) for each log type:
Information logs: Recommended 7-30 days
Warning logs: Recommended 30-90 days
Error logs: Recommended 90-365 days
Click Save to apply changes
Best Practices
Tiered retention strategy: Implement different retention periods based on log importance
Storage monitoring: Periodically review log volume to adjust retention settings
Extended error retention: Keep error logs longer to support pattern analysis over time
Compliance considerations: Adjust retention to meet any regulatory requirements
Troubleshooting preparation: Temporarily increase retention when implementing changes or during testing phases