vania-janet/multiturn-rag-retrieval-data huggingface dataset:
FAQs for bandwidth metering 

You can review answers to some frequently asked questions about bandwidth metering.



 How is bandwidth metering priced? 



* Public bandwidth egress (or bandwidth allocation) pricing depends on regions. To learn more, visit [Bandwidth packages from IBM Cloud](https://www.ibm.com/cloud/bandwidth) and contact a specialist.
* Public bandwidth usage over GB allocation is charged per GB.







 What IMS permissions do I need to view and change bandwidth allocations (or add and remove devices to and from bandwidth pools)? 

The BANDWIDTH_MANAGE IMS infrastructure classic permission is the only required permission for bandwidth metering. After you allow this permission, you can complete the following actions:



* Create a bandwidth pool
* Move a device into or out of a pool
* Void a device’s move into a pool
* Cancel a pool



Certain actions pertaining to bandwidth pools, including visibility, might be constrained based on device-level permission. Reconcile your device-level permissions on specific devices to manage their bandwidth and membership in pools.





 Why don't I see the same number of devices as displayed on the devices count? 

This issue might be due to permission restrictions because some users do not have permission to view specific devices. This issue might also be the result of devices that were reclaimed in the middle of the billing cycle, but are still contributing to the cost of the pool.





 What kind of devices generate bandwidth? 

Compute devices use bandwidth. For example, devices that generate bandwidth include bare metal servers, virtual servers, firewalls (FSA 10G), and Netscaler devices.





 Why doesn't the allocation display the same value that I ordered? 

The allocation that is shown is related to the proration policy. For example, imagine that you order 20 TB of bandwidth on the 15th of the month. The allocation that is shown on the bandwidth summary page will show 10 TB until the next billing cycle. Then, the allocation displays the full amount of what was ordered.





 What is the maximum number of devices that I can attach to a bandwidth pool? 

You can attach an unlimited number of devices to a bandwidth pool.





 Is there a charge for traffic on the Classic Private Network?
2020/01/10 21:27:50 Terraform plan | provisioning_status: "active" => <computed>
2020/01/10 21:27:50 Terraform plan | target_address: "172.16.1.4" => "172.16.1.4"
2020/01/10 21:27:50 Terraform plan | weight: "50" => <computed>
2020/01/10 21:27:50 Terraform plan 
2020/01/10 21:27:50 Terraform plan | -/+ ibm_is_lb_pool_member.lb1-pool-member2 (new resource required)
2020/01/10 21:27:50 Terraform plan | id: "r006-11cb7734-e05c-405b-9e35-20e05bc2766f/r006-d917d290-071a-4da1-a995-91262ea89f2c/r006-5418feb7-2169-47c3-8c71-66a86fec6d9a" => <computed> (forces new resource)
2020/01/10 21:27:50 Terraform plan | health: "ok" => <computed>
2020/01/10 21:27:50 Terraform plan | href: "https://us-south.iaas.cloud.ibm.com/v1/load_balancers/r006-11cb7734-e05c-405b-9e35-20e05bc2766f/pools/r006-d917d290-071a-4da1-a995-91262ea89f2c/members/r006-5418feb7-2169-47c3-8c71-66a86fec6d9a" => <computed>
"resource_instance_id": "crn:v1:bluemix:staging:database-service:us-south:a/1c8ae972c35e470d994b6faff9494ce1:793ff3d3-9fe3-4329-9ea0-404703a3c371::",
"plan_id": "da40662d-2f72-4a19-8c79-8c77cf285e17",
"measured_usage":
{
"measure": "QUERIES",
"quantity": 100
},
{
"measure": "STORAGE",
"quantity": 123.456
}
]
},
{
"start": 1485910800000,
"end": 1485910800000,
"resource_instance_id": "ed20abbe-8870-44e6-90f7-56d764c21127",
"plan_id": "da40662d-2f72-4a19-8c79-8c77cf285e17",
"measured_usage":
{
"measure": "instances",
"quantity": {
"previous": 0,
"current": 1
}
}
]
}
]
Show more

