This document describes the recommended configurations to make after IguanaX has been installed and licensed on your machine.
...
| Expand |
|---|
|
IguanaX uses Git to support building instance and managing integrationsintegration management. By setting up Iguana to interact with a local or cloud Git service you can: Backup and store your IguanaX configurations and integrations in external repositories Collaborate efficiently and track changes on Iguana and your integration projects Safely deploy integrations from development, test, to production Quickly standardize implementations as you create common libraries and collections
| Tip |
|---|
Add your Git Server to Iguana’s Server List: Iguana’s Git Servers page contains a list of Git servers you can connect your Iguana to. By default, the list contains cloud servers for Bitbucket, GitHub, GitLab and Azure DevOps. If you have an on premise server with one of these providers, you will need to add your server address to the list in order to connect. | | Panel |
|---|
| panelIconId | atlassian-check_mark |
|---|
| panelIcon | :check_mark: |
|---|
bgColor | #E6FCFF| Tip |
|---|
Configure Iguana’s Git Settings: Setup Iguana’s Git settings to leverage your Git service. These Git settings are stored on a per user basis so it is important that each user accessing and working in Iguana configures these settings. |
| Tip |
|---|
Configure your Git Instance: Integrate your IguanaX instance with Git to store all Iguana configurations and settings in a single Git repository you define. Configuring a Git Instance enables you to track instance changes, automate instance backups and quickly restore Iguana if needed. |
|
| Expand |
|---|
| title | Log Configuration and Maintenance |
|---|
|
Iguana’s Logs contain service information, user activity, and all transactions which can contain sensitive data. Log configuration and management is crucial as the logs are integral to Iguana's operations. | Tip |
|---|
Secure 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: |
| Tip |
|---|
Set Purge Rules and Monitor Log Disk Space: Avoid interruptions that can be caused if Iguana cannot write to the log storage because it is out of space. Manage your log storage with Log Purge Rules. Logs older than the defined log age will be automatically deleted by Iguana’s daily log purge at midnight. The default log age is 7 days. Purge rules can be applied to one or more components using a matching rule. Your ideal log age may depend on your log sizes and requirements around how long you need to keep messages for troubleshooting. Monitor your disk space on the Log Usagepage. Here, you can see total disk space used, free space, and a breakdown of log sizes of each component, giving you comprehensive information to determine appropriate log purge rules for your Iguana.
|
| Tip |
|---|
Backup Logs Regularly: 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. |
|
| Expand |
|---|
| title | Configure Custom Notifications |
|---|
|
Automate monitoring of Iguana and your integrations using Iguana’s notification system. | Tip |
|---|
Create custom Iguana notifications: Use notification rules to monitor for errors or unique conditions as well as proactively address building message queues and inactivity. Implement your notifications to send alerts to your team via email using the IguanaX Notifications component or implement your own component to send alerts to another application, such as Slack, Microsoft Teams, etc. |
|
...