vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The following values are only valid for the specified preset type:

Email

PagerDuty

Slack



Channel configuration values for email presets

 Value Description 

 emails The email addresses where the alert will be sent. 
 timezone (Optional) The preferred timezone. 



Sysdig (IBM Cloud Monitoring)

Webhook



Channel configuration values for Sysdig (IBM Cloud Monitoring) presets

 Value Description 

 key Your API key. 
 severity The severity level associated with the alert. For example, high. 
 url The URL of your IBM Cloud Monitoring instance. 



Examples of channels values can be obtained by [creating presets in the UI](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-preset_ui) and then using the [GET all configured presets](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-preset-apipreset-api-get-all) method to return the channels values for the preset.







 Examples of using the preset configuration API 

The following are examples of how to use the preset configuration API.

In these examples, <SERVICE_KEY> is the [service key](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-service_keys) for your IBM Cloud Activity Tracker instance.



 Creating a preset 

The following sample creates a preset.

curl --request POST https://api.us-south.logging.cloud.ibm.com/v1/config/presetalert 
-H "Accept: application/json" 
-H "Content-Type: application/json" 
-H "servicekey: <SERVICE_KEY>" 
-d '{ "name": "My preset", "channels": ["<CHANNEL>"] }'

A response similar to the following will be returned:
* Adds the --private-only option to the zone network-set command to unset the public VLAN for the worker pool metadata. Subsequent worker nodes in that worker pool zone are connected to a private VLAN only.
* Removes the --force-update option from the worker update command.
* Adds the VLAN ID column to the output of the alb ls and alb get commands.
* Adds the Multizone Metro column to the output of the locations command to designate zones that are multizone-capable.
* Adds the Master State and Master Health fields to the output of the cluster get command. For more information, see [Master states](https://cloud.ibm.com/docs/containers?topic=containers-health-monitorstates_master).
* Updates the help text in various languages.







 Version 0.3.8 

Version 0.3.8 of the CLI was released on 30 April 2019.



* Adds support for [global endpoint functionality](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zonesendpoint) in version 0.3. By default, you can now view and manage all your IBM Cloud Kubernetes Service resources in all locations. You are not required to target a region to work with resources.
* Adds the [ibmcloud ks locations](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_supported-locations) command to list all locations that IBM Cloud Kubernetes Service supports.
* Adds the --location option to the cluster ls and zone ls commands to filter resources by one or more locations. - Adds the --region option to the credential set/unset/get, api-key reset, and vlan spanning get commands. To run these commands, you must specify a region in the --region option.









 Version 0.2 

Review the following changes for 0.2 versions of the CLI plug-in.

Version 0.2 of the CLI plug-in is deprecated.
For example, if 52.137.182.166 is currently registered to your domain and you want to add 52.137.182.270, you must specify --ip 52.137.182.166 --ip 52.137.182.270 in the command.

Minimum required permissions
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster where the domain is applied.

--domain DOMAIN
: Required. The domain you want to update.

--hostname HOSTNAME
: For VPC clusters. The hostname to register for the domain.

--ip IP
: The IP addresses to register for the domain. The IP addresses passed in fully replace those that are currently associated with the domain. If you want to keep the current IP addresses, you must include them. Specifying this flag with no values unregisters the current IP addresses from the domain.

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



 Example ingress domain update command 

ibmcloud ks ingress domain update --cluster CLUSTER --domain DOMAIN [--hostname HOSTNAME] [--ip IP] [-q]







 ibmcloud ks ingress instance default set 

Virtual Private Cloud

Classic infrastructure

Set a registered an IBM Cloud Secrets Manager instance to default. If an existing default instance exists, it will be unset from default.

When you set a new default Secrets Manager instance, any existing secrets that are not managed by IBM Cloud must have their certificate CRN manually updated to match the CRN of the new default instance. To update the CRN, use the ibmcloud ks ingress secret update command. If you do not update the CRN, these secrets do not update at the next scheduled certificate renewal.

ibmcloud ks ingress instance default set --cluster CLUSTER --crn CRN --name NAME [-q] [--secret-group GROUP]

Minimum required permissions
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:
buffered_cover = stc.geohash.geohash_cover_at_bit_depth(poly, 36, distance=50)

Zoom

![Shows buffered geohash coverage at a fixed bit depth for a given geometry.](https://cloud.ibm.com/docs-content/v1/content/cd4be197c8921ed12923aa899ac93a8ab643c158/AnalyticsEngine/images/buffered_cover.png)

Figure 2. Buffered geohash coverage at a fixed bit depth for a given geometry
4. Compute a compact geohash cover by computing the fixed depth cover first and then compressing the cover:

raw_cover = stc.geohash.geohash_cover_at_bit_depth(poly, 36)
compact_cover = stc.geohash.geohash_compression(raw_cover)

Zoom

![Shows compact geohash coverage at a fixed bit depth for a given geometry.](https://cloud.ibm.com/docs-content/v1/content/cd4be197c8921ed12923aa899ac93a8ab643c158/AnalyticsEngine/images/compact_cover.png)

Figure 3. Compact geohash coverage at a fixed bit depth for a given geometry
>>> stc.geohash.neighbors('ezs42')
['ezefp', 'ezs40', 'ezs41', 'ezefr', 'ezs43', 'ezefx', 'ezs48', 'ezs49']
* get_east, get_west, get_north, get_south: Returns the east, west, north, or south geohash for a given geohash:

>>> stc.geohash.get_east('ezs42')
'ezs43'
* Encode a geohash to a BitVector:

>>> bv = geohash.number_hash_encode(p)
>>> bv.truncate(25)
>>> stc.geohash.expand(bv)
[BitVector(0110010110011010011000101),
BitVector(0110010110011010011010000),
BitVector(0110010110011010011010001),
BitVector(0110010110011010011000111),
BitVector(0110010110011010011010010),
BitVector(0110010110011010011010011),
BitVector(0110010110011010011001101),
BitVector(0110010110011010011011000),
BitVector(0110010110011010011011001)]
>>> stc.geohash.neighbors(bv)
[BitVector(0110010110011010011000101),
BitVector(0110010110011010011010000),
BitVector(0110010110011010011010001),
BitVector(0110010110011010011000111),
logging.basicConfig(level=logging.NOTSET)

authenticator = IAMAuthenticator('<ibmcloud-api-key>')

schematics_service = SchematicsV1(authenticator = authenticator)

schematics_service.set_service_url('https://us.schematics.cloud.ibm.com')

logging.info("Started Retrieving the Schematic logs")

workspace_activity = schematics_service.get_workspace_activity(
w_id="<workspace id>",
activity_id="<activity-id>",
).get_result()

print(json.dumps(workspace_activity, indent=2))

logging.info("Completed Retrieving the Schematic logs")
Show more





 Example Python response 

INFO:root:Started Retrieving the Schematic logs
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): iam.cloud.ibm.com:443
DEBUG:urllib3.connectionpool:https://iam.cloud.ibm.com:443 "POST /identity/token HTTP/1.1" 200 1055
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): us.schematics.cloud.ibm.com:443
DEBUG:urllib3.connectionpool:https://us.schematics.cloud.ibm.com:443 "GET /v1/workspaces/us-south.workspace.Sample-Schematics-Api-workspace.0f4b9089/actions/34130efab10d7c792e1c357ac4caf6aa HTTP/1.1" 200 None
{
"action_id": "34130efab10d7c792e1c357ac4caf6aa",
"name": "WORKSPACE_CREATE",
"status": "COMPLETED",
"message": [],
Specifies an output format. Only JSON is supported.



 Examples 

Print available resource groups in JSON format:

ibmcloud resource groups --output json







 -q, --quiet 

Suppresses verbose messages. Prompt messages like Getting information from... as ... do not display if -q, --quiet is specified.



 Examples 

Print available resource groups in quiet mode:

ibmcloud resource groups -q









 ibmcloud help 

Displays the general help for first-level built-in commands and supported namespaces of IBM Cloud CLI, or the help for a specific built-in command or namespace.

ibmcloud help [COMMAND|NAMESPACE]



 Prerequisites 

None.





 Command options 

COMMAND|NAMESPACE
: The command or namespace that help is displayed for. If not specified, the general help for IBM Cloud CLI is shown. Optional.





 Examples 

Display general help for the IBM Cloud CLI:

ibmcloud help

Display help for the dev command:

ibmcloud help dev







 ibmcloud version 

Print the version of the IBM Cloud CLI.

ibmcloud version



 Prerequisites 

None.





 Command options 

None.





 Examples 

Print the version of the IBM Cloud CLI:

ibmcloud version







 ibmcloud api 

Set or view the IBM Cloud API endpoint.

ibmcloud api [API_ENDPOINT] [--unset] [--skip-ssl-validation] [--vpc]



 Prerequisites 

None.





 Command options 

API_ENDPOINT
: The API endpoint that is targeted, for example, https://cloud.ibm.com. If both the API_ENDPOINT and --unset options aren't specified, the current API endpoint is displayed. Optional.

--skip-ssl-validation
: Bypass SSL validation of HTTP requests. This option isn't recommended.

--vpc
: Use a VPC connection for a private API endpoint.

--unset
* [Static provisioning by using existing PVCs with a stateful set](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_static_statefulset)



* [Changing the size and IOPS of your existing storage device](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_change_storage_configuration)
* [Backing up and restoring data](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_backup_restore)



* [Setting up periodic snapshots](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock-snaps)
* [Replicating snapshots to another zone](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock-replicate)
* [Duplicating storage](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock-dupe)
* [Backing up data to IBM Cloud® Object Storage](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock-cos-backup)
* [Copying data to and from pods and containers](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock-cp)



* [Storage class reference](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_storageclass_reference)



* [Bronze](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storagebronze-block)
* [Silver](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storagesilver-block)
import com.ibm.cloud.objectstorage.services.s3.AmazonS3ClientBuilder;
import com.ibm.cloud.objectstorage.services.s3.model.;
import com.ibm.cloud.objectstorage.services.s3.transfer.TransferManager;
import com.ibm.cloud.objectstorage.services.s3.transfer.TransferManagerBuilder;
import com.ibm.cloud.objectstorage.services.s3.transfer.Upload;

import java.io.ByteArrayInputStream;
import java.io.File;
import java.io.IOException;
import java.io.InputStream;
import java.nio.charset.Charset;
import java.sql.Timestamp;
import java.util.List;
import java.util.UUID;

public class JavaExampleCode {
private static AmazonS3 _cosClient;
private static String api_key;
private static String service_instance_id;
private static String endpoint_url;
private static String location;

public static void main(String[] args) throws IOException
{
// Creating a random UUID (Universally unique identifier).
UUID uuid = UUID.randomUUID();

// Constants for IBM COS values
SDKGlobalConfiguration.IAM_ENDPOINT = "https://iam.cloud.ibm.com/oidc/token";
api_key = "<api-key>"; // example: xxxd12V2QHXbjaM99G9tWyYDgF_0gYdlQ8aWALIQxXx4
UUID (required)
: UUID of the service, exclusive with NAME.

-f, --force
: Lock without confirmation.





 Examples 

Lock service ID sample-teset without confirmation:

ibmcloud iam service-id-lock sample-teset -f

Lock service ID ServiceId-cb258cb9-8de3-4ac0-9aec-b2b2d27ac976:

ibmcloud iam service-id-lock ServiceId-cb258cb9-8de3-4ac0-9aec-b2b2d27ac976







 ibmcloud iam service-id-unlock 

Unlock a service ID:

ibmcloud iam service-id-unlock (NAME|UUID) [-f, --force]



 Command options 

NAME (required)
: Name of the service, exclusive with UUID.

UUID (required)
: UUID of the service, exclusive with NAME.

-f, --force
: Unlock without confirmation.





 Examples 

Unlock service ID sample-teset without confirmation:

ibmcloud iam service-id-unlock sample-teset -f

Unlock service ID ServiceId-cb258cb9-8de3-4ac0-9aec-b2b2d27ac976:

ibmcloud iam service-id-unlock ServiceId-cb258cb9-8de3-4ac0-9aec-b2b2d27ac976







 ibmcloud iam api-keys 

List all IBM Cloud platform API keys:

ibmcloud iam api-keys [--uuid]



 Command options 

--uuid
: Show UUID of the API key.







 ibmcloud iam api-key-create 

Create an IBM Cloud platform API key:

ibmcloud iam api-key-create NAME [-d DESCRIPTION] [--file FILE] [--lock]

Using the IBM Cloud CLI login with an API Key does not work with the legacy SL API Key that is found on control.softlayer.com option.
Policy ID: 140555ce-93ac-4fb2-b15d-6ad726795d90
Roles: Administrator
Resources:
Service Name containers-kubernetes
Service Instance df253b6025d64944ab99ed63bb4567b6
Region
Resource Type
Resource
3. If you have either of these policies, skip to the second bullet point of step 4. If you don't have either of these policies, skip to the third bullet point of step 4.



4. Depending on your access policies, choose one of the following options.



* If you have access to the cluster and to the resource group that the cluster is in:



1. Target the resource group. Note: You can't work with clusters in other resource groups until you change this resource group.

ibmcloud target -g <resource_group>
2. Target the cluster.

ibmcloud oc cluster config --cluster <cluster_name_or_ID>



* If you have access to the cluster but not to the resource group that the cluster is in:



1. Do not target a resource group. If you already targeted a resource group, remove the target.

ibmcloud target --unset-resource-group
2. Target the cluster.

ibmcloud oc cluster config --cluster <cluster_name_or_ID>



* If you don't have access to the cluster:



1. Ask your account owner to assign an [IBM Cloud IAM platform access role](https://cloud.ibm.com/docs/openshift?topic=openshift-userschecking-perms) to you for that cluster.
2. Do not target a resource group. If you already targeted a resource group, remove the target.

ibmcloud target --unset-resource-group
3. Target the cluster.

ibmcloud oc cluster config --cluster <cluster_name_or_ID>
Managing IBM Cloud Object Storage (COS) buckets 

Buckets are a way to organize your data in an IBM Cloud Object Storage instance.

To manage buckets, your user must be granted permissions to work with buckets on the IBM Cloud Object Storage instance. For more information about roles, see [Identity and Access Management roles](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam).



 Creating a bucket 

Choose 1 of the following options to create a bucket:



Table 1. Create bucket requests

 Action More info 

 Create a bucket through the IBM Cloud UI [Learn more](https://cloud.ibm.com/docs/atracker?topic=atracker-coscos_create_bucket_ui) 
 Create a bucket through the IBM Cloud CLI [Learn more](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-cli-plugin-ic-cos-cliic-create-bucket) 
 Create a bucket by using cURL [Learn more](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-curlcurl-add-bucket) 
 Create a bucket by using the REST API [Learn more](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-compatibility-api-bucket-operationscompatibility-api-new-bucket) 
 Create a bucket with a different storage class by using the REST API [Learn more](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-compatibility-api-bucket-operationscompatibility-api-storage-class) 
 Create a bucket with Key Protect or Hyper Protect Crypto Services managed encryption keys (SSE-KP) by using the REST API [Learn more](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-compatibility-api-bucket-operationscompatibility-api-key-protect)
: The API endpoint that is targeted, for example, https://cloud.ibm.com. If both the API_ENDPOINT and --unset options aren't specified, the current API endpoint is displayed. Optional.

--skip-ssl-validation
: Bypass SSL validation of HTTP requests. This option isn't recommended.

--vpc
: Use a VPC connection for a private API endpoint.

--unset
: Remove the API endpoint setting.





 Examples 

Set the API endpoint to cloud.ibm.com:

ibmcloud api cloud.ibm.com

Set the API endpoint to cloud.ibm.com and bypass SSL validation.

ibmcloud api https://cloud.ibm.com --skip-ssl-validation

View the current API endpoint:

ibmcloud api

Remove the API endpoint:

ibmcloud api --unset







 ibmcloud config 

Writes default values to the configuration file.

ibmcloud config --http-timeout TIMEOUT_IN_SECONDS --trace (truefalsepath/to/file) 
--color (true|false) | --locale (LOCALE|CLEAR) | --check-version (true|false)



 Prerequisites 

None.





 Command options 

--check-version
: Enable or disable CLI version checking. Valid values are true or false.

--color
: Enable or disable color output. This option is disabled by default. Valid values are true or false.

--http-timeout
: The timeout value for HTTP requests in seconds. The default value is 60 seconds.

--locale<
: Set a default locale. If no value is specified, the previous locale is deleted.

--trace
: Trace HTTP requests to the terminal or specified file. Valid values are true or false.

You can specify only one of the options at a time.





 Examples 

Set HTTP request timeout to 30 seconds:
,"alertid":"398bec1582","immediate":false,"terminal":true,"triggerlimit":1,"triggerinterval":"15m","operator":"absence","emails":"MyUser@mycompany.com"]},{"integration":"webhook","immediate":false,"terminal":true,"triggerlimit":1,"triggerinterval":"30","operator":"presence","bodyTemplate":"{n"name": "{{ name}}",n"sentFrom": "logDNA"n}","url":"https://mycompany.domain.com/webhook/endpoint","alertid":"56dbdca8e7"}],"presetid":"e0f24d3ebf","account":"090bba4d47","name":"Email preset with 2 notifications","_created":"2021-11-18T15:16:50.376Z","_modified":"2021-11-18T15:16:50.376Z"}]





 Get information about a specific preset 

The following sample gets information about a specific preset.

curl --request GET https://api.us-south.logging.cloud.ibm.com/v1/config/presetalert/<PRESET_ID> 
-H "Accept: application/json"
-H "servicekey: <SERVICE_KEY>"

Where <PRESET_ID> is the presetid value returned when [running the GET method to return all presets.](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-preset-apipreset-api-get-all)

A response similar to the following will be returned:
: The wsk API version. This flag is optional.

--authKEY, -uKEY
: The wsk authorization KEY. This flag is optional.

--certSTRING
: The wsk client certificate. This flag is optional.

--cliversion
: The wsk CLI version. This flag is optional.

--keySTRING
: The wsk client KEY. This flag is optional.

--namespaceNAMESPACE
: An IAM namespace name or ID. This flag cannot be set for Cloud Foundry namespaces. This flag is optional.





 Example 

ibmcloud fn property get --auth







 ibmcloud fn property set 

Set a property. At least one flag is required. After a property is set, it is retained on your workstation at <home_dir>/.bluemix/plugins/cloud-functions/config.json. To remove a property, run [ibmcloud fn property unset --<property>](https://cloud.ibm.com/docs/cli?topic=cli-functions-clicli_prop_set).

ibmcloud fn property set [--auth KEY] [--cert STRING] [--key STRING] [--namespace NAMESPACE]



 Command options 

--authKEY, -u
: The wsk authorization KEY. This flag is optional.

--certSTRING
: The wskclient certificate. This flag is optional.

--keySTRING
: The wsk client KEY. This flag is optional.

--namespaceNAMESPACE
: An IAM namespace name or ID. This flag cannot be set for Cloud Foundry namespaces. This flag is optional.





 Example 

ibmcloud fn property set --namespace myNamespace

Output

ok: whisk namespace set to myNamespace







 ibmcloud fn property unset 

Unset a property for the wsk CLI.
Before you create a Logpush job, you must have an [Log Analysis](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-getting-started) instance (for CLI and API use only) or an [Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage) instance with a bucket that has write access granted to IBM Cloud® account cislogp@us.ibm.com. This enables CIS to write request logs into the Object Storage bucket.





 Setting up Logpush using the console 

You can use either Log Analysis instances or Cloud Object Storage buckets as destinations for logpush jobs.



 Creating Logpush with Log Analysis 

To configure a logpush job using Log Analysis, follow these steps.



1. Select the service.



* Choose IBM Log Analysis
* Select the dataset type
* Enter an description
* Click "Next"



2. Configure the destination.



* Select the Log Analysis instance from the list menu
* Enter the region your Log Analysis instance is in
* Enter the Ingress key
* Click "Next"



3. Select the log fields that you want included in the log push.



* Verify that the logpush details are correct
* Select the logpush settings from the Timestamp and Frequency list menus
* Choose whether to enable the logpush job using the Enabled switch
* Select the log fields to include in the logpush job
* Click Connect destination.









 Creating Logpush with COS 

It is recommended that you set up an allowlist that ensures only [CIS IPs](https://cloud.ibm.com/docs/cis?topic=cis-cis-allowlisted-ip-addresses) can push objects into the Object Storage bucket. For more information on configuring an IP allowlist in Object Storage, see [Setting a firewall](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-setting-a-firewall).
,"alertid":"398bec1582","immediate":false,"terminal":true,"triggerlimit":1,"triggerinterval":"15m","operator":"absence","emails":"MyUser@mycompany.com"]},{"integration":"webhook","immediate":false,"terminal":true,"triggerlimit":1,"triggerinterval":"30","operator":"presence","bodyTemplate":"{n"name": "{{ name}}",n"sentFrom": "logDNA"n}","url":"https://mycompany.domain.com/webhook/endpoint","alertid":"56dbdca8e7"}],"presetid":"e0f24d3ebf","account":"090bba4d47","name":"Email preset with 2 notifications","_created":"2021-11-18T15:16:50.376Z","_modified":"2021-11-18T15:16:50.376Z"}]





 Get information about a specific preset 

The following sample gets information about a specific preset.

curl --request GET https://api.us-south.logging.cloud.ibm.com/v1/config/presetalert/<PRESET_ID> 
-H "Accept: application/json"
-H "servicekey: <SERVICE_KEY>"

Where <PRESET_ID> is the presetid value returned when [running the GET method to return all presets.](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-preset-apipreset-api-get-all)

A response similar to the following will be returned: