As part of Production Footprint Deployment we support Flexible Scaling of various services

Flexible Scaling provides you the ability to independently scale up services based on number of Devices, Events, Metrics, percentage of Metrics for Alarming and Anomaly, and so on as listed in the following table.

For Production Footprint system requirements, see VMware Telco Cloud Service Assurance Sizing Sheet.

For VMware Telco Cloud Service Assurance Domain Managers sizing sheet, see:
The following table provides the values supported for the scaling parameters for TKG, TCA, and AKS based deployments:
Scaling Parameter Value
Number of Managed Devices 7.5 K to 1 million.
Number of incoming Events 75 K to 10 million.
Number of incoming Metrics 3 million to 80 million.
Retention Period (For Metric Raw Data) 1 week and above. Value must be in terms of weeks.
Percentage of Unique Metrics for Alarm (percentMetricsForAlarms) 0 - 100 (Total number of unique metrics is 400; if user specifies a value of 10, then its means 40 Alarm definitions can be created).
Percentage of Unique Metrics for Anomaly (percentMetricsForAnomaly) 0 - 100 (Total number of unique metrics is 400; if user specifies a value of 10, then its means 40 Anomaly definitions can be created).
Number of Concurrent Users 100
Alerts for OI Server

alertsForOIServer (per sec)

 If a value not given then the default value is taken as 0. Total number of Alerts supported by VMware Telco Cloud Service Assurance is 0 to 200.
Number of Traps or Syslog

noOfTrapsOrSyslog (per sec)

 If a value not given then the default value is taken as 0. Total number of Alerts supported by VMware Telco Cloud Service Assurance is 0 to 200.
Retention Interval for Longterm Data

retentionIntervalForLongtermData

  • Metric Hourly rollup data (Weeks)
  • Metric Daily rollup data (Months)
  • Metric Weekly rollup data (Years)
  • Events History Retention (Days)

Retention Interval Time

  • 4 weeks
  • 1 month
  • 1 year
  • 31 days
The following table provides the values supported for the scaling parameters for VM based deployment:

Scaling Parameter

Value

Number of Managed Devices

7.5 K to 200 K.

Number of incoming Events

75K to 2000 K.

Number of incoming Metrics

3 million to 80 million.

Retention Period

1 week and above.
Percentage of Unique Metrics for Alarm (percentMetricsForAlarms) 0 - 100 (Total number of unique metrics is 400; If user specifies a value of 10, then its means 40 Alarm definitions can be created).
Percentage of Unique Metrics for Anomaly (percentMetricsForAnomaly) 0 - 100 (Total number of unique metrics is 400; If user specifies a value of 10, then its means 40 Anomaly definitions can be created).

Number of Concurrent Users

100
Alerts for OI Server

alertsForOIServer (per sec)

If a value is not given then the default value is taken as 0. Total number of Alerts supported by VMware Telco Cloud Service Assurance is 0 to 200.
Number of Traps or Syslog

noOfTrapsOrSyslog (per sec)

If a value is not given then the default value is taken as 0. Total number of Alerts supported by VMware Telco Cloud Service Assurance is 0 to 200.

retentionIntervalForLongtermData

  • Metric Hourly rollup data (Weeks)

  • Metric Daily rollup data (Months)

  • Metric Weekly rollup data (Years)

  • Events History Retention (Days)

Retention Interval Time

  • 4 weeks

  • 1 month

  • 1 year

  • 31 days
The following notes apply to Production footprints:
  • The Production Footprint System requirements table given above shows the VMware Tanzu Kubernetes Grid management sizing for deployments where a dedicated TKG management cluster is used for the TKG workload cluster. To size deployments when multiple workload clusters are managed by a single management cluster, see VMware Tanzu Kubernetes Grid documentation.
  • vSphere HA in vSphere must be enabled on which VMware Tanzu Kubernetes Grid management and workload cluster or VMs with Native Kubernetes (VM Based) are deployed.
  • In AKS, by default, first three worker nodes will be the control plane nodes.
  • IPv6 is not supported for VMware Telco Cloud Service Assurance deployment.
  • VM Snapshots are not supported for restoring the VMware Telco Cloud Service Assurance setup.