vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* For a management event, this field is set to false.
* For a data event, this field is set to true.







 eventTime (string) 

This field indicates the timestamp when the event was created.

The timestamp that you see for an event in the UI is set from eventTime and indicates the time when the event was created.

The date is represented as Universal Time Coordinated (UTC).

The format of this field is:

YYYY-MM-DDTHH:mm:ss.SS+0000

For example, a sample eventTime is 2017-10-19T19:07:50.32+0000.





 Initiator fields 

Initiator fields provide information about the user, service, or application that request to run an action in your account.



 initiator.id (string) 

This field provides information about the ID of the initiator that requests the action.

You can find any of the following initiators:



* IBM ID for users that use an IAM token to trigger an action in your account.
* Service ID for services or applications that trigger an action in your account.
* Certificate ID for requests where a certificate is used to trigger an action in your account.
* Profile ID for requests that are run by using a trusted profile







 initiator.name (string) 

This field provides information about the username of the initiator of the action.

This is the human readable name that corresponds to the initiator.id value.

When the initiator is an IBM Cloud service, the field is set to IBM or the name of the service.





 initiator.authnId (string) 

ID of the user that logs in to IBM Cloud.





 initiator.authnName (string) 

Username of the user that logs in to IBM Cloud.





 initiator.typeURI (string) 

This field defines the type of the source of the event.

Valid values are:



* service/security/account/user
* service/security/account/serviceid,
* service/security/client/certificateid
* service/security/clientid
* The requestData.location field includes the specific location of the crypto unit. The location follows this format:

[region].[availability zone].[hardware security module (HSM) module index].[HSM domain index].

