Skip to content

Latest commit

 

History

History
43 lines (20 loc) · 2.5 KB

service-plans-a9d2d1b.md

File metadata and controls

43 lines (20 loc) · 2.5 KB

Service Plans

The SAP Cloud Logging service plans provide different ingestion and storage capabilities.

Note:

Updating service plans isn't supported. The recommended migration procedure involves running instances side-by-side during a transition.

For production service plans, service instances scale automatically within the configured limits. To avoid disk overflow, there is time-based and disk-utilization-based data curation. If the disk usage watermark has been exceeded and the instance is scaled to its maximum, the system automatically deletes the oldest indices. The term net storage capacity used in service plan descriptions refers to the usable disk-size up to the watermark and has subtracted the disk space required for replicas. Service plans can handle peak load in relation to their storage volumes. However, service quality degradation can happen if the load exceeds the non-scaled disk capacity within one day.

To get an overview on the availability of SAP Cloud Logging according to region, infrastructure provider, and release status, visit the SAP Discovery Center.

The dev plan is only for evaluation purposes. It must not be used in production use cases, as it lacks cloud qualities. It also doesn't include auto-scaling or data replication, and has limited ingestion throughput. Therefore it isn't suitable for testing loads exceeding its 7.5 GB-storage capacity.

The standard plan targets usage in production. It incorporates data replication, and enables automatic scaling of net storage capacity from 75 GB to 375 GB.

Example:

If the average ingest rate is 100x 2 kB logs per second, a single standard plan instance can sustain storage for approximately 8 to 43 days, depending on the specific scaling configuration.

The large plan targets usage in production. It incorporates data replication and enables automatic scaling of net storage capacity from 750 GB to 3.75 TB.

Example:

If the average ingest rate is 1000x 2 kB logs per second, a single large plan instance can sustain storage for approximately 8 to 43 days, depending on the specific scaling configuration.