Disk space monitoring for runtime clouds

Disk space monitoring for the runtime clouds protects customers who inadvertently process too much data through aggressive scheduling or a misconfigured integration process.

This might happen if an integration process or series of integration processes begins to extract too much data without the customer's knowledge. This protection stops the processes from executing and prevents you from incurring any further overage fees while running on a runtime cloud.

This protection is triggered when an account exceeds 200 GB in disk space usage. When protection is triggered:

• The account's processes that are currently executing stop to avoid further overage fees.

• Processes that are stopped in this fashion display a message stating that the account has exceeded its size quota.

• New processes are not executed and they display the same message.

• You must contact Support to resolve the issue.

• Processes that run on local basic runtimes are not affected.

If you are concerned that your account might exceed the 200 GB limit, contact Support so that we can monitor your account and determine if you will actually exceed the disk space usage limit.

Disk space monitoring for private runtime clouds

If you have your own private runtime cloud, disk space monitoring is disabled by default. However, you can enable it for your runtime cloud to prevent accidental problems. In your runtime cloud you can set the disk space limit as needed. You can set a global limit for all accounts, different limits for the individual accounts that use your runtime cloud, or both.

The following properties control disk space monitoring for runtime clouds.

Property	Valid Values	Description
Disk Space Monitoring com.boomi.container.config.runDiskspaceMonitor=<value>	true or false	If set to true (the default), disk space monitoring is enabled. The monitoring system runs based on the value that is set in the Disk Space Monitoring Frequency property. It is recommended that you set this value through the user interface in the Properties panel, Advanced tab for runtime clouds.
Disk Space Monitoring Verbose Logging com.boomi.container.config.diskspacemonitor.verboseLogging	true or false	If set to true (the property default is set to false), the runtime cloud returns more information than the usual logging mode provides. You can use this option for troubleshooting needs, though large log files may slow down performance. Verbose logging includes: Size of each date directory in the data directory Total size of the data directory Size of each date directory in the execution/history directory Total size of the execution/history directory It is recommended that you set this value through the user interface in the Properties panel, Advanced tab for runtime clouds.
Disk Space Monitoring Account Auto Suspension com.boomi.container.config.diskspacemonitor.enableAccountAutoSuspension	true or false	Determines whether an account is automatically suspended when it exceeds the allotted disk space. This property is enabled by default. You can set this property through the user interface in the Properties panel, Advanced tab for runtime cloud.
Disk Space Monitoring Frequency com.boomi.container.config.diskspaceMonitorInterval=<number>	A whole number	Controls the frequency with which the disk space monitor runs. The number is specified in milliseconds. If this property is not set manually in Cloud properties, the property assumes a default value of 3,600,000 milliseconds (60 minutes). It is recommended that you set this value through the user interface in the Properties panel, Advanced tab for runtime clouds.
Disk Space Monitoring Threads com.boomi.container.config.diskspacemonitor.numThreads=<number>	A whole number	Controls the number of threads to be used for disk space monitoring. The value cannot be set to 0. The property's default value is 1. It is recommended that you set this value through the user interface in the Properties panel, Advanced tab for runtime clouds.
Disk Space Warning Limit com.boomi.container.config.diskspaceMonitorWarnThreshold=<number>	0 to 100	If set, logs a warning message on the server if the account reaches the specified percentage of its disk quota. You can monitor the server logs to ensure that no accounts are approaching the threshold. By default, this property is not enabled until a number is entered as the value. If you have both the Disk Usage Limit property set and Disk Space Monitoring enabled, the percentage of your disk space is logged as an info message each time the monitoring system runs according to the schedule you have set in the Monitoring Frequency property. It is recommended that you set this value through the user interface in the Properties panel, Advanced tab for runtime clouds.
Account Disk Usage com.boomi.container.config.quota.ACCOUNT_DISK_USAGE=<number> <KB MB GB TB>	A whole number followed by KB, MB, GB, or TB or a positive integer in bytes	Used to set the global size limit for all accounts that use your runtime cloud, different limits for the individual accounts that use your runtime cloud, or both. By default, the property assumes an "unlimited" value unless a numerical value is entered in the property field. (Clearing the field of all numbers reinstates the "unlimited" value). It is recommended that you set this value through the user interface on the Attachment Quotas tab.
Purge Manager com.boomi.container.config.runPurgeManager=<value>	true or false	If set to true (the default), the purging process is run in the runtime cloud. The purge log messages are written to the container logs. For more information, see Purging runtime Logs. If set to false, you need to run the purging process separately from the runtime cloud. The purge log messages are written to the atom-maintenance.log file. It is recommended that you set this value through the user interface in the Properties panel, Advanced tab for runtime clouds.