For example, if you provision your instance in the us-east region, the value that is returned is similar to [us-east].[AZ2-CSSTAG2].[03].[22].
* The target.id field includes the [Cloud Resource Name (CRN)](https://cloud.ibm.com/docs/account?topic=account-crn) of the crypto unit.
* The target.name field also includes the location of the crypto unit.
* The target.typeURI field includes the URI of the object that the action is targeting at. For example, if you perform the hs-crypto.tke-cryptounit-master-key-register.add action, the value that is returned is hs-crypto/tke-cryptounit/master-key-register.



For the following TKE events, some specific fields indicate more information.



 Add a crypto unit administrator 



* The requestData.adminId field includes the SHA-256 hash of the signature key file that is associated with the administrator to be added.
* The responseData.adminIds field lists the SHA-256 hashes of the signature key files associated with all the administrators that are added to the crypto unit.







 Remove a crypto unit administrator 



* The requestData.adminId field includes the SHA-256 hash of the signature key file that is associated with the administrator to be removed.
* The responseData.adminIds field lists the SHA-256 hashes of the signature key files associated with all the administrators that are added to the crypto unit.







 Set the signature thresholds
* The responseData.totalResources field includes the total number of registrations that are returned in the response.









 Trusted Key Entry events 

The following table lists the returned values that indicate a successful TKE event.



Table 14. Returned values of a successful TKE event

 Field name Returned value 

 outcome success 
 reason.reasonCode 200 
 reason.reasonType OK 



The following common fields for TKE events include extra information:



* The requestData.location field includes the specific location of the crypto unit. The location follows this format:

[region].[availability zone].[hardware security module (HSM) module index].[HSM domain index].

For example, if you provision your instance in the us-east region, the value that is returned is similar to [us-east].[AZ2-CSSTAG2].[03].[22].
* The target.id field includes the [Cloud Resource Name (CRN)](https://cloud.ibm.com/docs/account?topic=account-crn) of the crypto unit.
* The target.name field also includes the location of the crypto unit.
* The target.typeURI field includes the URI of the object that the action is targeting at. For example, if you perform the hs-crypto.tke-cryptounit-master-key-register.add action, the value that is returned is hs-crypto/tke-cryptounit/master-key-register.



For the following TKE events, some specific fields indicate more information.



 Add a crypto unit administrator 



* The requestData.adminId field includes the SHA-256 hash of the signature key file that is associated with the administrator to be added.
* The responseData.adminIds field lists the SHA-256 hashes of the signature key files associated with all the administrators that are added to the crypto unit.







 Remove a crypto unit administrator 



* The requestData.adminId field includes the SHA-256 hash of the signature key file that is associated with the administrator to be removed.
* For a management event, this field is set to false.
* For a data event, this field is set to true.







 eventTime (string) 

This field indicates the timestamp when the event was created.

The timestamp that you see for an event in the UI is set from eventTime and indicates the time when the event was created.

The date is represented as Universal Time Coordinated (UTC).

The format of this field is:

YYYY-MM-DDTHH:mm:ss.SS+0000

For example, a sample eventTime is 2017-10-19T19:07:50.32+0000.





 Initiator fields 

Initiator fields provide information about the user, service, or application that request to run an action in your account.



 initiator.id (string) 

This field provides information about the ID of the initiator that requests the action.

You can find any of the following initiators:



* IBM ID for users that use an IAM token to trigger an action in your account.
* Service ID for services or applications that trigger an action in your account.
* Cloud Foundry (CF) user ID for users that use a UAA token to trigger an action in your account.
* Certificate ID for requests where a certificate is used to trigger an action in your account.
* Profile ID for requests that are run by using a trusted profile







 initiator.name (string) 

This field provides information about the username of the initiator of the action.

This is the human readable name that corresponds to the initiator.id value.

When the initiator is an IBM Cloud service, the field is set to IBM or the name of the service.





 initiator.authnId (string) 

ID of the user that logs in to IBM Cloud.





 initiator.authnName (string) 

Username of the user that logs in to IBM Cloud.





 initiator.typeURI (string) 

This field defines the type of the source of the event.

Valid values are:



* service/security/account/user
* service/security/account/serviceid,
GHz Inc ghzinc1









 ibmcloud ac collection create 

You can create a collection, by using the command:

ibmcloud ac collection create {--file FILE-PATH | --name NAME [--collection_id COLLECTION_ID] [--description DESCRIPTION] [--tags TAGS]}



 Command options 

--name NAME
: Collection name. Required field - input either as a flag or from file.

--collection_id COLLECTION_ID (optional)
: Collection ID. If this value is not provided, name will automatically become the ID. Optional field - input either as a flag or from file.

--description DESCRIPTION (optional)
: Description of the collection. Optional field - input either as a flag or from file.

--tags TAGS (optional)
: Tags associated with the collection. Optional field - input either as a flag or from file.

--file FILE
: Input through the file. File format Supported - JSON





 Example 

To create a collection with name sample using flags ([click here](https://cloud.ibm.com/docs/app-configuration-cli-plugin?topic=app-configuration-cli-plugin-app-configuration-cliac-fileinput) for using commands with --file flag), run the following command:

ibmcloud ac collection create --name sample --collection_id sampleId --description sampleDesc --tags sampleTag



 Output 

The command returns the following output:

collection_id sampleId
description sampleDesc
created_time 2021-01-18T08:15:45Z
updated_time 2021-01-18T08:15:45Z
name sample









 ibmcloud ac collection get 

You can get a collection, by using the command:

ibmcloud ac collection get --collection_id COLLECTION_ID [--expand EXPAND] [--include INCLUDE]



 Command options 

--collection_id COLLECTION_ID
: Collection ID for the collection.

--expand EXPAND (optional)
: Expanded view of the collection details.

--include INCLUDE (optional)
* The target.id field includes the [Cloud Resource Name (CRN)](https://cloud.ibm.com/docs/account?topic=account-crn) of the event.
* The target.name field indicates the target name of the event, such as "mtlscert-admin-key" or "mtlscert-cert".
* The target.typeURI field includes the URI of the object that the action is targeting at. For example, if you perform the hs-crypto.mtlscert-admin-key.create action, the value that is returned is hs-crypto/mtlscert-admin-key.



The specified fields of the following certificate manager events can indicate more information.



 Create the administrator signature key for the certificate administrator 

The following fields include extra information:



* The requestData.accountId field includes the current user ID.
* The responseData.action field includes the action details of the current user.







 Update the administrator signature key for the certificate administrator 

The following fields include extra information:



* The requestData.accountId field includes the current user ID.
* The responseData.action field includes the action details of the current user.







 Remove the administrator signature key of the certificate administrator 

The following fields include extra information:



* The requestData.accountId field includes the current user ID.
* The responseData.action field includes the action details of the current user.







 Get the administrator signature key of the certificate administrator 

The following fields include extra information:



* The requestData.accountId field includes the current user ID.
* The responseData.action field includes the action details of the current user.







 Create or updating certificates by the certificate administrator 

The following fields include extra information:



* The requestData.certificateId field indicates the target certificate.
* The responseData.action field indicates that the certificate is to be created or updated.







 List certificates by the certificate administrator 

The following field includes extra information:



* The responseData.action field indicates all certificates that are managed by current administrator are to be listed.







 Get certificates by the certificate administrator 

The following fields include extra information:
* ibmcloud is load-balancer-listener-policy-rule-create my-lb 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 my-policy --condition equals --type header --field my-app-header --value match-value --output JSON







 Command options 



* LOAD_BALANCER: ID or name of the load balancer.
* LISTENER_ID: ID of the listener.
* POLICY: ID or name of the policy.
* --vpc: ID or name of the VPC. It is only required to specify the unique resource by name inside this VPC.
* --condition: The condition of the rule. One of: contains, equals, matches_regex.
* --type: The type of the rule. One of: header, hostname, path, query, body.
* --value: Value to match the rule condition.
* --field: The HTTP field. This field is applicable to "header", "query", and "body" rule types. For rule type "header", this field is required. For rule types "query" or "body", this field is optional.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is load-balancer-listener-policy-rule-delete 

Delete one or more policies from a load balancer listener.

ibmcloud is load-balancer-listener-policy-rule-delete LOAD_BALANCER LISTENER_ID POLICY (RULE_ID1 RULE_ID2 ...) [--vpc VPC] [--output JSON] [-f, --force] [-q, --quiet]



 Command options 



* LOAD_BALANCER: ID or name of the load balancer.
* LISTENER_ID: ID of the listener.
* POLICY: ID or name of the policy.
* LISTENER_ID: ID of the listener.
* POLICY: ID or name of the policy.
* RULE_ID: ID of the rule.
* --vpc: ID or name of the VPC. It is only required to specify the unique resource by name inside this VPC.
* --condition: The condition of the rule. One of: contains, equals, matches_regex.
* --type: The type of the rule. One of: header, hostname, path, query, body.
* --value: Value to match the rule condition.
* --field: The HTTP field. This field is applicable to "header", "query", and "body" rule types. For rule type "header", this field is required. For rule types "query" or "body", this field is optional.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is load-balancer-listener-policy-rules 

List all load balancer policy rules.

ibmcloud is load-balancer-listener-policy-rules LOAD_BALANCER LISTENER_ID POLICY [--vpc VPC] [--output JSON] [-q, --quiet]



 Command options 



* LOAD_BALANCER: ID or name of the load balancer.
* LISTENER_ID: ID of the listener.
* POLICY: ID or name of the policy.
* --vpc: ID or name of the VPC. It is only required to specify the unique resource by name inside this VPC.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is load-balancer-listener-policy-update 

Update a policy of a load balancer listener.
Debugging cluster add-ons 

Virtual Private Cloud

Classic infrastructure

As you use Red Hat® OpenShift® on IBM Cloud®, consider these techniques for troubleshooting [managed add-ons](https://cloud.ibm.com/docs/openshift?topic=openshift-managed-addons), such as HPCS Router.

You can check the health state and status of a cluster add-on by running the following command.

ibmcloud oc cluster addon ls -c <cluster_name_or_ID>

Example output

Name Version Health State Health Status
debug-tool 2.0.0 normal Addon Ready

The Health State reflects the lifecycle of the add-on components. Each state is described in the following table.



Add-on health states

 Add-on health state Description 

 critical The add-on is not ready to be used for one of the following reasons:<br><br><br><br> * Some or all the add-on components are unhealthy.<br> * The add-on failed to deploy.<br> * The add-on may be at an unsupported version.<br> * Check the Health Status field for more information.<br><br><br> 
 normal The add-on is successfully deployed. Check the status to verify that the add-on is Ready or to see if an update is available. 
 pending Some or all components of the add-on are currently deploying. Wait for the state to become normal before working with your add-on. 
 updating The add-on is updating and is not ready to be used. Check the Health Status field for the version that the add-on is updating to. 
 warning The add-on might not function properly due to cluster limitations. Check the Health Status field for more information. 



The Health Status provides details of what add-on operation is in progress. Each status is described in the following table.



Add-on health statuses

 Status code Add-on health status Description 

 H1500 Addon Ready The add-on is successfully deployed and is healthy.
Debugging cluster add-ons 

Virtual Private Cloud

Classic infrastructure

As you use IBM Cloud® Kubernetes Service, consider these techniques for troubleshooting [managed add-ons](https://cloud.ibm.com/docs/containers?topic=containers-managed-addons), such as Istio.

You can check the health state and status of a cluster add-on by running the following command.

ibmcloud ks cluster addon ls -c <cluster_name_or_ID>

Example output

Name Version Health State Health Status
debug-tool 2.0.0 normal Addon Ready
istio 1.4 - Enabling

The Health State reflects the lifecycle of the add-on components. Each state is described in the following table.



Add-on health states

 Add-on health state Description 

 critical The add-on is not ready to be used for one of the following reasons:<br><br><br><br> * Some or all the add-on components are unhealthy.<br> * The add-on failed to deploy.<br> * The add-on may be at an unsupported version.<br> * Check the Health Status field for more information.<br><br><br> 
 normal The add-on is successfully deployed. Check the status to verify that the add-on is Ready or to see if an update is available. 
 pending Some or all components of the add-on are currently deploying. Wait for the state to become normal before working with your add-on. 
 updating The add-on is updating and is not ready to be used. Check the Health Status field for the version that the add-on is updating to. 
 warning The add-on might not function properly due to cluster limitations. Check the Health Status field for more information. 



The Health Status provides details of what add-on operation is in progress. Each status is described in the following table.



Add-on health statuses

 Status code Add-on health status Description 

 H1500 Addon Ready The add-on is successfully deployed and is healthy.
: When used with the private_cert_configuration_action_sign_csr action, this field determines whether to use the common name (CN) from a certificate signing request (CSR) instead of the CN that is included in the data of the certificate.

Does not include any requested Subject Alternative Names (SANs) in the CSR. To use the alternative names, include the use_csr_sans property.

--use-csr-sans (bool)
: When used with the private_cert_configuration_action_sign_csr action, this field determines whether to use the Subject Alternative Names (SANs) from a certificate signing request (CSR) instead of the SANs that are included in the data of the certificate.

This field does not include the common name in the CSR. To use the common name, include the use_csr_common_name property.

--ou ([]string)
: The Organizational Unit (OU) values to define in the subject field of the resulting certificate.

The list items must match regular expression /(.?)/. The maximum length is 10 items. The minimum length is 0 items.

--organization ([]string)
: The Organization (O) values to define in the subject field of the resulting certificate.

The list items must match regular expression /(.?)/. The maximum length is 10 items. The minimum length is 0 items.

--country ([]string)
: The Country (C) values to define in the subject field of the resulting certificate.

The list items must match regular expression /(.?)/. The maximum length is 10 items. The minimum length is 0 items.

--locality ([]string)
: The Locality (L) values to define in the subject field of the resulting certificate.

The list items must match regular expression /(.?)/. The maximum length is 10 items. The minimum length is 0 items.

--province ([]string)
: The Province (ST) values to define in the subject field of the resulting certificate.

The list items must match regular expression /(.?
* containers-kubernetes.logging-autoupdate.changed
* containers-kubernetes.masterlog-retrieve
* containers-kubernetes.masterlog-status
* containers-kubnertes.cluster.rbac.update
* containers-kubernetes.service.create
* containers-kubernetes.service.delete
* containers-kubernetes.subnet.add
* containers-kubernetes.subnet.create
* containers-kubernetes.subnet.update
* containers-kubernetes.vlan.create
* containers-kubernetes.vlan.delete
* containers-kubernetes.worker.create
* containers-kubernetes.worker.delete
* containers-kubernetes.worker.update
* containers-kubernetes.workerpool.create
* containers-kubernetes.workerpool.delete
* containers-kubernetes.workerpool.update
* containers-kubernetes.zone.delete
* containers-kubernetes.zone.update



Deprecated fields across events
: The following fields are deprecated and replaced by or updated with new values across events.



* The correlationID is replaced by correlationId to align with field casing standards.
* The resourceGroupID field is no longer used. Instead, the resource group ID can be found in the target.resourceGroupId field.
* The reason.reasonCode field is now formatted as an integer (int) instead of string (string).
* The requestData field is now formatted as a JSON object instead of a JSON string.
* The responseData field is now formatted as a JSON object instead of string.
* The target.typeURI values are updated for consistency. All values now have a prefix of containers-kubernetes/ instead of container/. For example, container/cluster is now containers-kubernetes/cluster and container/worker is now containers-kubernetes/worker.







 16 March 2021 

Ingress ALB change log
You can check the health state and status of a cluster add-on by running the following command.

ibmcloud oc cluster addon ls -c <cluster_name_or_ID>

Example output

Name Version Health State Health Status
debug-tool 2.0.0 normal Addon Ready

The Health State reflects the lifecycle of the add-on components. Each state is described in the following table.



Add-on health states

 Add-on health state Description 

 critical The add-on is not ready to be used for one of the following reasons:<br><br><br><br> * Some or all the add-on components are unhealthy.<br> * The add-on failed to deploy.<br> * The add-on may be at an unsupported version.<br> * Check the Health Status field for more information.<br><br><br> 
 normal The add-on is successfully deployed. Check the status to verify that the add-on is Ready or to see if an update is available. 
 pending Some or all components of the add-on are currently deploying. Wait for the state to become normal before working with your add-on. 
 updating The add-on is updating and is not ready to be used. Check the Health Status field for the version that the add-on is updating to. 
 warning The add-on might not function properly due to cluster limitations. Check the Health Status field for more information. 



The Health Status provides details of what add-on operation is in progress. Each status is described in the following table.



Add-on health statuses

 Status code Add-on health status Description 

 H1500 Addon Ready The add-on is successfully deployed and is healthy. 
 H1501, H1502, H1503 Addon Not Ready Some or all the add-on components are unhealthy. Check whether all add-on component pods are running. Satellite clusters: Also see [Why doesn't my cluster add-on work?](https://cloud.ibm.com/docs/satellite?topic=satellite-addon-errors).