To submit usage for your active service instances, call the [Usage Metering API](https://cloud.ibm.com/apidocs/usage-meteringreport-resource-usage) as shown in the following sample request. To make the API call, your metering approval request must be approved by IBM Cloud.

You can find the resource_id value, which is the Global catalog ID listed on the Brokers page in Partner Center.



* Curl
* Java
* Python
* Go
* Node
* Usage is invoiced to the enterprise account for the entire month when the account was added. For example, if you add an account to the enterprise on 15 June, all of the usage for the month of June is reflected in the July invoice.







 Shared credit pool 

The enterprise credit pool consolidates credit from all accounts in the enterprise and shares it with the accounts. The pool includes credit from all sources, including platform subscription credit, promotional credit, and support credit. When accounts in the enterprise create and use resources, the cost for this usage is deducted from the credit pool.

When existing subscriptions are added to the enterprise, each individual subscription term is re-created within the credit pool, including characteristics such as the remaining credit balance, start dates, and end dates. As credit is used, the subscription terms burn down individually according to when they expire. For example, you imported two accounts with existing subscriptions in August 2019. One subscription, 32100456, is for $1,000 for 18 months that began in January 2019. Because it spans multiple years, the subscription is divided into terms of up to one year each. The other subscription, 55543210 is for $500 a month for two years that began in April 2019, which is also divided into multiple terms. Then, you purchased a new one-year subscription, 00012345, through your enterprise for $1,500 a month that starts in July 2020. As enterprise users use resources, credit is deducted from the first term from subscription 32100456 because it expires the soonest, then the first term from subscription 55543210 because it expires next, and so on. This behavior ensures optimum usage of your purchased subscription credit.



Table 1. Subscriptions in an enterprise credit pool
This table has column headers and a summary row. The row headers identify the subscription and attributes. The last row has a header in the first column and a summation of values from previous rows in the second column.

 Originating Subscription Remaining Credit Valid From Valid Until 

 IBM Cloud Platform - 32100456, term 1 $5,000 2019-01-01 2019-12-31
For support subscriptions that were bought before this date, credit is available on a month-to-month basis. When you buy or renew a support subscription, any existing active support subscriptions are converted to the term-based model for the remainder of their term.

For example, you might have a support subscription for $200 per month with three months remaining. When you buy a new support subscription, the existing subscription is converted to a new one with $600 of credit that can be used anytime within those three months.





 Viewing subscription usage 

You can view the subscriptions in your account to track your credit spending. To access this information, you need an access policy with the Viewer role or higher on the Billing account management service. See [IAM access](https://cloud.ibm.com/docs/account?topic=account-userroles) for more information.



 Platform subscriptions 

To view your platform and service subscription usage, in the IBM Cloud® console, go to Manage > Billing and usage, and select Subscriptions.



* Click the tabs to view spending details and trends about your subscription usage, including any usage overages that your account incurred. For example, the credit burndown view displays how your credit balance changes over time, and the spending by month view displays your monthly spending from all subscriptions.
* View all active and inactive subscriptions in your account in the tables. For multi-year subscriptions, each term is displayed separately. Active subscriptions are subscriptions that still have remaining credit to spend and time that's left in the subscription term. Upcoming subscriptions are subscriptions were added to the account but haven't yet reached their term period. A subscription is inactive if its term expires or all of its credit is spent.



You can use the spending and usage information on the Subscriptions page to evaluate whether your subscriptions suit your usage needs. For example, if you consistently have overages, you might increase your monthly spending commitment to save money on that usage. To buy new subscriptions or change future subscription amounts, contact [IBM Cloud Sales](https://www.ibm.com/cloud?contactmodule).





 Support subscriptions
Standard The monthly instance price includes 1000 active entity IDs and 100,000 API calls. This plan includes feature flags in addition to the property management capabilities. 
 Enterprise The monthly instance price includes 10,000 active entity IDs and 1,000,000 API calls. This plan includes percentage rollout and targeting segments in addition to property management and feature flags that are found in the Standard plan. 







 What are the charges to use App Configuration? 

The fundamental pricing metrics for App Configuration are Application Instance, Active Entity ID, and API Call.

Application Instance - An Application Instance is a uniquely named copy of App Configuration created by you but managed by IBM. Multiple instances of App Configuration within a single environment are all considered separate application instances, as are individual App Configuration instances in multiple environments (such as test, development, staging, or production).

A single instance of App Configuration can serve multiple environments, and in fact the service is designed to do so.

Active Entity ID - An active entity ID is a unique identifier for each entity that interacts with the App Configuration service. For example, an entity might be an instance of an app that runs on a mobile device, a microservice that runs on the cloud, or a component of infrastructure that runs that microservice. For any entity to interact with App Configuration, it must provide a unique entity ID. This task is most easily accomplished by programming your app or microservice to send the Entity ID by using the App Configuration SDK.

API Call - An API call is the invocation of the App Configuration through a programmable interface.

Exactly what constitutes an API call varies depending on the entity type (for example, a microservice or a mobile app). For server-side entities like microservices, when the state of a feature flag or property changes in the App Configuration, a websocket connection notifies the SDK in the microservice that a state change occurred. The microservice then calls back into the App Configuration to retrieve the update. This action is an API call.

An API call also occurs on startup to the retrieve the initial configuration state. For client-side entities like mobile apps, websockets are not used.
What is Event Streams's maximum message size? 

Event Streams's maximum message size is 1 MB, which is the Kafka default.





 What are Event Streams's replication settings? 

Event Streams is configured to provide strong availability and durability. The following configuration settings apply to all topics and cannot be changed:



* replication.factor = 3
* min.insync.replicas = 2







 What are the restrictions and defaults for topics and partitions? 



* Topic names are restricted to a maximum of 100 characters.
* The default number of partitions for a topic is one.
* Each IBM Cloud space has a limit of 100 partitions. To create more partitions, you must use a new IBM Cloud space.







 How do I check which Event Streams plan I've provisioned? 

To confirm which type of Event Streams plan you've provisioned (Lite, Standard, or Enterprise), complete the following steps:



1. In the IBM Cloud console, navigate to the instance of Event Streams that you want to check.
2. Click the Plan tab in the navigation pane on the left. The Current plan section displays your plan type.







 Can I change my Event Streams plan using the IBM Cloud console? 

Yes, but only if you are moving from the Lite plan to the Standard plan.



1. In the IBM Cloud console, navigate to the instance of Event Streams Lite plan that you want to change.
2. Click the Plan tab in the navigation pane on the left.
3. In the Change pricing plan section, check the Standard box. Click Upgrade.

Allow a few minutes for the cached limit of 1 partition for the Lite plan to clear so that you can take advantage of the 100 partition limit for the Standard plan.

However, this option does not currently work in the IBM Cloud console for any other combination of plans. For example, if you try a different plan combination, you'll see an error message like the the following:

Could not find VCAP::CloudController::ServicePlan with guid: ibm.eventstreams.standard







 What are the differences between the Event Streams Standard and Event Streams Enterprise plans?
: 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.](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-exclusion_rules)Usage Quotas rules are triggered dynamically based on your defined thresholds while other exclusion rules are always in effect.
* If the quota is set to a value lower than what has been consumed and sent to storage, all incoming logs after the rule value has been set will be discarded.
* If you change your daily or monthly usage quota, all exclusion rules will be automatically disabled. For example, if your set your monthly usage quota to 100 GB, and you have three daily exclusion rules configured to that quota, if you change your monthly usage quota to a different value the exclusion rules will be disabled. You can reenable them if desired. Exclusion rules are automatically disabled to help avoid having having logs being unintentionally discarded.







 Configuring usage quotas 

You can configure quotas and what is done when various thresholds are reached.



 Accessing usage quotas 

To configure Usage Quotas, access the Usage Quotas settings by doing the following:

The Usage Quotas option is in the left-pane of the LogDNA application, under Settings > Usage .



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).

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.
Use the index rate to analyze and predict costs associated with storage of searchable data. [Learn more about index rate analysis](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-control_usage_index_rate).

Managing and limiting data usage
: In your Activity Tracker instance, 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. [Learn more about usage quotas](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-control_usage_quotas).





 4 October 2021 

API for Archiving
: Documentation of API changes supporting archiving is generally available. [Learn more about the archiving API](https://cloud.ibm.com/apidocs/activity-trackerget-v1-config-archiving).





 1 October 2021 

API for data streaming
: Documentation of API changes supporting data streaming is generally available. [Learn more about the streaming API](https://cloud.ibm.com/apidocs/activity-trackerpost-v1-config-stream).





 13 August 2021 

Data streaming support
: Feature to stream data from an IBM Cloud Activity Tracker instance to other corporate tools such as Security Information and Event Management (SIEM) tools is generally available. [Learn more about streaming](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-streaming).





 2 July 2021 

Support to stream data is available in beta
: New beta feature released in US-South and Frankfurt to stream data from an IBM Cloud Activity Tracker instance to other corporate tools such as Security Information and Event Management (SIEM) tools. [Learn more about streaming](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-streaming).





 31 March 2021 

New CLI support
: New CLI added that can be used to list instances and export data from an instance.
firewallEventsAdaptiveGroups 30 days 
 healthCheckEventsGroups 90 days 
 healthCheckEvents 90 days 
 httpRequestsAdaptiveGroups 30 days 
 httpRequests1dGroups 365 days 
 httpRequests1hGroups 90 days 
 httpRequests1mGroups 7 days 
 loadBalancingRequestsGroups 30 days 
 loadBalancingRequests 30 days 
 synAvgPps1mGroups 7 days 





 Query settings for account limits 

To obtain specific information regarding limits for a data node, use the settings node.



Table 3. Settings node fields

 Field Description 

 enabled Returns true if the data set (node) is available for the current plan. 
 maxDuration Defines the maximum time period (in seconds) that can be requested in one query (varies by data node). 
 maxNumberOfFields Defines the maximum number of fields that can be requested in one query (varies by data node). 
 maxPageSize Defines the maximum number of records that can be returned in one query (varies by data node). 
 notOlderThan Limits how far back in the record a query can search (in seconds, varies by data node and plan). 



The following is an example query:

{
viewer {
zones(filter: { zoneTag: $zoneTag }) {
settings {
browserInsightsAdaptiveGroups {
maxDuration
maxNumberOfFields
maxPageSize
enabled
notOlderThan
}
}
}
}
}

The query response follows:

{
"data": {
"viewer": {
"zones": [
{
"settings": {
"browserInsightsAdaptiveGroups": {
"enabled": true,
"maxDuration": 2592000,
"maxNumberOfFields": 30,
"maxPageSize": 10000,
"notOlderThan": 2595600
}
}
}
]
}
},
ibmcloud billing resource-group-usage 

Show 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]



 Command options 

GROUP_NAME (required)
: Name of the resource group.

-d MONTH_DATE (optional)
: Display data for the month and date that is specified by using the YYYY-MM format. If not specified, usage of the current month is shown.

--output FORMAT (optional)
: Specify output format. Only JSON is supported.

-q, --quiet (optional)
: Suppress verbose output.







 ibmcloud billing resource-instances-usage 

Show 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]



 Command options 

-o ORG_NAME (optional)
: Filter instances by organization.

-g GROUP_NAME
: Filter instance by resource group.

-d MONTH_DATE (optional)
: Display data for month and date that is specified by using the YYYY-MM format. If not specified, usage of the current month is shown.

--output FORMAT (optional)
: Specify output format. Accepted inputs are JSON and CSV.

-q, --quiet (optional)
: Suppress verbose output.







 ibmcloud billing enterprise-usage 

Show enterprise usage reports:

ibmcloud billing enterprise-usage [--account-group ACCOUNT_GROUP_NAME | --account-group-id ACCOUNT_GROUP_ID | --account ACCOUNT_NAME | --account-id ACCOUNT_ID] [--month MONTH] [--children] [--output FORMAT] [-q, --quiet]



 Command options 

--account ACCOUNT_NAME (optional)
: Name of target account.

--account-id ACCOUNT_ID (optional)
Day 3 to Day 15 1 1 / 1 (5.5 + 3.5 + (1 + 13) / 15 1.4666 (On Day 15 EOD) 
 Day 15 to Day 30 0 0 / 1 (5.5 + 3.5 + (1 * 12) + (0 * 15) / 30 0.7333 (On Day 30 EOD) 



* As seen on the same day as when the usage was submitted.





 Daily proration Max 

Calculate the maximum usage per day and average it for the month. The maximum of each day is added up and divided by the number of days currently passed (in Coordinated Universal Time).

Formula: Summation(daily max) / number of days passed in billing period

The quantity might change throughout the month, but what is rated is the maximum usage per day.

Given a 30-day month, see the following table to calculate the maximum usage per day and monthly average:



Table 6. Maximum usage per day and monthly average calculations

 Time Usage Daily Max Calculation Quantity in dashboard* 

 Day 1 (morning) 0 MAX(0) 0 / 1 0 
 Day 1 (night) 1 MAX(0, 1) 1 / 1 1 
 Day 2 to Day 15 1 MAX(1) (1 + 1 + ...) / day 1 
 Day 15 to Day 30 0 MAX(0) (1 + (1 * 14) + 0 + ...) / day < 1 



* As seen on the same day as when the usage was submitted.





 Monthly proration 

Divides the usage cost at the time of service creation by the remaining number of days in the month (in UTC, including the current day). Each subsequent month is not prorated. The full monthly charge is applied, regardless of how much the instance is used.

Formula:



* If provisioned date is from the current month: (Unit Price) * (Number of days that are remaining in the month / Number of days in the month)
* If provisioned date is from the previous month: (Unit Price)



Given a 30-day month, see the following table to calculate the monthly prorated cost:



Table 7. Monthly prorated cost calculations

 Time Usage Calculation Quantity in dashboard
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 
 Day 2 (morning) 0 MAX(10, 0) 10 
 Day 3 (morning) 15 MAX(10, 15) 15 
 Day 4 (night) 1 MAX(15, 1) 15 







 Daily proration Average 

Calculate the average usage for each day and average it for the month. The average of each day is added and divided by the number of days currently passed (in UTC).

Formula: Summation(daily average) / Number of days passed in the billing period

The quantity might change throughout the month, but what is rated is the average usage per day.

Given a 30-day month, use the following table to calculate the daily proration average:



Table 5. Average usage per day and monthly average calculations

 Time Usage Daily average Calculation Quantity in dashboard* 

 Day 1 (morning) 8 8 / 1 8 / 1 8 
 Day 1 (night) 3 (8 + 3) / 2 5.5 / 1 5.5 (On Day 1 EOD) 
 Day 2 (morning) 2 2 / 1 (5.5 + 2) / 2 3.75 
 Day 2 (night) 5 (2 + 5) / 2 (5.5 + 3.5) / 2 4.5 (On Day 2 EOD) 
 Day 3 to Day 15 1 1 / 1 (5.5 + 3.5 + (1 + 13) / 15 1.4666 (On Day 15 EOD) 
 Day 15 to Day 30 0 0 / 1 (5.5 + 3.5 + (1 * 12) + (0 * 15) / 30 0.7333 (On Day 30 EOD) 



* As seen on the same day as when the usage was submitted.





 Daily proration Max