vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For some workloads, especially where data is sent in large batches, this may result in small deviations from the limit.





 IAM ID bytes out quota used percentage 

The percentage of bytes out quota used per IAM ID. Where a bytes out quota was set for a user (IAM ID), this value shows the percentage of that quota being used.



Table 30. The percentage of bytes out quota used per IAM ID

 Metadata Description 

 Metric Name ibm_eventstreams_iam_id_bytes_out_quota_used_percentage 
 Metric Type gauge 
 Value Type percent 
 Segment By Service instance, Service instance name, Iam Id 



This is for information to help you monitor trends in your usage, particularly if any IAM IDs are consuming close to their quota limits. Quota metrics might sometimes exceed 100 %. Kafka quotas use sampling and are applied asynchronously. For some workloads, especially where data is sent in large batches, this may result in small deviations from the limit.





 Used disk space percentage 

The percentage of currently used disk space.



Table 31. Used disk space percentage metric metadata

 Metadata Description 

 Metric Name ibm_eventstreams_instance_utilised_disk_space_percent 
 Metric Type gauge 
 Value Type percent 
 Segment By Service instance, Service instance name 



This is for information to help you monitor trends in your usage. Refer to [Event Streams](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-plan_choose) to determine what the recommended limits are for your plan and cluster.





 Rest-producer requests per second 

Number of requests per second made to the REST Producer API.



Table 32: Rest-producer requests per second metric metadata

 Metadata Description 

 Metric Name ibm_eventstreams_instance_rest_producer_requests_per_sec 
 Metric Type gauge 
 Value Type none 
 Segment By Service instance, Service instance name 



This is for information to help you monitor usage of the REST Producer API, including use of schema encoders.





 Mirroring throughput 

The bytes per second of mirroring throughput from the source Event Streams instance.



Table 33.
If clients' VMs running on IBM Cloud for Education need to access resources on clients' internal network, such as clients' license servers, data etc, we can setup VPN to access clients' internal network, In order to setup VPN, clients need to provide following information to IBM:



* VPN account
* VPN connection information (e.g endpoint URL)
* The name of the image requiring VPN access



* When I order "Base Flex Plan", it says each authorized user entitled for one VM, what if user needs to provision more than one VM?

Applications Lab Base Flex Plan (a.k.a. per authorized user plan) allows maximum one reservation at a time. If you want to have multiple reservations at the same time, please use other plans or use mutiple accounts.
* What happens when I delete my service instance?

The service instance will not appear on Resource List and billing of the instance stops from next month. IBM Cloud retains the service instance for 7 days and in case you need to restore the same instance back, please raise a support ticket for "IBM Cloud for Education" in 7 days upon deleting instance from IBM Cloud UI. After 7 days, the service instance will be deleted permanently and can no longer be restored.
* Can't submit block allocation request?

Please make sure that "First Date of Usage" is later than the current time. The time zone by default is UTC.
* Which model of GPU cards are installed on the servers?

Nvidia V100 is used. Customers cannot access GPU directly, and can only access virtual GPU virtualized from V100.
* Do you support Operating Systems not shown in the image library, like Ubuntu 20 etc?

Yes. We are able to support the most popular Operating Systems in the market, please submit a ticket or click on the help to send us the configuration detail.



IBM Spectrum LSF



* What Spectrum LSF packages are included in a cluster deployed with this offering?

The following Spectrum LSF programs are included:



* IBM Spectrum LSF Standard Edition
* IBM Spectrum LSF License Scheduler
* IBM Spectrum LSF Data Manager



* What locations are available for deploying VPC resources?
* A quota can be applied to the 'default' user, so it applies to any user, even for whom no user-specific quota was set.







 Client metrics 

The Java client also exposes throttling information with the following per-broker metrics:



* produce-throttle-time-max
* produce-throttle-time-avg
* fetch-throttle-time-max
* fetch-throttle-time-avg







 Setting client quotas 

