Skip to content

Switch to IEC binary prefixes #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Maksimiliana merged 3 commits into from
Feb 9, 2026
Merged

Switch to IEC binary prefixes #47

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
febf0a1
Switch to IEC binary prefixes
JannikBrand Feb 6, 2026
c8bea0d
Update docs/service-plans-a9d2d1b.md
JannikBrand Feb 9, 2026
fb24e6f
Update docs/service-plans-a9d2d1b.md
JannikBrand Feb 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/service-plans-a9d2d1b.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,27 +21,27 @@ To get an overview on the availability of SAP Cloud Logging according to region,

## Development Plan

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 `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 GiB storage capacity.



<a name="loioa9d2d1b5306d4da08ed0d0e38b2850f0__section_b2x_fb5_zyb"/>

## Standard Plan

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.
The `standard` plan targets usage in production. It incorporates data replication, and enables automatic scaling of net storage capacity from 75 GiB to 375 GiB.

> ### 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.
> If the average ingest rate is 100 x 2 KiB logs per second, a single standard plan instance can sustain storage for approximately 7 to 34 days, depending on the specific scaling configuration and including indexing and compression factors.



<a name="loioa9d2d1b5306d4da08ed0d0e38b2850f0__section_ak4_2c5_zyb"/>

## Large Plan

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.
The `large` plan targets usage in production. It incorporates data replication and enables automatic scaling of net storage capacity from 750 GiB to 3.75 TiB.

> ### 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.
> If the average ingest rate is 1000 x 2 KiB logs per second, a single large plan instance can sustain storage for approximately 7 to 34 days, depending on the specific scaling configuration and including indexing and compression factors.

Loading