--- sourceDocument: Australia Asset Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-asset-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Asset Management ft:clusterId : - itam bundleId : - itam workflow : - Technology --- # System properties for Cloud Cost Management # System properties for Cloud Cost Management {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 8 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of System properties for Cloud Cost Management This document details the system properties available in the Cloud Cost Management application for ServiceNow customers using the Australia release (updated March 12, 2026). These properties control various operational aspects such as billing downloads, spend analysis, business hours reporting, rightsizing recommendations, and integration with cloud providers like AWS and Microsoft Azure. Show full answer Show less System properties can be accessed and configured via **All \> System properties \> All properties** . Common properties are editable through the System Properties form, while less frequently used ones reside in the **sysproperties** table. ## Key Configuration Areas and Their Practical Use * **Billing Download Jobs:** Properties like `ciplacementthreadsnumber` and batch size limits optimize how many configuration items (CIs) and billing records are processed concurrently, improving throughput and resource handling during billing data ingestion. * **Spend Analysis:** Controls such as `metricbasetransformlimit` and chunk sizes for spend flows regulate data processing volumes and report generation, enabling efficient handling of large billing datasets and forecast periods. * **Business Hours Reporting:** Settings define batch sizes and chunking for resource reports and rightsizing recommendations, balancing processing efficiency and system load. * **Microsoft Azure Integration:** Batch size limits for API calls and polling intervals for recommendation orchestrators control concurrency and responsiveness of rightsizing and unused resource recommendations. * **AWS Price Sheet Download:** Timeout settings help manage the maximum allowed duration for AWS price sheet downloads, ensuring job stability. * **Cloud Cost Management Infra Stack (Optional):** Properties optimize data storage by limiting pivot keys, filtering tag data, and controlling which CI types are persisted, reducing data volume and improving performance. * **Job Timeout Controls:** Several timeout properties govern the lifecycle stages of billing and processing jobs to prevent hangs and ensure timely execution. Some require ServiceNow support intervention for configuration. * **Multi-currency Setup:** Properties enable multi-currency features, configure exchange rate dates, and allow integration with existing currency conversion tables, simplifying currency management within Cloud Cost Management. ## What Customers Can Expect * Fine-grained control over batch sizes, chunking, and threading enables scalable and efficient processing of cloud cost and usage data across AWS, Azure, and multi-currency environments. * Improved performance and resource management during billing data ingestion, spend analysis, and rightsizing recommendation generation. * Optimized data storage and memory usage when the Infra Stack application is installed, by filtering and consolidating cost line items and tags. * Configurable timeouts help prevent stalled jobs and improve reliability of billing and recommendation workflows. * Multi-currency support integration streamlines financial reporting in diverse currency environments, leveraging existing ServiceNow currency tables if desired. * Some timeout and job management properties require coordination with ServiceNow support to ensure proper configuration and system stability. These system properties are available for the Cloud Cost Management application. Access system properties by navigating to AllSystem propertiesAll properties.. You can set some property values on the System Properties form, but other lesser-used properties are available only on the System Property \[sys_properties\] table. {#sys-pro-ci__table_ays_hkm_ywb__entry__2} | System property | Description | |-|-| | sn_cld_intg_core.ci_placement_threads_number | Number of threads that are used by CI placement flow to create CIs in the billing process. * Type: integer * Default value: 4 {#sys-pro-ci__ul_nyq_pkm_ywb} | | sn_cld_intg_aws.max_unprocessed_records_for_ci_placement | Maximum number of records to read in one batch from the AWS Cost And Usage Bill Data table for CI Placement. * Type: integer * Default value: 300000 {#sys-pro-ci__ul_glt_zkm_ywb} | | sn_cld_intg_aws.min_unprocessed_records_for_ci_placement | Minimum number of records to read in one batch from the AWS Cost And Usage Bill Data table for CI Placement. * Type: integer * Default value: 100000 {#sys-pro-ci__ul_k2d_flm_ywb} | [Table 1. System properties for Billing Download jobs] {#sys-pro-ci__table_ays_hkm_ywb} {#sys-pro-ci__table_fkc_hlm_ywb__entry__2} | System property | Description | |-|-| | sn_cld_spend_core.metricbase_transform_limit | Maximum number of Billing records to use in one Metric Base transform. * Type: integer * Default value: 20000 {#sys-pro-ci__ul_v5m_rqm_ywb} | | sn_cld_spend_core.spend_report_flow_launcher_chunk_size | Number of non-empty CI chunks to send to the spend flow launcher. * Type: integer * Default value: 40 {#sys-pro-ci__ul_mmn_tqm_ywb} | | sn_cld_spend_core.spend_report_per_chunk_workload_size | Number of workloads (CI ranges and metadata) for each chunk in the spend flow launcher. * Type: integer * Default value: 500 {#sys-pro-ci__ul_zdn_4rm_ywb} | | sn_cld_spend_aws.num_months_forecast | Number of future months after the current month for which the AWS Forecast spend is retrieved during every execution of the Spend job. * Type: integer * Default value: 2 {#sys-pro-ci__ul_khg_qrm_ywb} | | sn_cld_spend_core.favourite_views_limit | The maximum number of spend views that a user can mark as favorites. The request to mark a view as favorite is rejected after the user reaches this value. * Type: integer * Default value: 10 {#sys-pro-ci__ul_nym_t1s_fkc} | [Table 2. System properties for Spend analysis] {#sys-pro-ci__table_fkc_hlm_ywb} {#sys-pro-ci__table_e52_trm_ywb__entry__2} | System property | Description | |-|-| | sn_clin_core.bh_report.batch_size | The number of resources to include in a Business Hours report batch. * Type: integer * Default value: 5000 {#sys-pro-ci__ul_ubs_yrm_ywb} | | sn_clin_core.bh_recom_max_chunk_size | Number of records used to create workload chunks of rightsizing recommendations. If you set a value greater than glide.db.max_view_records, then the glide.db.max_view_records value is used instead. A smaller number means more chunks and a larger number means fewer chunks. Records considered in one execution of generating recommendations = (number of chunks) \* (data records/chunk) * Type: integer * Default value: 10000 {#sys-pro-ci__ul_sx5_csm_ywb} | | sn_clin_core.bh_recom_num_chunks_per_workload | Number of chunks per workload. This value times the value of sn_clin_core.bh_recom_max_chunk_size is the total number of records per workload when generating rightsizing recommendations. Records considered in one execution of generating recommendations = (number of chunks) \* (data records/chunk) * Type: integer * Default value: 10 {#sys-pro-ci__ul_wst_fsm_ywb} | [Table 3. System properties for Business Hours Note: The collection of data for a single download of billing or price sheet data is called a workload. Data in a workload is held in sets of data called chunks. You can specify the size of each chunk and the number of chunks in a workload.] {#sys-pro-ci__table_e52_trm_ywb} {#sys-pro-ci__table_tc3_hsm_ywb__entry__2} | System property | Description | |-|-| | mid.azure_action.batch_size | Use `batch_size` to set the batch size to fewer than 20 for action calls like Stop, Start, Modify (resize), Terminate, and Describe. Cloud Cost Management uses the Azure Batch API to make a bulk request for the actions. By default, Azure Batch supports a maximum of 20 for the synchronous call. * Type: integer * Default value: 20 {#sys-pro-ci__ul_j2t_ksm_ywb} | [Table 4. System properties for Microsoft Azure] {#sys-pro-ci__table_tc3_hsm_ywb} {#sys-pro-ci__table_drz_msm_ywb__entry__2} | System property | Description | |-|-| | sn_cld_intg_azure.az_rs_recommendation_queue_orchestrator_polling_time | Polling time for the Microsoft Azure recommendation orchestrator to check the status of the `generate`, `get generate status`, `list recommendation`, or `process recommendation` call and move it to the next stage for processing. Note: A short polling time is better if there are fewer subscriptions. * Type: integer * Default value: 5000 (ms) {#sys-pro-ci__ul_bz4_rsm_ywb} | | sn_cld_intg_azure.chunk_size_generate_recommendation_subscriptions | Number of subscriptions to be processed by each workload. Each workload creates a maximum of 5 threads to process 10 subscriptions in parallel based on the available MID Server worker threads. Changing the setting to lower number increases the number of workloads created. `Generate Recommendation` is an asynchronous API call that quickly returns the generate recommendation operation ID. Note: For fewer than 50 subscriptions, you can decrease the value to enable parallel processing. For example, for 40 subscriptions, changing the chunk size to 10 allows 4 workloads to process subscriptions. By default, a maximum of 3 parallel workload executions are allowed. The maximum is configured in the flow launcher job that is defined in the `sn_cld_intg_core_flow_launcher_job_config` table. * Type: integer * Default value: 5 {#sys-pro-ci__ul_pzl_5sm_ywb} | | sn_cld_intg_azure.advisor_get_status_min_chunk_size | Minimum number of subscriptions to process in a workload for `Get generate status` API call. The call creates a workload when the specified minimum chunk size is met and, after all subscriptions are processed, doesn't create another workload. Note: By default, a maximum of 4 parallel workload executions are allowed. The maximum is configured in the flow launcher job that is defined in the `sn_cld_intg_core_flow_launcher_job_config` table. * Type: integer * Default value: 5 {#sys-pro-ci__ul_st4_n5m_ywb} | | sn_cld_intg_azure.advisor_list_recommendation_min_chunk_size | Minimum number of subscriptions to process in a workload for the `list recommendation` API call. The call creates a workload when the specified minimum chunk size is met and, after all subscriptions are processed, doesn't create another workload. Note: Increasing the chunk size might increase the overall processing time because subscriptions are processed sequentially. By default, a maximum of 4 parallel workload executions are allowed. The maximum is configured in the flow launcher job that is defined in the `sn_cld_intg_core_flow_launcher_job_config` table. * Type: integer * Default value: 1 {#sys-pro-ci__ul_t1r_bvm_ywb} | | sn_clin_azure.advisor_process_recommendation_min_chunk_size | The number of recommendation responses that should be processed in a workload for the API call and persisted in the Rightsizing or Unused Machines recommendation table. The call creates a workload when the specified minimum chunk size is met and, after all subscriptions are processed, doesn't create another workload. Note: Increasing the chunk size might increase the overall processing time because subscriptions are processed sequentially. By default, a maximum of 4 parallel workload executions are allowed. The maximum is configured in the flow launcher job that is defined in the `sn_cld_intg_core_flow_launcher_job_config` table. * Type: integer * Default value: 20 {#sys-pro-ci__ul_ogq_2vm_ywb} | [Table 5. System properties for Rightsizing and Unused resources operations for Microsoft Azure Note: The collection of data for a single set of recommendations is called a workload. Data in a workload is held in sets of data called chunks. You can specify the size of each chunk and the number of chunks in a workload.] {#sys-pro-ci__table_drz_msm_ywb} {#sys-pro-ci__table_mhq_gtr_nbc__entry__2} | System property | Description | |-|-| | sn_cld_intg_aws.pricesheet_timeout_aws | Controls AWS price sheet download flow time out duration. * Value format: DD HH:MM:SS * Default value: 2 days {#sys-pro-ci__ul_q2d_ztr_nbc} | [Table 6. System properties for AWS Pricesheet] {#sys-pro-ci__table_mhq_gtr_nbc} {#sys-pro-ci__table_bmd_bgv_gdc__entry__2} | System property | Description | |-|-| | sn_cld_intg_core.optimize_pivot_keys | Enables the option to limit the columns used for pivot key generation so that multiple cost line items map to a single pivot key, which decreases the number of entries in the cost usage table. * Type: true \| false * Default value: false {#sys-pro-ci__ul_mgc_zzw_f3c} | | sn_cld_intg_core.sink_only_required_ci_types | Enables the option that only the line items that have the CI types - cmdb_ci_vm_instance, cmdb_ci_database, cmdb_ci_cloud_database, cmdb_ci_storage_volume, cmdb_ci_storage_vol_snapshot, are sent to Glide for storage in the cost usage table, reducing the data that is transmitted. * Type: true \| false * Default value: false {#sys-pro-ci__ul_g42_zzw_f3c} | | sn_cld_intg_core.enable_tag_filtering | Enables the option that only the tag names that are mapped to tag categories in the Cloud Cost Management Workspace are considered to save the tag values. This verification optimizes the memory requirement to transfer the tags to Glide. * Type: true \| false * Default value: false {#sys-pro-ci__ul_brg_zzw_f3c} | | ready.job.files.timeout | Maximum time in minutes to generate billing files for AWS assume role setup or blobs for Azure on Glide. You can monitor the AWS billing job files \[sn_cld_intg_aws_billing_files\] table for AWS and the Azure billing Job chunk blob detail \[sn_cld_intg_azure_job_chunk_blob_detail\] table for Azure only when the download is in progress and the time-out condition is met. * Type: String * Default value: 180 {#sys-pro-ci__ul_hst_5gv_gdc} | | ready.job.nofiles.timeout | Maximum time in minutes to wait for the backend to pick up the job when there's no other job being processed for the same provider. Important: To configure this system property, contact your support team. Don't configure it on your own. * Type: String * Default value: 10 {#sys-pro-ci__ul_a5q_1bw_fcc} | | reserved.job.timeout | Maximum time in minutes to wait for the job to change from Reserved to In progress state. Important: To configure this system property, contact your support team. Don't configure it on your own. * Type: String * Default value: 5 {#sys-pro-ci__ul_zvw_bbw_fcc} | | inprogress.job.timeout | Maximum time in minutes to wait for the job to change from In progress to Sink complete state. Important: To configure this system property, contact your support team. Don't configure it on your own. * Type: String * Default value: 10 {#sys-pro-ci__ul_lds_cbw_fcc} | | sinkcomplete.job.timeout | Maximum time in minutes to wait for the job to change from Sink begin to Sink complete state. Important: To configure this system property, contact your support team. Don't configure it on your own. * Type: String * Default value: 20 {#sys-pro-ci__ul_bdf_mbw_fcc} | | billing.data.post.processing.timeout | Maximum waiting time in minutes for billing from Post processing to Complete phase. The final stage of billing job includes inserting spend data into Glide. During the Post processing phase, the newly inserted data is activated and the existing data is inactivated. Increasing the time out value gives more time for the activation flow to complete. * Type: String * Default value: 30 {#sys-pro-ci__ul_ofy_jbw_fcc} | | retry.cred.failed.billing.job.timeout | Maximum time in minutes to wait before canceling a job that's in the Requested state due to credential failure. When you add a credential, it's sent to the backend only in the next billing run, resulting in a temporary failure. However, retries are made to establish a connection. This property specifies how long to wait before canceling the reattempted job. * Type: String * Default value: 30 {#sys-pro-ci__ul_pwr_hbw_fcc} | | sn_cld_intg_azure.billing_chunk_duration | Defines the chunk size for Azure billing blob in days. By default, each blob contains billing data for three days. * Type: Number * Default value: 3 {#sys-pro-ci__ul_in5_hdw_fcc} | [Table 7. System properties for Cloud Cost Management Infra Stack Important: These system properties are used only if the Cloud Cost Management Infra Stack application is installed in addition to the Cloud Cost Management version 8.1.] {#sys-pro-ci__table_bmd_bgv_gdc} {#sys-pro-ci__table_kvf_lvr_yhc__entry__2} | System property | Description | |-|-| | sn_cld_intg_core.enable_multicurrency_setup | Enables the multi-currency setup feature for users. * Type: true \| false * Default value: true {#sys-pro-ci__ul_a1y_pvr_yhc} | | sn_cld_spend_core.aws_exchange_rate_date | Sets up the currency exchange rate date for AWS. Type: integer | | glide.currency2.system_rate_\ | Eliminates the need to maintain a separate custom exchange rate table exclusively for Cloud Cost Management. To use an existing exchange rate table from another application, enter its name as the value for this property. * Type: String * Value: name of the table {#sys-pro-ci__ul_q4x_zkf_b3c} | | sn_cld_spend_core.ccm_custom_conversion_rate_\ | Sets up the currency exchange rates based on the preferred currency. The table to be used for conversion should extend to the System Currency Conversion Rates \[fx_conversion_rate\] table. * Type: String * Value: name of the table {#sys-pro-ci__ul_cny_gyr_yhc} | [Table 8. System properties for Multi-currency setup] {#sys-pro-ci__table_kvf_lvr_yhc} *[\>]: and then