The IBM® Event Streams for IBM Cloud® Enterprise plan allows the use of the Kafka API to set and describe quotas on Kafka V3.1.x clusters. For more information, see the [Quota Operations section](https://cloud.ibm.com/apidocs/event-streams/adminrestcreate-quotas) of the IBM® Event Streams for IBM Cloud® Admin REST API.

With reference to the [Kafka documentation on quotas](https://kafka.apache.org/documentation/quotas), only throughput quota types ("producer_byte_rate" and "consumer_byte_rate" quota types) applied to the "user" entity (or the "default user") are supported.

The "client-id" entity, the "request", and the "controller-mutation" quota types are not supported as user-settable quotas. In Event Streams, an authenticated user identity is represented by an IBM Cloud® Identity and Access Management ID. Because Kafka quotas are applied per Cloud Identity and Access Management ID, a single quota can be shared by a group of API keys, if these all belong to the same Cloud Identity and Access Management service ID.

To obtain the Cloud Identity and Access Management ID of an Cloud Identity and Access Management (IAM) service ID, the IBM Cloud CLI can be used.

ibmcloud iam service-id ServiceId-12345678-aaaa-bbbb-cccc-1234567890ab --output json

See the following example output:

{

    "active":true,

    "jti":"...",
(https://cloud.ibm.com/docs-content/v1/content/9713d864488177dc6b273b53b7f2383a81f10bc1/billing-usage/images/advance-billing.png)

Figure 4. In advance infrastructure monthly usage charges.



* In Arrears (for example, the month of February) infrastructure hourly charges. These are usage-based charges from the previous month. Note the 672 hrs * .066 format of the charges. In arrears, infrastructure hourly charges are always in this format.



Zoom

![An example of an arrears infrastructure hourly charge on the detailed invoice tab from the downloaded Excel invoice.](https://cloud.ibm.com/docs-content/v1/content/9713d864488177dc6b273b53b7f2383a81f10bc1/billing-usage/images/arrears-hourly.png)

Figure 5.In Arrears infrastructure hourly charges.



* In arrears (for example, the month of January) platform service charges. These are usage-based charges from two months prior. They are labeled Platform service in column B and reference the month in which the usage was consumed.



Zoom

![In arrears platform service charges.](https://cloud.ibm.com/docs-content/v1/content/9713d864488177dc6b273b53b7f2383a81f10bc1/billing-usage/images/arrears-platform-service-charges.png)

Figure 6. In arrears platform service charges for the month of January.





 Next steps 

To continue your learning about your billing and usage, see [Managing payments](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-linkedusage),
"Total number of megabytes transferred between the Edge to the end user in the region - Australasia",
"Total number of megabytes transferred between the Edge to the end user in the region - EMEA",
"Total number of megabytes transferred between the Edge to the end user in the region - India",
"Total number of megabytes transferred between the Edge to the end user in the region - Japan",
"Total number of megabytes transferred between the Edge to the end user in the region - North America",
"Total number of megabytes transferred between the Edge to the end user in the region - Rest Of APAC",
"Total number of megabytes transferred between the Edge to the end user in the region - South America"
],
"totals": [
15, // Total Hits from start time to end time.
4.9301e-5, // Total Bandwidth from start time to end time.
0, // Hits by type 0XX
0, // Hits by type 200
0, // Hits by type 206
0, // Hits by type 2XX
0, // Hits by type 302
0, // Hits by type 304
0, // Hits by type 3XX
0, // Hits by type 404
13, // Hits by type 4XX
2, // Hits by type 5XX
0, // Hits by type Other
0, // Bandwidth by region Australasia
3.6554e-5, // Bandwidth by region EMEA
0, // Bandwidth by region India
0, // Bandwidth by region Japan
1.1524e-5, // Bandwidth by region North America
1.223e-6, // Bandwidth by region Rest Of APAC
0 // Bandwidth by region South America
],
"percentage": [ // The percentage of the bandwidth by regions
null,
null,
null,
null,
null,
null,
null,
null,
null,
null,
null,
null,
null,
0, // Australasia
: You can enforce production and consumption rate limits by settings quotas through [Administrative REST API](https://cloud.ibm.com/apidocs/event-streams/adminrestlist-quotas) to prevent network saturation or monopolizing broker resources.





 October 2022 

Context-based restrictions
: You can use network type or context-based restrictions to restrict the network connectivity on the Enterprise plan. For more information, see [Restricting Network Access](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-restrict_access).

Apache Kafka upgrade
: Upgrade to Apache Kafka version 3.1.





 July 2022 

Enhanced support for matching schemas
: Enhanced support for matching schemas when you use Confluent SerDes with the schema registry.





 May 2022 

Schema registry support on the Satellite plan
: The new [Satellite plan](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-satellite_about) now supports the [Schema registry API](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-satellite-provisioningsatellite-enable-schema-registry).





 April 2022 

Satellite plan
: With the new [Satellite plan](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-satellite_about), you can create a hybrid environment that brings the scalability and on-demand flexibility of public cloud services to the applications and data that run in your secure private cloud.

More topic and consumer group metrics
: More topic and consumer group metrics are available, see [Monitoring Event Streams metrics by using IBM Cloud Monitoring](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-metrics).





 December 2021 

Apache Kafka upgrade
: Upgrade to Apache Kafka version 2.8.





 October 2021 

IAM
If you need help with selecting the UNSPSC for your service, see [How to select UNSPSC codes?](https://help.ungm.org/hc/en-us/articles/360013132940-How-to-select-UNSPSC-codes-) to find the one that applies to your product. For the purposes of this tutorial, select a common UNSPSC.



1. Click Pricing > Add UNSPSC.
2. Select Cloud-based software as a service.
3. Click Add.







 Step 4: Define your pricing plan 

IBM Cloud supports two pricing models: free or usage-based. For the purposes of this tutorial, complete the following steps to add a usage-based plan.

By adding a usage-based pricing plan, you provide your suggested retail pricing information. However, IBM reserves the right to set the final pricing for any product that is offered to customers in the IBM Cloud catalog.



1. Click Add plan.
2. Select Usage-based as the type of plan.
3. Enter a name for your plan. For the purposes of this tutorial, enter Usage-based. Plan names must be in English and can contain only alphanumeric characters, hyphens, spaces, and periods.
4. Enter a description for your plan. Include any limitations that users must know. For example, The usage-based plan is for our upgraded services. This plan does not include our advanced features.
5. Select Per-location for the deployment location.
6. Select Specific locations to restrict deployment.
7. Choose Dallas - Region, London - Region, and Osaka - Region.
8. Select the broker that you want to link to this plan. If you haven't added a broker to your account, you can't link a broker to your plan. After you add a broker, you can link it by editing the pricing plan.
9. Click Save.
10. Click Add metrics.
11. In the Usage metrics section, click Add metrics.
12.
* How do I view my commitment usage?

To view your commitment usage, in the IBM Cloud® console, go to Manage > Billing and usage, and select Commitments & subscriptions.



* Click the tabs to view information on active or upcoming commitments.
* Use the graph to view what you've spent toward your overall committed amount.
* View monthly breakdown of the spending history for the commitment in the table.



* How do I view my commitment terms?

After you consult with a sales representative to sign up for IBM Cloud Enterprise Savings Plan, the sales team will email you a copy of your quote and information about IBM Cloud's Terms and Conditions.
* How do I add a new commitment?

Contact your [IBM Cloud Sales](https://www.ibm.com/cloud?contactmodule) representative to add a new commitment to your account.
* Why am I getting invoiced for a commitment I didn’t use?

Since you committed to a certain amount for a certain period of time and you didn't reach it, IBM Cloud® have the rights to charge you with the remaining amount.
* Can I convert my US-based USD Pay-As-You-Go to a Subscription account? If so, what kind of impact does the commitment model have?

Yes, you can convert your account from US-based USD Pay-As-You-Go to an Enterprise Savings Plan, but it will be only effective after the term end of your former plan.
* Where can I access my invoice?

If you have a billable account, you can access your invoice by clicking Manage > Billing and usage, and selecting Invoices. If you have a Lite account, you don't have an invoice because you're never charged for Lite plan usage.

You might be redirected to [IBM Invoices website](https://www.ibm.com/invoices). See [How do I view invoices for Pay-As-You-Go or Subscription accounts?]
Use the following commands to retrieve resource usage and billing information.



1. Log in, and select the account.

ibmcloud login
2. View usage by running the ibmcloud billing command as shown in the following examples.



* View usage for the current month.

ibmcloud billing account-usage [-d YYYY-MM] [--output FORMAT] [-q, --quiet]
* View monthly usage for an org (account admin or org billing manager only):

ibmcloud billing org-usage ORG_NAME [-d YYYY-MM] [--output FORMAT] [-q, --quiet]
* View monthly usage for a resource group (account admin or resource group admin only):

ibmcloud billing resource-group-usage GROUP_NAME [-d YYYY-MM] [--output FORMAT] [-q, --quiet]
* View monthly resource instances usage under the current account:

ibmcloud billing resource-instances-usage [-o ORG] [-g RESOURCE_GROUP] [-d YYYY-MM] [--output FORMAT] [-q, --quiet]
Members 50 per pool 
 Policies N/A 
 Rules N/A 
 Security Groups N/A 
 Subnets 1 per load balancer 







 Routing tables and routes 



Table 9. Quotas for routing tables and routes

 Resource Quota 

 Routing tables per VPC 50 
 Routes per routing table 200 



Each route has a destination property, which includes a prefix length (/24 in 10.2.0.0/24). The number of unique prefix lengths that are supported per custom routing table is 14. Multiple routes with the same prefix count as only one unique prefix.





 Reserved IP addresses 



Table 10. Quotas for reserved IP addresses

 Resource Quota 

 Reserved IP addresses 20,000 per region 







 Block storage volumes and snapshots 



Table 11. Quotas for block storage volumes and snapshots

 Resource Quota 

 Boot and secondary volumes 300 total VPC volumes per account in a region 
 Snapshots and backup snapshots Up to 750 per volume in a region 







 File shares 



Table 12. Quotas for file shares

 Resource Quota 

 File shares 300 total file shares per account in a region 







 Placement groups 



Table 13. Quotas for placement groups

 Resource Quota 

 Placement groups 100 placement groups per account in a region 
 Instances 12 instances per placement group per region with host_spread placement group strategy. 
 Instances 4 instances per placement group per region with power_spread placement group strategy. 



The quotas for placement groups are set and can't be adjusted.







 Service limits 

The following table displays current VPC service limits. Unlike quotas, these limits can't be adjusted.



Table 14. Limits for VPC resources

 Resource Limit 

 VPCs with classic access 1 per region 
 Network interfaces 5 per instance 
 PCI network interfaces for bare metal servers 8 per bare metal server 
 Public Gateways 1 per zone per VPC 
 Security groups 5 per network interface (NIC) on a virtual server instance 
 Remote rules for security groups 5 per security group 
 Secondary volumes per instance Up to 12 secondary volumes 
 Instance groups for auto scale and more 200 per account 
 Instance group memberships 1000 per instance group
All prices mentioned on this page are illustrative and do not represent the actual amounts used for billing. To calculate the exact pricing, use the [IBM cost estimator](https://cloud.ibm.com/estimator).



Table 2. Monthly LPAR charges

 Hours elapsed in a month Amount charged LPAR description 

 300 hours (300 hours x $0.343)/month = $103 1 core, 8 GB memory, 150 GB disk, AIX 
 430 hours (430 hours x $0.465)/month = $200 1 core, 16 GB memory, 150 GB disk, AIX 
 730 hours (Monthly Total) $103 + $200 = $303 (Monthly Total) 1 core, 16 GB memory, 150 GB disk, AIX 



In this example, the LPAR resources are increased (after reaching 300 hours in the month) from 8 GB to 16 GB of memory. The price of the LPAR is prorated by the hour for the final monthly price of $303.

For detailed usage and billing information, you can refer to the part number in your invoice. The part numbers in the invoice represent the charge unit. Refer to the following table to view the part numbers and its corresponding description.



 Part number Description 

 SOS_VIRTUAL_PROCESSOR_CORE_HOURS Scale out shared uncapped processor per core-hour 
 SOD_VIRTUAL_PROCESSOR_CORE_HOURS Scale out dedicated processor per core-hour
Therefore, 4 of your 14 running worker nodes are deleted, to make the number of worker nodes equal to the total capacity of 10 reserved worker nodes.

To avoid an unexpected deletion, scale down your worker pools before the contract ends to the remaining capacity in the reservation. Or, add contracts to your reservation so that you continue to have enough reserved capacity for the worker nodes that you need.





 Billing and discounts 

How much is the discount? Can I combine reservations with other discounts?
: The discounts vary by the flavor, location, and term of the contract, but typically users realize a significant cost savings compared to on demand worker nodes.



* 33% or more for 1 year terms.
* Up to 50% for 3 year terms.



These discounted reserved worker nodes are in addition to any current account-level discounts that you might have, such as discounts from an IBM Cloud subscription account.

How am I billed? How are my discounts applied?
: When you create a contract, a discounted monthly price for the total number of worker nodes is calculated. Then, this cost is applied for each month in the term. You are billed each month for the discounted cost, regardless of how many worker nodes that you use during the month. Keep in mind that the price of each new contract is fixed at the time that the contract is created for the lifetime of the contract.

Consider the following example. You create a contract on 15 December 2020 for 12 worker nodes for a 1 year term, until 15 December 2021. The total discounted cost for all 12 worker nodes for the entire term is calculated at $12,000. For each full month, you are billed a flat rate of $1,000, regardless of how many worker nodes in the reservation are in use. For the first and last months, you are billed a pro-rated amount, according to the dates that the contract is active in the months.

If I don't need reserved worker nodes anymore, can I modify my contract?
: No, you can't modify the terms of the contract, such as the duration, number of worker nodes, or flavor. You can remove any unneeded worker nodes from your clusters, but you can't get a refund for unused capacity in your reservation.
If the plan you select has an instance price, the price for the instance includes a set number of entity IDs and API calls that are included in the instance price. If you exceed the included allotment, your instance continues to operate normally but you accumulate an overage charge based on the published rate for entity IDs and API calls.

The Active Entity ID cost is based on the number of unique entities that interact with your App Configuration instance during the month. Entities self-identify when an API call is made, and each instance of your application provides a unique entity ID. You are not charged for entities that do not call App Configuration during the month. If your pricing plan includes a free allotment of Active Entity IDs, then you are not charged until the allotment is exceeded.

Active Entity ID cost can be difficult to predict so you need to closely monitor your historical activity. See [How to view usage metrics for App Configuration?](https://cloud.ibm.com/docs?tab=faqsfaq-ac-metrics) Rely on your own domain knowledge, business metrics, and usage forecasts to predict Active Entity ID cost.

The API Call cost is based on the number of API calls sent or received by App Configuration during the month over all your entities combined. Check section - [What are the charges to use App Configuration?](https://cloud.ibm.com/docs?tab=faqsfaq-ac-charges) to determine what constitutes an API call.

If your pricing plan includes a free allotment of API calls, then you are not charged until the allotment is exceeded. Closely monitor your historical activity and check out [How to view usage metrics for App Configuration?](https://cloud.ibm.com/docs?tab=faqsfaq-ac-metrics) Rely on your own domain knowledge, business metrics, and usage forecasts to predict cost.
* Can you give some example pricing scenarios?



 Pricing Scenario 1: Mobile App with Feature Flags 

Assume you have a mobile app and you want feature flags and targeted segments to roll out features incrementally to different sets of users. Your historical metrics show 200,000 users but only about 50% are active in a month.