vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ibmcloud oc quota ls [--provider PROVIDER] [--output json]

Minimum required permissions
: Viewer platform access role for IBM Cloud Kubernetes Service

Command options:

--provider (classic | vpc-gen2)
: The infrastructure provider type to list quota and limits for.

--output json
: Optional: Prints the command output in JSON format.

Example:

ibmcloud oc quota ls







 subnets command 

Virtual Private Cloud

Classic infrastructure

List available subnets in all resource groups in your IBM Cloud infrastructure account.

ibmcloud oc subnets [--provider (classic | vpc-gen2)] [--vpc-id <VPC_ID> --zone <VPC_ZONE>] [--location LOCATION] [--output json] [-q]

Minimum required permissions
: Viewer platform access role for IBM Cloud Kubernetes Service

Command options:

--provider (classic | vpc-gen2)
: The infrastructure provider type to list subnets for. This option is required to list VPC subnets.

--vpc-id VPC_ID
: The ID of the VPC to list subnets for. This option is required when you specify the vpc-gen2 provider type. To list VPC IDs, run ibmcloud oc vpcs.

--zone VPC_ZONE
: The zone to list VPC subnets for. This option is required when you specify a VPC provider type.

-l, --location LOCATION
: Filter output by a specific location. To see supported locations, run ibmcloud oc locations. To specify multiple locations, use one option for each location, such as -l dal -l seo.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.

Example:

ibmcloud oc subnets -l ams03 -l wdc -l ap





 vlan commands 

Classic infrastructure
"percentage_of_total": 9.130321057818866
},
{
"name": "kms",
"current_total": 205699,
"percentage_of_total": 8.608651799894956
},
{
"name": "is-load-balancer",
"current_total": 107925,
"percentage_of_total": 4.516739242794874
}
]
Show more





 List usage data for a specific service for the past 6 months 

By specifying the <SERVICE_NAME>, the usage data for only that service is returned. The <SERVICE_NAME> is the [CRN service name](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-cloud_services) for the service.

curl "https://api.us-south.logging.cloud.ibm.com/v1/usage/hosts/<SERVICE_NAME>" -u <SERVICE_KEY>:

For example, if you want to query usage data for the IBM Key Protect service you would run the following:

curl "https://api.us-south.logging.cloud.ibm.com/v1/usage/hosts/kms" -u <SERVICE_KEY>:

And the output would be similar to the following:

[
{
"name": "kms",
"current_total": 205699,
"percentage_of_total": 8.608651799894956
}
]





 List usage data for a specific service over the past 10 days 

The following will list the aggregated usage information for the <SERVICE_NAME> service over the past 10 days.

curl "https://api.us-south.logging.cloud.ibm.com/v1/usage/hosts/<SERVICE_NAME>?from=$(($(date +%s)-864000))&to=$(date +%s)" -u <SERVICE_KEY>:
After you log in with your user ID and password, the IBM Cloud dashboard opens.
2. Click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/icons/icon_hamburger.svg) > Observability.
3. Select Activity Tracker.

The list of IBM Cloud Activity Tracker instances is displayed.

There is 1 instance per region.
4. Select the instance in the region where you want to view events. Then, click Open Dashboard.
5. In the web UI, click the Settings icon ![Settings icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/admin.png) > Usage > Usage Quotas.







 Enabling and disabling Usage Quotas 

To enable Usage Quotas make sure the selection at the top of the dialog is set to on. To disable the Usage Quota configuration, make sure the selection is set to off. Usage Quotes are disabled by default.





 Setting up your usage quotas 

When you first access the Usage Quotas dialog you will see the daily and monthly quotas set for your instance.

To change the daily and monthly quotas, do the following:



1. Click Edit Usage Quotas
2. Change the Daily Usage Quota and Monthly Usage Quota to your desired values. The quotas can be specified in MB, GB, or TB. These are hard quotas.
3. Select what you would like to occur when the quotas are reached.

Discard logs when the Daily Usage Quota is reached until midnight UTC
: If selected, when the daily quota is reached within a 24-hour period at UTC, logs will no longer be saved.

Discard logs when the Monthly Usage Quota is reached until the next billing cycle
* [Increase your quota limits for pull traffic](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_quotaregistry_quota_set).



