vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can choose to retain your events for 7, 14, or 30 days. In addition, a 30 day HIPAA compliant offering is also available. For more information about these offerings, see [Service plans](https://cloud.ibm.com/docs/atracker?topic=atracker-service_plan).

Use Activity Tracker hosted event search offerings to manage events using a UI or to manage auditing events that are not routed by Activity Tracker Event Routing.







 What are the different options to collect and monitor auditing events in my account? 

To collect and monitor activity in your account, you must configure the Activity Tracker Event Routing service in your account by using any of the following methods:



* You can [configure Activity Tracker Event Routing](https://cloud.ibm.com/docs/atracker?topic=atracker-getting-started-routing-2) to manage auditing events in your account while maintaining Financial Services Validated status.

The target resource must be an IBM Cloud® Object Storage bucket that is available in the same account where the auditing events are generated.

You can also use a bucket that is available in a different account from where auditing events are generated.

You must follow and comply with the Financial Services Validated requirements for buckets to maintain Financial Services Validated status.
* You can [configure the Activity Tracker Event Routing hosted event search offering](https://cloud.ibm.com/docs/atracker?topic=atracker-getting-started-search) to manage auditing events through the UI, or if you need PCI, SOC2, Privacy Shield or HIPAA compliance.
* You can configure Activity Tracker Event Routing to define the Activity Tracker Event Routing hosted event search instances where auditing events are routed.

The Activity Tracker Event Routing hosted event search instances can be located in the same account where auditing events are generated or in a different account.







 Where can I find the list of Cloud services that generate Activity Tracker Event Routing events?
HTTP Requests httpRequests1mGroupshttpRequests1hGroupshttpRequests1dGroupshttpRequestsAdaptiveGroups 
 Image Resizing Analytics imageResizingRequests1mGroups 
 Load Balancing Analytics loadBalancingRequestsloadBalancingRequestsGroups 
 SYN Attacks (DoS Analytics) synAvgPps1mGroups 
 Edge Functions Metrics workersInvocationsAdaptive 







 Errors 

The GraphQL Analytics API is a RESTful API based on HTTPS requests and JSON responses and returns familiar HTTP status codes (for example, 404, 500, 504). In conformity to the GraphQL specification, a 200 response can contain an error, which is in contrast to the common REST approach.

All responses contain an errors array, which is null if there are no errors. Non-null errors contain message, path, and timestamp.

The following code is an example error response:

{
"data": null,
"errors": [
{
"message": "cannot request data older than 2678400s",
"path":
"viewer",
"zones",
"0",
"firewallEventsAdaptiveGroups"
],
"extensions": {
"timestamp": "2019-12-09T21:27:19.195060142Z"
}
}
]
}





 Limits 

The limits for retaining historical data are defined in the following table.



Table 2. Historical data limits

 Data node Enterprise 

 browserInsightsAdaptiveGroups 30 days 
 firewallEventsAdaptiveByTimeGroups 30 days 
 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
response, e := client.GetObjectLockConfiguration(getObjectLockConfigurationInput)
if e != nil {
fmt.Println(e)
} else {
fmt.Println("Object Lock Configuration =>", response.ObjectLockConfiguration)
}
}

func objectLockRetention(bucketName string, client s3.S3, keyName string) {

// Put objectlock retenion on the object uploaded to the bucket.
retention_date := time.Now().Local().Add(time.Second * 5)
putObjectRetentionInput := &s3.PutObjectRetentionInput{
Bucket: aws.String(bucketName),
Key: aws.String(keyName),
Retention: &s3.ObjectLockRetention{
Mode: aws.String("COMPLIANCE"),
RetainUntilDate: aws.Time(retention_date),
},
}
_, e := client.PutObjectRetention(putObjectRetentionInput)

// Get objectlock retention of the above object.
getObjectRetentionInput := new(s3.GetObjectRetentionInput)
getObjectRetentionInput.Bucket = aws.String(bucketName)
getObjectRetentionInput.Key = aws.String(keyName)
response, e := client.GetObjectRetention(getObjectRetentionInput)
if e != nil {
fmt.Println(e)
} else {
fmt.Println("Object Lock Retention =>", response.Retention)
}
}

func objectLockLegalHold(bucketName string, client s3.S3, keyName string) {

// Setting the objectlock legalhold status to ON.
putObjectLegalHoldInput := &s3.PutObjectLegalHoldInput{
success: provision of file from on premises worked and was replaced with the following contents:
hi







 Remove resources 



1. Remove the resources created by Terraform:

cd $CHECKOUT_DIR/vpc-app-deploy/ansible/tf

and

terraform destroy



Depending on the resource it might not be deleted immediately, but retained (by default for 7 days). You can reclaim the resource by deleting it permanently or restore it within the retention period. See this document on how to [use resource reclamation](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation).







 Related content 



* [Public frontend and private backend in a Virtual Private Cloud](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-public-app-private-backend),
* [Deploy a LAMP stack using Terraform](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-lamp-stack-on-vpc)
* [Learn about repeatable and reliable end-to-end app provisioning and configuration](https://developer.ibm.com/articles/application-deployment-with-redhat-ansible-and-ibm-cloud-schematics/)
* [Discover best-practice VPC configuration for application deployment](https://developer.ibm.com/articles/secure-vpc-access-with-a-bastion-host-and-terraform/)
* Delete IBM Cloudant and bind to a microservice
* IBM Cloudant service



Depending on the resource it might not be deleted immediately, but retained (by default for 7 days). You can reclaim the resource by deleting it permanently or restore it within the retention period. See this document on how to [use resource reclamation](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation).





 Related content 



* [Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift)
* [IBM Cloudant](https://cloud.ibm.com/catalog/services/cloudant)
* [Analyze logs and monitor application health](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-application-log-analysisapplication-log-analysis)
* [Horizontal Pod Autoscaling](https://docs.openshift.com/container-platform/4.12/nodes/pods/nodes-pods-autoscaling.html)
return cos.putBucketProtectionConfiguration({
Bucket: bucketName,
ProtectionConfiguration: {
'Status': 'Retention',
'MinimumRetention': {'Days': 10},
'DefaultRetention': {'Days': 100},
'MaximumRetention': {'Days': 1000}
}
}).promise()
.then(() => {
console.log(Protection added to bucket ${bucketName}!);
})
.catch((e) => {
console.log(ERROR: ${e.code} - ${e.message}n);
});
}





 Check retention policy on a bucket 

This implementation of a GET operation fetches the retention parameters for an existing bucket.

Syntax

GET https://{endpoint}/{bucket-name}?protection= path style
GET https://{bucket-name}.{endpoint}?protection= virtual host style

Example request

GET /example-bucket?protection= HTTP/1.1
Authorization: {authorization-string}
x-amz-date: 20181011T190354Z
Content-Type: text/plain
Host: 67.228.254.193

Example response

HTTP/1.1 200 OK
Date: Wed, 5 Oct 2018 15:39:38 GMT
X-Clv-Request-Id: 7afca6d8-e209-4519-8f2c-1af3f1540b42
Accept-Ranges: bytes
Server: Cleversafe/3.13.1
X-Clv-S3-Version: 2.5
x-amz-request-id: 7afca6d8-e209-4519-8f2c-1af3f1540b42
Content-Length: 299
<ProtectionConfiguration>
<Status>Retention</Status>
<MinimumRetention>
<Days>100</Days>
Replace missing values as determined by the specified interpolator.

TS_INNER_ALIGN(TimeSeries, TimeSeries, InterpolatorType)
: Output: TimeSeries, TimeSeries
: Temporally inner align two time series of the same type. Unlike TS_INNER_JOIN, this function produces two output time series, each of which is aligned with the other.
: The output time series are of the same type as the input time series.

TS_LEFT_ALIGN(TimeSeries, TimeSeries, InterpolatorType)
: Output: TimeSeries, TimeSeries
: Temporally left align two time series of the same type, and set any missing values to null. Unlike TS_LEFT_JOIN, this function produces two output time series, each of which is aligned with the other. The output time series are of the same type as the input time series.

TS_RIGHT_ALIGN(TimeSeries, TimeSeries, InterpolatorType)
: Output: TimeSeries, TimeSeries
: Temporally right align two time series of the same type, and set any missing values to null. Unlike TS_RIGHT_JOIN, this function produces two output time series, each of which is aligned with the other. The output time series are of the same type as the input time series.

TS_FULL_ALIGN(TimeSeries, TimeSeries, InterpolatorType)
: Output: TimeSeries, TimeSeries
: Temporally full align two time series of the same type, and set any missing values to null. Unlike TS_FULL_JOIN, this function produces two output time series, each of which is aligned with the other. The output time series are of the same type as the input time series.

TS_VECTORN(TimeSeries, TimeSeries, ...)
: Output: ArrayTimeSeries
: Temporally inner join up to 10 time series of the same type to produce a single array time series of vectors. Only observations with matching timeticks are retained, so if all observations are to be retained, align the input time series before you use this function.





 Interpolation functions 

Use interpolation either to fill missing values or to resample a time series at a different periodicity.
The BGP hold-time is three times the interval at which keepalive messages are sent, and hold-time is the maximum number of seconds allowed to elapse between successive keepalive messages that BGP receives from a peer. BGP on the local routing device uses the smaller of either the local hold-time value or the peer’s hold-time value as hold-time for the BGP connection between the two peers.

Bidirectional Forwarding Detection (BFD) is not supported by Transit gateway's GRE tunnels.

In vSRX, the default hold-time is 90 seconds, which means that the default frequency for keepalive messages is 30 seconds. For more information, see [precision-timers](https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/ref/statement/precision-timers-edit-protocols-bgp.html) and [hold-time](https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/ref/statement/hold-time-edit-protocols-bgp.html).





 Related links 



* [VMware vSphere overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vs_vsphereclusteroverview)
* [Getting started with IBM Cloud Gateway Appliance](https://cloud.ibm.com/docs/gateway-appliance?topic=gateway-appliance-getting-started)
* [Getting started with IBM Cloud Transit Gateway](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-getting-started)
* [GRE Configuration Example](https://kb.juniper.net/InfoCenter/index?page=content&id=KB19371&cat=SRX_SERIES&actp=LIST)
TS_VECTORN(TimeSeries, TimeSeries, ...)
: Output: ArrayTimeSeries
: Temporally inner join up to 10 time series of the same type to produce a single array time series of vectors. Only observations with matching timeticks are retained, so if all observations are to be retained, align the input time series before you use this function.





 Interpolation functions 

Use interpolation either to fill missing values or to resample a time series at a different periodicity.

TS_RESAMPLE(DoubleTimeSeries, Long, InterpolatorType) or TS_RESAMPLE(StringTimeSeries, Long, InterpolatorType)
: Output: The output is of the same type as the input time series.
: Resample the specified time series by using the specified periodicity (second parameter). Depending on the periodicity:



* The output time series might contain new, generated observations that are not in the input time series. The [interpolator](https://cloud.ibm.com/docs/services/sql-query?topic=sql-query-artifactinterpolator_creation) (third parameter) determines how to set values for any generated observations.
* Some of the observations in the input time series might be absent from the output time series. However, even skipped observations are used during interpolation.







 String matching functions 

Match a string time series against a string sequence or a set of strings.

TS_MATCH(StringTimeSeries, MatcherType, Array[String])
: Output: StringTimeSeries
: If the specified pattern (third parameter) matches the values in the input time series (first parameter) as required by the specified matcher (second parameter), this function returns the matching observations; otherwise, it returns null.





 Time functions 

Convert a string or timestamp into a value of type Long.

TS_TIMESTAMP(String) or TS_TIMESTAMP(TimestampType)
: Output: Long
* Set the filter to kube.namespace.name, is, ibm-observe.

Zoom

![Configure Filter](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution55-openshift-microservices/explore-img-10.png)

Configure Filter
* Click Save.



The dashboard now shows information about the ibm-observe namespace.

Zoom

![Custom Network Traffic and Bandwidth](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution55-openshift-microservices/dashboard-img-5.png)

Custom Network Traffic and Bandwidth



Find more about IBM Cloud Monitoring in the [IBM Cloud documentation](https://cloud.ibm.com/docs/monitoring?topic=monitoring-getting-started).







 Step 11: Remove resources 

In the [Resource List](https://cloud.ibm.com/resources) locate and delete the resources you wish to remove:



* Delete the Red Hat OpenShift on IBM Cloud cluster
* To delete the Red Hat OpenShift resources without deleting the cluster, run the below commands:

oc delete all --all --namespace example-health
oc delete project/example-health
* Delete Log Analysis instance
* Delete IBM Cloud Monitoring
* Delete IBM Cloudant and bind to a microservice
* IBM Cloudant service



Depending on the resource it might not be deleted immediately, but retained (by default for 7 days). You can reclaim the resource by deleting it permanently or restore it within the retention period. See this document on how to [use resource reclamation](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation).
Number of snapshots to retain.

-m, --minute
: Minute of the hour when snapshots are taken, integer between [0-59].

-r, --hour
: Hour of the day when snapshots are taken, integer between [0-23].

-d, --day-of-week
: Day of the week when snapshots are taken, integer between [0-6]. 0 means Sunday,1 means Monday,2 means Tuesday,3 means Wednesday,4 means Thursday,5 means Friday,6 means Saturday.

Examples:

ibmcloud sl block snapshot-enable 12345678 -s WEEKLY -c 5 -m 0 --hour 2 -d 0

This command enables snapshot for a volume with ID 12345678. The snapshot is taken weekly on every Sunday at 2:00, and up to 5 snapshots are retained.





 ibmcloud sl block snapshot-delete 

Delete a snapshot on a specified volume:

ibmcloud sl block snapshot-delete SNAPSHOT_ID

Examples:

ibmcloud sl block snapshot-delete 12345678

This command deletes snapshot with ID 12345678.





 ibmcloud sl block snapshot-list 

List block storage snapshots:

ibmcloud sl block snapshot-list VOLUME_ID [OPTIONS]

Command options:

--sortby
: Column to sort by, options are: id,name,created,size_bytes.

Examples:

ibmcloud sl block snapshot-list 12345678 --sortby id

This command lists all snapshots of volume with ID 12345678 and sorts them by ID.





 ibmcloud sl block snapshot-order 

Order snapshot space for a block storage volume:

ibmcloud sl block snapshot-order VOLUME_ID [OPTIONS]

Command options:

-s, --size
: Required. Size of snapshot space to create in GB.

-t, --tier
: Optional.
(https://cloud.ibm.com/icons/checkmark-icon.svg) 
 On-demand refresh from parent volume ![Checkmark icon.](https://cloud.ibm.com/icons/checkmark-icon.svg)^[[1]](https://cloud.ibm.com/docs?tab=faqsfn1)^ ![Checkmark icon.](https://cloud.ibm.com/icons/checkmark-icon.svg)^[[2]](https://cloud.ibm.com/docs?tab=faqsfn2)^ 
 Separated from parent volume ![Checkmark icon.](https://cloud.ibm.com/icons/checkmark-icon.svg) 



* How long does it take to convert a dependent duplicate into an independent volume?

The conversion process can take some time to complete. The bigger the volume, the longer it takes to convert it. For a 12-TB volume, it might take 24 hours. You can check on the progress in the UI or from the CLI.



* In the UI, go to [Classic Infrastructure](https://cloud.ibm.com/gen1/infrastructure/devices). Click Storage > Block Storage for Classic, then locate the volume in the list. The conversion status is displayed on the Overview page.
* From the CLI, use the following command.

slcli block duplicate-convert-status <dependent-vol-id>

The output looks similar to the following example.

slcli block duplicate-convert-status 370597202
Username Active Conversion Start Timestamp Completed Percentage
SL02SEVC307608_74 2022-06-13 14:59:17 90



* Where can I find more information about Portable Storage?

Portable storage volumes (PSVs) are an auxiliary storage solution exclusively for Virtual Servers. You can detach PSV from one Virtual Server and attach it to another. You can connect a portable storage disk to one Virtual Server at a time while all information that is stored on the disk is retained for transfer between devices.
Securing your data in App ID
: You can now restore deleted instances of App ID during the data retention period. [Learn more](https://cloud.ibm.com/docs/appid?topic=appid-mng-data).





 27 January 2020 

Cloud Directory: Connect your own email provider
: You can now bring your own custom email provider or connect your SendGrid account to have more control over your email communication with your users. For more information, see the [configuring email settings docs](https://cloud.ibm.com/docs/appid?topic=appid-cd-typescd-email-settings).

Import and export user roles
: You can now include any roles that are assigned to a user as part of using the export and import APIs. For more information, see the [migrating profiles](https://cloud.ibm.com/docs/appid?topic=appid-user-adminmigrating-profiles) or [managing Cloud Directory users](https://cloud.ibm.com/docs/appid?topic=appid-cd-usersuser-migration) documentation.

Post-MFA extensions
: You can now create post-MFA extensions to help you to monitor and improve your users MFA experiences. For more information, see the [extending MFA docs](https://cloud.ibm.com/docs/appid?topic=appid-cd-mfacd-mfa-extensions).

Pre-MFA extensions
: You can now create pre-MFA extensions that allow you to make custom decisions at runtime about which users must complete your MFA flow. For more information, see the [extending MFA docs](https://cloud.ibm.com/docs/appid?topic=appid-cd-mfacd-mfa-extensions).





 15 December 2019 

Access control
: You can now define which users are able to access your app data, use specific features, or perform specific actions in your apps by using role-based access control.
IBM Cloud service level objectives 

Service level objectives (SLOs) describe the design points that the IBM Cloud® services are engineered to meet in the following areas:



* Availability
* Operations management
* Performance



The SLO is not a warranty and IBM will not issue credits for failure to meet an objective. Refer to the [Service Level Agreements (SLAs)](https://cloud.ibm.com/docs/overview?topic=overview-slas) for commitments and credits that are issued for failure to meet any committed SLAs.

The following tables describe the service level objectives (SLOs) for the IBM Cloud services in a high availability configuration. As you aggregate or deploy services into a single zone, your SLO might vary. For more information about how IBM Cloud is striving to ensure the highest availability of services, see [How IBM Cloud ensures high availability and disaster recovery](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtime).



 Service level objectives for IBM Cloud platform services and other vital services 

These services include our control plane and self-service interfaces, IAM service, key management service, virtual machine compute instances, block and object storage services, virtual networks service, web or Layer 7 load-balancing service, and relational DBaaS.



 Platform services 

The following table describes the service level objectives (SLOs) for the vital IBM Cloud platform services in a high availability configuration.



Table 1. Service level objectives (SLOs) for the IBM Cloud platform services

 Platform service Availability target High availability guidance 

 IBM Cloud console 99.999% [High availability for the platform](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimeplatform-ha) 
 IBM Cloud CLI 99.999% [Understanding high availability and disaster recovery for the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-ha-dr) 
 IBM Cloud network 99.9999% [High availability for the network](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimeha-network)
* [Scaling instances depending on load](https://ibm.ent.box.com/notes/302764242833?s=8fybw54tw7i6oq7luqugj6i1m8bbzp4l)







 Related links 

See [how IBM Cloud ensures high availability and disaster recovery](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimezero-downtime). You can also find more information about [Service Level Agreements](https://cloud.ibm.com/docs/overview?topic=overview-slas).
Understanding high availability and disaster recovery 

All IBM Cloud® general availability (GA) services have a Service Level Agreement of 99.99% availability. IBM Cloud VPC is offered in Dallas, Toronto, Frankfurt, London, Madrid, Tokyo, Osaka, Sydney, Washington DC, and São Paulo. Each location has three different data centers for redundancy.

See [ensure zero downtime](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimezero-downtime) to learn more about the high availability and disaster recovery standards in IBM Cloud. For more information about high availability and disaster recovery for IBM Cloud VPC, see [Your responsibilities by using Virtual Private Cloud](https://cloud.ibm.com/docs/vpc?topic=vpc-responsibilities-vpc). You can also find information about [Service Level Agreements](https://cloud.ibm.com/docs/overview?topic=overview-slas).

For examples of deploying a highly available web application, see [Building a highly available 3-tier web application in VPC](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-ha-3-tier).

For more information about how you can use Veeam software to back up your storage data on a virtual server instance, see [About Veeam](https://cloud.ibm.com/docs/vpc?topic=vpc-about-veeam).

Placement Groups supports anti-affinity placement strategies for workload high availability. For more information, see [About placement groups](https://cloud.ibm.com/docs/vpc?topic=vpc-about-placement-groups-for-vpc).



  IBM Cloud Load Balancer for VPC and VPN for VPC Backups 

IBM Cloud Load Balancer for VPC and VPN for VPC have off-site storage and replication of configuration data in an out-of-region disaster recovery node with daily backups. The disaster recovery location and backups are located within the regulatory boundary.