System properties for Cloud Cost Management
Summarize
Summary of System Properties for Cloud Insights IT Asset Management
This document provides a comprehensive list of system properties for managing Cloud Insights IT Asset Management, specifically for the Washington DC release. These properties control various parameters related to billing, spend analysis, business hours, Microsoft Azure integration, rightsizing recommendations, and cloud cost management. Understanding and configuring these properties allows customers to optimize their Cloud Insights operations effectively.
Show less
Key Features
- Billing Download Jobs: Configure thread counts and record limits for CI placement from AWS data.
- Spend Analysis: Manage metrics for billing records and forecast spend over future months.
- Business Hours: Set batch sizes and chunk configurations for reporting and rightsizing recommendations.
- Microsoft Azure Operations: Control batch sizes for Azure action calls and recommendation processing.
- Cloud Cost Management Infra Stack: Set various timeout properties for managing job states and processing efficiency.
Key Outcomes
By leveraging these system properties, ServiceNow customers can:
- Improve the efficiency of CI placements and billing processes through optimized thread and record settings.
- Enhance spend reporting accuracy and forecasting capabilities.
- Streamline business hour reporting and rightsizing recommendations with adjustable workloads.
- Optimize Azure integrations for better performance and processing speed.
- Manage job states effectively, ensuring timely processing and reducing latency in billing data handling.
Set some property values on the System Properties form, but other lesser-used properties are available only on the System Property [sys_properties] table.
| 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.
|
| 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.
|
| 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.
|
| System property | Description |
|---|---|
| sn_cld_spend_core.metricbase_transform_limit | Maximum number of Billing records to use in one Metric Base transform.
|
| sn_cld_spend_core.spend_report_flow_launcher_chunk_size | Number of non-empty CI chunks to send to the spend flow launcher.
|
| 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.
|
| 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.
|
| System property | Description |
|---|---|
| sn_clin_core.bh_report.batch_size | The number of resources to include in a Business Hours report batch.
|
| 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)
|
| 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)
|
| System property | Description |
|---|---|
| mid.azure_action.batch_size | Use 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.
|
| 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 in the case of fewer subscriptions.
|
| 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 created workloads.Generate Recommendation is a 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.
|
| sn_cld_intg_azure.advisor_get_status_min_chunk_size | Minimum number of subscriptions to process in a workload for The call creates a new workload when the specified minimum chunk size is met and, after all subscriptions are processed, does not 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.
|
| 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 new workload when the specified minimum chunk size is met and, after all subscriptions are processed, does not 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.
|
| 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.
|
| System property | Description |
|---|---|
| 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 AWS billing job files [sn_cld_intg_aws_billing_files] table for AWS and 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|
| 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.
|