Pull traffic across public connections counts toward usage and quota. Pull traffic across private connections doesn't count.

The following example is for the standard plan:
: In the month, your quota limit for pull traffic is set to 5 GB. You already pulled images from your namespaces and used 4.5 GB of this pull traffic. You have 0.5 GB pull traffic available until you reach your quota limit. One user wants to pull an image from your namespace with a size of 1 GB. Because the quota limit is not yet reached, Container Registry allows the user to pull this image.

After the image is pulled, Container Registry determines the bandwidth that you used during the pull and checks whether the limit for pull traffic is reached. In this example, the pull traffic usage increases from 4.5 GB to 5.5 GB. With your current quota limit set to 5 GB, Container Registry prevents you from pulling images from your namespace.







 Cost of Container Registry 

You can see the costs of IBM Cloud Container Registry in the pricing plans section of the offering details page, see [Container Registry](https://cloud.ibm.com/registry/catalog).







 Upgrading your service plan 

You can upgrade your service plan to benefit from unlimited storage and pull traffic usage to manage the Docker images for all namespaces in your IBM Cloud account.

If you want to find out what service plan you have for the registry region that you're targeting, run the ibmcloud cr plan command.

To upgrade your service plan, complete the following steps.



1. Log in to IBM Cloud.

ibmcloud login

If you have a federated ID, use ibmcloud login --sso to log in to the IBM Cloud CLI. Enter your username and use the provided URL in your CLI output to retrieve your one-time passcode. If you have a federated ID, the login fails without the --sso and succeeds with the --sso option.
2.
If a service offers a metered plan, IBM Cloud users are charged based on the amount of resources that they use. For example, IBM Cloud users that use database services might be charged based on the amount of storage that their applications use. Usage submission must occur in order for the usage to be converted into a chargeable record.

All integrated billing services that offer a metered plan must use the IBM Cloud metering service to report usage data.

You’re required to automate hourly usage submission by using metering service API if you offer a metered plan.

For more information on metering, see [Metering integration](https://cloud.ibm.com/docs/sell?topic=sell-meteringinterameteringintera). For more information on submitting metered usage, see [Submitting usage for metered plans](https://cloud.ibm.com/docs/sell?topic=sell-submitusagesubmitusage).





 Provisioning scenario: Pulling it all together 

Now let's pull all of the concepts together and look at an example of how service instance creation works by using the IBM Cloud platform.

Zoom

![Provisioning scenario](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/sell/images/flow-am.svg)

Figure 1. How the platform handles service instance creation



 Creating a service instance by using the console 

When a user wants to create a service instance, they can select the service, plan, and use the Create operation.

The IBM Cloud platform validates that the user has permission to create the service instance by using IBM Cloud IAM. After this validation occurs, your service broker's creation endpoint (PUT /v2/resource_instances/:resource_instance_id) is started. For the instance to be created, the following rules must be met:



* The IBM Cloud context is included in the context variable
* The X-Broker-API-Originating-Identity has the IBM IAM ID of the user that started the request
For more information, see [Service keys by using the API](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-service_keysservice_keys_api).
* Replace <LIMIT_NUMBER> with the number of services to be returned from the highest usage to the lowest. If not specified, only the highest-usage service will be returned. <LIMIT_NUMBER> is an integer number.
* Replace <FROM_DATE> with your desired starting date in Unix epoch format. For example, $(($(date +%s)-864000)) would be 10 days ago and $(($(date +%s)-86400)) is 1 day ago. $(date +%s) is today. Dates can be specified as relative values as shown, or a specific integer such as 1633046400.
* Replace <TO_DATE> with your desired ending date in Unix epoch format.



[This website](https://www.epochconverter.com/) can help you calculate the epoch date.





 Output 

The method returns the requested data in JSON format.

[
{
"name": "service name 1",
"current_total": 1418178,
"percentage_of_total": 59.35177415676025
},
{
"name": "service name 1",
"current_total": 287299,
"percentage_of_total": 12.023670768735
}
]

In this case usage for 2 services has been returned. The current_total value reports the number of ingested lines during the queried time period. The percentage_of_total is the percentage of total lines ingested during the time period by all services.





 Additional examples 

The following provide additional, specific usage examples.



 List usage data for all services for the past 6 months 

This command list the aggregated usage information for all services for the past 6 months.
The service includes a minimum threshold for object size and storage period consistent with the intended use of this service for cooler, less-active data.
* Cold Vault is used for cold workloads where data is accessed every 90 days or less - a larger extra retrieval charge ($/GB) is applied each time data is read. The service includes a longer minimum threshold for object size and storage period consistent with the intended use of this service for cold, inactive data.



Flex has been replaced by Smart Tier for dynamic workloads. Flex users can continue to manage their data in existing Flex buckets, although no new Flex buckets may be created. Existing users can reference pricing information [here](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-flex-pricing).

For more information, see [the pricing table at ibm.com](https://cloud.ibm.com/objectstorage/createpricing).

The Active storage class is only used with [One Rate plans](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-onerate), and can not be used in Standard or Lite plans.

For more information about how to create buckets with different storage classes, see the [API reference](https://cloud.ibm.com/docs/cloud-object-storage/api-reference?topic=cloud-object-storage-compatibility-api-bucket-operationscompatibility-api-storage-class).

For each storage class, billing is based on aggregated usage across all buckets at the instance level. For example, for Smart Tier, the billing is based on usage across all Smart Tier buckets in a given instance - not on the individual buckets.





 How do I create a bucket with a different storage class? 

When creating a bucket in the console, there is a menu that allows for storage class selection.

When creating buckets programmatically, it is necessary to specify a LocationConstraint that corresponds with the endpoint used. Valid provisioning codes for LocationConstraint are
   US Geous-standard / us-vault / us-cold / us-smart
Monthly active entity ID overage Overage not allowed overage allowed overage allowed 
 Max monthly active entity IDs per instance 10 Unlimited Unlimited 
 API calls included with instance 5,000 100,000 1,000,000 
 API call overage price Overage not allowed Overage allowed Overage allowed 
 Max monthly API calls per instance 5,000 Unlimited Unlimited 
 Environments 1 15 15 
 Collections 1 20 Unlimited 
 Properties 10 (properties + flags) 1000 Unlimited 
 Property types All All All 
 Max property size 10 kB 10 kB 10 kB 
 Max storage size (all properties) 0.1 MB 10 MB 10 MB 
 Flags 10 (properties + flags) 100 Unlimited 
 Attributes Glean from response and custom attributes Glean from response and custom attributes Glean from response and custom attributes 
 Segments 3 <br><br> * <br><br><br> Unlimited 
 Segment definition rules per segment 3 <br><br> * <br><br><br> 25 
 Max targeting definition rules per instance 3 <br><br> * <br><br><br> 100 
 Targeting definition rules per feature <br><br> * <br><br><br> <br><br> * <br><br><br> 50 
 Delivery mode Websocket (server)pull or get (client) Websocket (server) pull or get(client) Websocket(server)pull or get (client) 
 Role-based access Env-level Env-level Env-level 
 Locations London, Dallas, Washington DC, Sydney London, Dallas, Washington DC, Sydney London, Dallas, Washington DC, Sydney 
 HA Regional Regional Regional 
 Security End-to-end encryption RBAC End-to-end encryption RBAC End-to-end encryption RBAC 
 Monitoring IBM Cloud Monitoring IBM Cloud Monitoring IBM Cloud Monitoring 
 Audit IBM Cloud Activity Tracker IBM Cloud Activity Tracker IBM Cloud Activity Tracker 
 Support per your IBM Cloud support plan per your IBM Cloud support plan per your IBM Cloud support plan 
 Percentage rollout Supported Not Supported Supported 
 Snapshots Not Supported Not Supported Supported 
 KMS integration (BYOK and KYOK) Not Supported Not Supported Supported 



See the App Configuration catalog page for current pricing.





 How do I audit App Configuration activity?
The first 250,000 NLU items are charged at $0.003 per item
Additional NLU items until the 5,000,000th NLU item are charged at $0.001 per item
Estimated price = (250,000 NLU items × $0.003) + (50,000 NLU items × $0.001)
Estimated price = $750 + $50



Total cost = $800





 How do I calculate the Standard Plan price for 15,000 NLU items? 



* Since the first 250,000 NLU items are priced at $0.003/item - your 15,000 NLU items are charged at $0.003 per item (Tier 1). Your estimated price would be $45.







 How do I calculate the Standard Plan price for 6,000,000 NLU items? 



* Since you have more than 5,000,000 NLU items, your first 250,000 NLU items are charged at $0.003 per item (Tier 1), your next 4,750,000 NLU items are charged at $0.001 per item (Tier 2), and your remaining 1,000,000 NLU items are charged at $0.0002 per item (Tier 3). Your estimated price would be $5,700.
Choosing a One Rate plan 

The One Rate plan offers a predictable cost of ownership with an all-inclusive flat monthly charge ($/GB/month) that includes capacity, and built-in allowances for outbound bandwidth and operational requests. The One Rate plan is best suited for active workloads with large amounts of outbound bandwidth relative to storage capacity.

The built-in allowances for outbound bandwidth and operational requests (Class A, Class B) depend on the monthly stored capacity. There is no data retrieval charge. The One Rate plan has four pricing regions: North America, Europe, South America, and Asia Pacific. Furthermore, the plan aggregates billing metrics (storage capacity, outbound bandwidth and operational requests) across multiple instances within the One Rate pricing region for determining the allowances (the higher the aggregated storage capacity within a region, the higher the allowances for outbound bandwidth and operational requests for that region).



 Why use a One Rate plan? 



* Predictable and lower monthly TCO (total cost of ownership) for workloads with high levels of outbound bandwidth to capacity ratios (>20%).
* One Rate plans provide account-level billing that aggregates storage capacity across service instances by region.
* A flat capacity rate with built-in allowances for data access and egress offers a more predictable cost regardless of fluctuating usage patterns.







 Terminology 

Egress: The measure of outbound bandwidth (GB) read over the public endpoints.





 Who should use a One Rate plan? 

One Rate plan instances are more expensive when it comes to storage capacity costs, but much less expensive when taking into account egress charges. You should consider using a One Rate instance if:



1. You are a large enterprise or ISV, and most of the data being stored in Object Storage is constantly being read over the public endpoints.
2. You are reading large files from outside of IBM Cloud - for example in post-production film editing, satellite imaging, or music production.



Most workloads, such as for backups/long-term storage, data analysis using IBM Cloud resources, or for small files (such as PNGs for websites) are better served by a Standard plan.
Type Description 

 standard_add Add quantity from all submitted usage records for a month. 
 standard_max Maximum quantity from all submitted usage records for a month. 
 standard_avg Average quantity from all submitted usage records for a month. 
 dailyproration_max Calculated daily maximum. The sum up all the days for the month. 
 dailyproration_avg Calculated daily average. The sum up all the days for the month. 
 monthlyproration Calculated similar to the daily proration, but the price that is used is the plan price that is divided by the total number of days for the month (daily price). 





 Examples 

The quantity in dashboard value in each of the following examples is before the next usage is submitted, but after the current usage is processed.



 Standard Add 

See the following table for information about how to calculate the monthly usage.

Formula: ADD(usages)



Table 2. Monthly usage calculations

 Time Usage Calculation Quantity in dashboard 

 Day 1 (morning) 5 5 5 
 Day 1 (night) 5 5 + 5 10 
 Day 2 (morning) 5 10 + 5 15 
 Day 3 (morning) 5 15 + 5 20 
 Day 4 (night) 5 20 + 5 25 







 Standard Average 

See the following table for information about how to calculate the average monthly usage. Submitting 0 usage counts toward the average.

Formula: AVG(usages)



Table 3. Average monthly usage calculations

 Time Usage Calculation Quantity in dashboard 

 Day 1 (morning) 4 4 / 1 4 
 Day 1 (night) 0 (4 + 0) / 2 2 
 Day 2 (morning) 5 (4 + 0 + 5) / 3 3 
 Day 3 (morning) 3 (4 + 0 + 5 + 3) / 4 3 
 Day 4 (night) 3 (4 + 0 + 5 + 3 + 3) / 5 3 







 Standard Max 

See the following table for information about how to calculate the maximum monthly usage.

Formula: MAX(usages)



Table 4. Maximum monthly usage calculations

 Time Usage Calculation Quantity in dashboard 

 Day 1 (morning) 5 MAX(5) 5 
 Day 1 (night) 10 MAX(5, 10) 10
Managing usage quotas 

In IBM® Log Analysis, you can use the Usage Quota settings to control how much data is stored so you can manage your data cost while still being able to view and retain the data you need.



 What are usage quotas? 

You can use the Usage Quotas feature to set daily or monthly thresholds for the volume of log files that are to be stored. When the threshold is exceeded, IBM Log Analysis will take the actions you configure.

You can configure the system to:



* Stop storing all logs when the threshold is exceeded.
* Stop storing specific logs based on exclusion rules.
* Create alerts when a usage quote threshold is met.



When you stop storing some or all logs, logs will still be available in the live tail but will be unavailable for historical or audit purposes. Logs that are not stored do not count towards your usage billing.

By setting Usage Quotas you can balance your organization's needs to view, alert, and maintain important logs while balacing the need to manage the cost of data storage.





 Types of usage quotas 

There are three types of usage quotas.

Hard quotas
: A hard quota will stop saving or archiving all logs when the configured daily or monthly quota threshold is reached.

Soft quotas
: A soft quota will stop saving or archiving logs based on the exclusion rules you define. These exclusion rules can be configured to specify which logs to store and which to discard. For example, you can specify exclusion rules to discard rules from a specific host, application, or other query.

Alert-only
: An alert-only quota will send an alert allowing logs to continue to be saved, and your data usage to grow, even though the defined threshold has been exceeded.





 Considerations when using usage quotas 

When you exclude logs using the Usage Quotas function, the excluded logs will not be archived or streamed.

When deciding to use Usage Quotas, consider the following:



* Usage Quotas configured actions are separate from any other [defined exclusion rules.]
List usage data for a specific service over the past 10 days 

The following will list the aggregated usage information for the <SERVICE_NAME> service over the past 10 days.

curl "https://api.us-south.logging.cloud.ibm.com/v1/usage/hosts/<SERVICE_NAME>?from=$(($(date +%s)-864000))&to=$(date +%s)" -u <SERVICE_KEY>:





 List usage data for highest usage service for a 1 month period 

The following will list the usage information for the highest usage service over a specific month. The time period is specified by including a <START_DATE> and END_DATE.

curl "https://api.us-south.logging.cloud.ibm.com/v1/usage/hosts/?from=<START-DATE>&to=<END_DATE>&limit=<LIMIT_NUMBER>" -u <SERVICE_KEY>:

For example, to return the service with the highest data usage in October 2021, that is from October 1, 2021 through November 1 2021, you would run:

curl "https://api.us-south.logging.cloud.ibm.com/v1/usage/hosts?from=1633046400&to=1635724800&limit=1" -u <SERVICE_KEY>:
Limits and quotas for Code Engine 

The following sections provide technical details about the IBM Cloud® Code Engine limitation and quota settings.

How does my resource allocation effect my project quotas and billing?

From the console, you can view information about your current Code Engine resource allocation from your project overview page. If you want to display information about the allocated memory and vCPU values based on what you configured for each specific application or job, then view the listing of your applications or jobs in your project. With the CLI, you can also get information about your current resource allocation usage for the project with the [project get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project-get) command.

With Code Engine, you pay for only the resources that you use based on the configured memory and vCPU that your workloads consume, and any incoming HTTP calls. If your app scales to zero or your job or build isn't running, you are not consuming resources, and so you are not charged. To host all your applications and jobs, Code Engine deploys and manages the necessary infrastructure for you. However, while you are not billed for this infrastructure, it does count toward the project quotas. For more information about quotas, see the following tables.

The use of ephemeral storage is now bounded by memory. The ephemeral storage in Code Engine cannot exceed the default value of 0.4 GB (400 MB) or the configured value for memory. If you need more than the default for ephemeral storage, you must increase your memory according to the valid combinations of vCPU and memory.

See [Supported memory and CPU combinations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-mem-cpu-combo) for more information about the relationship between ephemeral storage and memory.



 Application defaults and limits 

The following table lists the limits for applications.



Application limits

 Category Default Maximum value Need to extend the maximum? 

 CPU 1.0 12.0 [Contact IBM support](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case&interface=ui)