vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Check out [Change management](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-servicesatis-change-management) for more information.
* Updating [worker nodes](https://cloud.ibm.com/docs/satellite?topic=satellite-hostshost-update-workers) in your Satellite location.



Key Protect on Satellite responsibilities:



* Running Key Protect maintenance and updates in your Satellite location.
* Ensuring the security of key operations and key-related processes.
* Sending audit logs through [IBM Cloud Activity Tracker](https://cloud.ibm.com/docs/key-protect?topic=key-protect-satellite-aboutsatellite-about-before-begin-activity).
* Support for issues related to the proper working of Key Protect.



It is recommended to coordinate with the Key Protect support team when maintaining your HSM, rotating keys, or performing other kinds of infrastructure maintenance.





 Using IBM Cloud Activity Tracker with Key Protect 

All activity in Key Protect is audited using IBM Cloud Activity Tracker. To get auditing logs through IBM Cloud Activity Tracker, you must first create an IBM Cloud Activity Tracker instance in IBM Cloud and then pass an ingestion key during [the deployment of Key Protect](https://cloud.ibm.com/docs/key-protect?topic=key-protect-satellite-ui-deploy). This ingestion key allows Key Protect logs to be sent to your IBM Cloud Activity Tracker instance, where you can view them. For more information on IBM Cloud Activity Tracker events, check out [Key Protect events](https://cloud.ibm.com/docs/key-protect?topic=key-protect-at-events).

For more information on creating an ingestion key, check out the [IBM Logging API reference doc](https://cloud.ibm.com/apidocs/log-analysisingest).

In Key Protect on Satellite, the target.ResourceGroupID value is always blank and the target.name is only visible if the resource targeted is a single Key Protect key.
To make consumer liveness easier to handle, background heartbeating was added in Kafka 0.10.1. The group coordinator expects group members to send it regular heartbeats to indicate that they remain active. A background heartbeat thread runs in the consumer and sends regular heartbeats to the coordinator. If the coordinator does not receive a heartbeat from a group member within the session timeout, the coordinator removes the member from the group and starts a rebalance of the group. The session timeout can be much shorter than the maximum polling interval, so that the time it takes to detect a failed consumer can be short, even if message processing takes a long time.

You can configure the maximum polling interval by using the max.poll.interval.ms property and the session timeout by using the session.timeout.ms property. You don't need to use these settings unless it takes more than 5 minutes to process a batch of messages.





 Managing offsets 

For each consumer group, Kafka maintains the committed offset for each partition that is consumed. When a consumer processes a message, it doesn't remove it from the partition. Instead, it just updates its current offset by using a process that is called committing the offset.

Event Streams retains committed offset information for 7 days.



 What if no existing committed offset exists? 

When a consumer starts and is assigned a partition to consume, it starts at its group's committed offset. If no existing committed offset exists, the consumer can choose whether to start with the earliest, or latest available message based on the setting of the auto.offset.reset property as follows:



* latest (the default): Your consumer receives and consumes only messages that arrive after you subscribe. Your consumer has no knowledge of messages that were sent before it subscribed, therefore don't expect that all messages are consumed from a topic.
* earliest: Your consumer consumes all messages from the beginning because it is aware of all messages that were sent.



If a consumer fails after processing a message but before committing its offset, the committed offset information does not reflect the processing of the message. This means that the message is processed again by the next consumer in that group to be assigned the partition.
url: "http://localhost:9115/probe?module=icmp&target=10.240.0.5"
tags:
service: windows_uptime
windows_hostname: windows-test-01

When you enable this option, you can segment data by windows_hostname and build alerts upon this metric.
5. Restart the monitoring agent. Run the following command:

service dragent restart







 Step 6: Next steps 



* Create a custom dashboard. For more information, see [Working with dashboards](https://cloud.ibm.com/docs/monitoring?topic=monitoring-dashboardsdashboards).
* Learn about alerts. For more information, see [Working with alerts](https://cloud.ibm.com/docs/monitoring?topic=monitoring-monitoringmonitoring_alerts).
* Learn how to manage logs. See [Logging with Windows VPC server instances](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-windows_vpc_tutorial).
For example, change https://us-east.monitoring.cloud.ibm.com//alerts/rules?direction=asc&sortBy=name to https://us-east.monitoring.cloud.ibm.com//alerts/legacy-editor/new





 14 April 2023 

IBM Cloud® Monitoring Secure is now IBM Cloud® Monitoring Workload Protection
: The UI now displays IBM Cloud® Monitoring Secure functions under the new name Workload Protection.



* The Secure icon has changed and now includes the text Workload Protection.
* [To access the Secure UI, select Workload Protection instead of Secure.](https://cloud.ibm.com/docs/monitoring?topic=monitoring-launchlaunch_step3)
* All instructions in the [IBM Cloud® Monitoring documentation](https://cloud.ibm.com/docs/monitoring) referring to Secure apply to Workload Protection.







 07 October 2022 

IBM Cloud® Monitoring has improved Explorer support for customers with only platform metrics.
: For customers monitoring only platform metrics, the Explorer view will now show the metrics organized by metric namespace. The ability to query metrics using PromQL is also supported.





 05 August 2022 

IBM Cloud® Monitoring has released support for trusted profiles.
: For more information, see [Trusted Profiles](https://cloud.ibm.com/docs/monitoring?topic=monitoring-trusted_profiles).





 06 July 2022 

IBM Cloud® Monitoring has released a new Alert Editor interface.
: The following changes have been made:



* New user interface to manage alerts.

You can still manage alerts by using the legacy editor. However, notice that new features are only available through the new editor.
* New configuration settings to help you troubleshoot issues. You can configure a dashboard and a runbook with an alert.



Deprecated features:



* Deprecation of the Anomaly Detection and Group Outlier alert types. You can view and manage existing alerts but you cannot define new ones.
Auditing events 

Security officers, auditors, or managers can use the IBM Cloud Activity Tracker service to track how users and applications interact with the App Configuration service in IBM Cloud.

IBM Cloud Activity Tracker records user-initiated activities that change the state of a service in IBM Cloud. You can use this service to investigate abnormal activity and critical actions and to comply with regulatory audit requirements. In addition, you can be alerted about actions as they happen. The events that are collected comply with the Cloud Auditing Data Federation (CADF) standard. For more information, see the [getting started tutorial for IBM Cloud Activity Tracker](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-getting-started).



 List of events 

The following list of App Configuration events is sent to IBM Cloud Activity Tracker.



Table 1. Overview of App Configuration actions that generate IBM Cloud Activity Tracker events

 Action Description 

 apprapp.segments.create Created a segment or failed to create 
 apprapp.segments.update Updated a segment or failed to update 
 apprapp.segments.delete Deleted a segment or failed to delete 
 apprapp.segments.list Called the list of segments or failed to list 
 apprapp.segments.read Retrieved segment details or failed to retrieve 
 apprapp.environments.create Created an environment or failed to create 
 apprapp.environments.update Updated an environment or failed to update 
 apprapp.environments.delete Deleted an environment or failed to delete 
 apprapp.environments.list Called the list of environments or failed to list 
 apprapp.environments.read Retrieved environment details or failed to retrieve environment details 
 apprapp.features.create Created feature or failed to create 
 apprapp.features.update Updated feature or failed to update 
 apprapp.features.updatevalues Updated feature details or failed to update details 
 apprapp.features.delete Deleted feature or failed to delete 
 apprapp.features.list Called the list of features or failed to list 
 apprapp.features.read Retrieved feature details or failed to retrieve the details 
 apprapp.features.evaluate Evaluated feature at the SDK or failed to evaluate
It then asynchronously processes the contents of the grammar and automatically extracts new words that the grammar can recognize. You cannot submit requests to add more data resources to a custom model, or to train the model, until the service's analysis of the grammar for the current request completes.

To determine the status of the analysis, use the GET /v1/customizations/{customization_id}/grammars/{grammar_name} method to poll the status of the grammar. The method accepts the ID of the custom model and the name of the grammar. The following example checks the status of the grammar named confirm-abnf.

IBM Cloud

curl -X GET -u "apikey:{apikey}" "{url}/v1/customizations/{customization_id}/grammars/confirm-abnf"

IBM Cloud Pak for Data

curl -X GET --header "Authorization: Bearer {token}" "{url}/v1/customizations/{customization_id}/grammars/confirm-abnf"

The response includes the status of the grammar:

{
"name": "confirm-abnf",
"out_of_vocabulary_words": 0,
"status": "being_processed"
}

The status field has one of the following values:



* analyzed indicates that the service has successfully analyzed the grammar.
* being_processed indicates that the service is still analyzing the grammar.
* undetermined indicates that the service encountered an error while processing the grammar.



Use a loop to check the status of the grammar every 10 seconds until it becomes analyzed. For more information about checking the status of a grammar, see [Listing grammars for a custom language model](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-manageGrammarslistGrammars).





 Handling add grammar failures 

If its analysis of a grammar fails, the service sets the grammar's status to undetermined and includes an error field that describes the failure with the grammar's status.
* [Security Bulletin: IBM Watson Speech Services Cartridge for IBM Cloud Pak for Data is vulnerable to denial of service and arbitrary code execution due to Apache Log4j (CVE-2021-45105 and CVE-2021-45046)](https://www.ibm.com/support/pages/node/6551168)







 20 December 2021 (Version 4.0.4) 

Version 4.0.4 is now available
: Text to Speech for IBM Cloud Pak for Data version 4.0.4 is now available. This version supports IBM Cloud Pak for Data version 4.x and Red Hat OpenShift versions 4.6 and 4.8. For more information about installing and managing the service, see [Installing Watson Text to Speech](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=speech-installing-watson-text).

Important: Changes to properties for disabling the storage and logging of user data
: Important: The names of the properties of the Speech services custom resource that specify whether user data is stored and logged have changed. The custom resource formerly contained the following properties:


 Anonymize logs

sttRuntime:
anonymizeLogs: "false" If true, disables storage and logging of user data
sttAMPatcher:
anonymizeLogs: "false" If true, disables storage and logging of user data
ttsRuntime:
anonymizeLogs: "false" If true, disables storage and logging of user data

These properties are now named as follows:


 Storage and logging of user data

sttRuntime:
skipAudioAndResultLogging: "false" If true, disables storage and logging of user data
sttAMPatcher:
skipAudioAndResultLogging: "false" If true, disables storage and logging of user data
ttsRuntime:
skipAudioAndResultLogging: "false" If true, disables storage and logging of user data
streaming_statistics Object Information and statistics related to the Speech to Text recognition. See [assistant_interaction_summaries.turns].request.streaming_statistics](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-cdr-log-referencecdr-log-reference-request-streaming_statistics). 





 assistant_interaction_summaries.turns[].request.streaming_statistics 

The assistant_interaction_summaries.turns[].request.streaming_statistics object contains the following properties:



Properties of the assistant_interaction_summaries.turns[].streaming_statistics object

 Property Type Description 

 transaction_id String A unique identifier of the transaction. 
 start_timestamp String The time when the transaction started, in ISO format (yyyy-MM-ddTHH:mm:ss.SSSZ). 
 stop_timestamp String The time when the transaction ended, in ISO format (yyyy-MM-ddTHH:mm:ss.SSSZ). 
 response_milliseconds Number The latency (in milliseconds) between when silence is detected in the caller's speech and a final result from the assistant is received. 
 echo_detected Boolean Whether an echo was detected. 
 confidence Number The confidence score of the final utterance. 









 assistant_interaction_summaries.turns[].response 

The assistant_interaction_summaries.turns[].response object contains the following properties:



Properties of the assistant_interaction_summaries.turns[].response object

 Property Type Description
The app processes might begin before the entire app is completely ready, which can affect responses especially when scaling up across many instances. With health checks, you can let your system can know whether your app is running and ready to receive requests. By setting these probes, you can also help prevent downtime when you perform a [rolling update](https://cloud.ibm.com/docs/containers?topic=containers-update_appapp_rolling) of your app. You can set two types of health checks: liveness and readiness probes.

Liveness probe
: Set up a liveness probe to check whether the container is running. If the probe fails, the container is restarted. If the container does not specify a liveness probe, the probe succeeds because it assumes that the container is alive when the container is in a Running status.

Readiness probe
: Set up a readiness probe to check whether the container is ready to receive requests and external traffic. If the probe fails, the pod's IP address is removed as a usable IP address for services that match the pod, but the container is not restarted. Setting a readiness probe with an initial delay is especially important if your app takes a while to start. Before the initial delay, the probe does not start, giving your container time to come up. If the container does not provide a readiness probe, the probe succeeds because it assumes that the container is alive when the container is in a Running status.

You can set up the probes as commands, HTTP requests, or TCP sockets. The example uses HTTP requests. Give the liveness probe more time than the readiness probe. For more information, see the [Kubernetes documentation](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/).

livenessProbe:
httpGet:
path: /
port: 9080
initialDelaySeconds: 300
periodSeconds: 15
readinessProbe:
httpGet:
path: /
port: 9080
initialDelaySeconds: 45
periodSeconds: 5





 Pod Disruption Budget
The list of voices is automatically filtered to use the same language as your assistant. To see all voices, toggle the Filter voices based on assistant language switch to Off.

For more information about voice options, and to listen to audio samples, see [Languages and voices](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-voices) in the Text to Speech documentation.

Click Next.



Any speech service charges that are incurred by the phone integration are billed with the Watson Assistant service plan as voice add-on charges. After the instances are created, you can access them directly from the IBM Cloud dashboard. Any use of the speech instances that occurs outside of your assistant are charged separately as speech service usage costs.

The phone integration setup is now complete. On the Phone page, you can click the tabs to view or edit the phone integration.

If you chose to generate a free telephone number, your new number is displayed on the Phone number tab immediately. However, provisioning the new number so it is ready to use might take several minutes.





 Adding more phone numbers 

If you are using existing phone numbers you configured using a SIP trunk provider, you can add multiple numbers to the same phone integration.

If you generated a free phone number, you cannot add more numbers.

To add more phone numbers:



1. In the phone integration settings, go to the Phone number tab.
2. Use one of the following methods to add phone numbers:



* To add phone numbers one by one, type each number in the table, along with an optional description. Click the checkmark icon ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/phone-checkmark-save.png) to save each number.
* To import a set of phone numbers that are stored in a comma-separated values (CSV) file, click the Upload a CSV file icon (!
When your customer makes a phone call using the telephone number connected to your assistant, the phone integration answers. The integration converts output from your assistant into voice audio by using the IBM Watson® Text to Speech service. The audio is sent to the telephone network through the SIP trunk. When the customer replies, the voice input is converted into text by using the IBM Watson® Speech to Text service.

This feature is available only to Plus or Enterprise plan users. Note that Speech to Text and Text to Speech charges are included in the cost of a [monthly active user](https://cloud.ibm.com/docs/assistant?topic=assistant-admin-managing-planadmin-managing-plan-user-based) (MAU).

Depending on the architecture of your existing telephony infrastructure, there are multiple ways you might integrate it with Watson Assistant. For more information about common integration patterns, read the blog post [Hey Watson, can I have your number?](https://medium.com/ibm-watson/hey-watson-can-i-have-your-number-7de8fc7621ed) on Medium.



 Set up the integration 

You must have Manager role access to the instance and Viewer role access to the resource group. For more information about access levels, see [Managing access to resources](https://cloud.ibm.com/docs/assistant?topic=assistant-access-control).

To set up the integration, complete the following steps:



1. In the Integrations section on the main page for your assistant, click Add integration.
2. On the Add integration page, click Phone.
3. Click Create.
4. Choose whether you want to generate a free phone number for your assistant or connect to an existing SIP trunk:



* To generate a free phone number for your assistant, click Generate a free phone number.

Generating a free phone number is supported only for Watson Assistant instances in the Dallas and Washington DC data centers.
Handling phone interactions 

If your assistant uses the phone integration, you can use various response types to customize the behavior of the integration or manage the flow of conversations that your assistant has with customers over the telephone.

You can use response types to perform the following phone-specific actions:



* [Apply advanced settings to the Speech to Text service](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-phone-actionsphone-actions-speech-advanced)
* [Apply advanced settings to the Text to Speech service](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-phone-actionsphone-actions-text-advanced)
* [Transfer a call to a live agent](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-phone-actionsphone-actions-transfer)
* [Play hold music or a voice recording](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-phone-actionsphone-actions-hold-music)
* [Enable keypad entry](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-phone-actionsphone-actions-dtmf)
* [Transfer the conversation to the web chat integration](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-phone-actionsphone-actions-transfer-channel)
* [End the call](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-phone-actionsphone-actions-hangup)
* [Send a text message during a phone conversation](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-phone-actionsphone-actions-sms)



In some cases, you might want to combine response types to perform multiple actions. For example, you might want to implement two-factor authentication by requesting phone keypad entry and sending a text message from the same action step. For more information, see the following:
Escalation If your assistant is integrated with one of the supported service desk systems, you can build in logic that transfers, or escalates, the conversation to a human when necessary. [Learn more](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-human-agent). 
 Incompletion Reasons why an action is not completed by a user, including escalated to agent, started a new action, stuck on a step, or abandoned or ongoing. [Learn more](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-analytics-action-completionreasons-for-incompletion) 
 Integrations Add-ons to the end experience that help solve specific user problems, for example, connecting to a human agent or searching existing help content. Integrations are not required for an assistant, but they are recommended. [Learn more](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-deploy-assistant). 
 Message A single turn within a conversation that includes a single call to the /message API endpoint and its corresponding response. 
 Monthly active user (MAU) A single unique user who interacts with an assistant one or many times in a given month. [Learn more](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-admin-managing-planadmin-managing-plan-user-based). 
 Preview Embeds your assistant in a chat window that is displayed on an IBM-branded web page. From the preview, you can test how a conversation flows through your assistant, from end to end. [Learn more](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-preview-share). 
 Recognition Measurement of how many requests are being recognized by the assistant and routed into starting an action. [Learn more](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-analytics-overviewrecognition). 
 Response To create your assistant's response in an action step, you use the Assistant says section.