vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 







 Classic services 

Americas

Asia Pacific

Europe



Table 3. Compute infrastructure services integration in Americas locations

 Service Dallas (us-south) Washington (us-east) Toronto (ca-tor) Sao Paulo (br-sao) 

 IBM Cloud® Virtual Servers ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 
 IBM Cloud® Bare Metal Servers ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 







 Compute serverless services 

Americas

Asia Pacific

Europe



Table 4. Compute serverless services integration in Americas locations

 Service Dallas (us-south) Washington (us-east) Toronto (ca-tor) Sao Paulo (br-sao) 

 Cloud Functions !
: See [Memory usage with Node.js runtime actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-testmemory_usage)





 14 October 2019 

New Functions CLI version 1.0.35.
: See [CLI version history](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-cli_versions).

Added console tasks to actions.
: See [Create actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actions).







 September 2019 



 24 September 2019 

New Functions CLI version 1.0.34.
: See [CLI version history](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-cli_versions).





 20 September 2019 

Extend your IBM Cloud Functions app with an IBM Cloud Object Storage instance.
: See [IBM Cloud Object Storage](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstorage).





 11 September 2019 

New Functions CLI version 1.0.33.
: See [CLI version history](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-cli_versions).
1.0.35 13 October 2019 <br><br> * Fixed a bug with the ibmcloud fn property get --apihost command that caused changes to the IBM Cloud API endpoint.<br> * Removed support from the ibmcloud fn property set --namespace <NAMESPACE> command for targeting Cloud Foundry-based namespaces. This command now targets only IAM-based namespaces.<br> * Improved the writing to the configuration file for the ibmcloud fn deploy command.<br><br><br> 
 1.0.34 24 September 2019 Fixed a bug with the ibmcloud fn property get command that displayed incorrect authentication key and default namespace after you switch API hosts or regions. 
 1.0.33 11 September 2019 <br><br> * Fixed a bug where the incorrect Cloud Functions API host is retained after you switch API hosts or regions.<br> * Fixed a bug with the ibmcloud fn namespace delete command that reported a success message when deletion failed.<br> * Updated the ibmcloud fn api command to support create, delete, get, and list for IAM-based namespaces.<br> * Updated the ibmcloud fn namespace get --properties command to display CRNs and Service IDs.<br><br><br> 
 1.0.30 03 April 2019 <br><br> * Improved the service bind command handling of IAM and org and space-based services.<br> * Added a fix for handling API endpoint https://cloud.ibm.com.<br><br><br> 
 1.0.29 06 February 2019 Added commands deploy and undeploy to deploy or undeploy a collection of Functions entities via a manifest file. For more information, see the [Deployment](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-deploydeploy) documentation. 
 1.0.28 21 January 2019 Added an error message when update, delete, get namespace name exists multiple times.
* [Managing the security of the Hello World application and gaining situational awareness](https://cloud.ibm.com/docs/codeengine?topic=codeengine-getting-started-with-guardguard-situational-awareness)
* [Clean up the tutorial applications](https://cloud.ibm.com/docs/codeengine?topic=codeengine-getting-started-with-guardguard-cleanup)







 Pricing for Code Engine 

[Pricing for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-pricingpricing)



* [Application pricing](https://cloud.ibm.com/docs/codeengine?topic=codeengine-pricingapp-pricing)
* [Job pricing](https://cloud.ibm.com/docs/codeengine?topic=codeengine-pricingjob-pricing)
* [Build pricing](https://cloud.ibm.com/docs/codeengine?topic=codeengine-pricingbuild-pricing)







 Code Engine notices 

[Code Engine notices](https://cloud.ibm.com/docs/codeengine?topic=codeengine-noticesnotices)



* [CREATIVE COMMONS ATTRIBUTION 2.0 GENERIC](https://cloud.ibm.com/docs/codeengine?topic=codeengine-noticescca2gen)
* [CREATIVE COMMONS ATTRIBUTION 2.5 GENERIC](https://cloud.ibm.com/docs/codeengine?topic=codeengine-noticescca25gen)
* [CREATIVE COMMONS ATTRIBUTION 3.0 GENERIC](https://cloud.ibm.com/docs/codeengine?topic=codeengine-noticescca3gen)
* [CREATIVE COMMONS ATTRIBUTION 4.0 GENERIC](https://cloud.ibm.com/docs/codeengine?topic=codeengine-noticescca4gen)







 Using Kubernetes with Code Engine
Event sources 

An event source is a service or application on IBM Cloud that emits event notifications and publishes them to a topic within the Event Notifications service. A source is a registered entity in an Event Notifications service instance. A source can be registered to an Event Notifications service instance either as an IBM Cloud source or an API source or an IBM Cloud platform source.

A source can publish to multiple topics. In other contexts sources are identified as producers or publishers.

From a billing perspective, ingested notifications are calculated for all incoming events. If a user has disabled a source or if the source is not connected to a topic, the user is not billed for the events from the IBM Cloud source. However, if the source is Enabled, and a topic is connected to it, the ingested events include all incoming events (not only the events that are filtered in the topic).



 IBM Cloud sources 

The list of IBM provided sources is as follows:



* [IBM Cloud Monitoring](https://cloud.ibm.com/docs/monitoring?topic=monitoring-tutorial-en)
* [Security and Compliance](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-event-notifications&interface=ui)
* [Secrets Manager](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-event-notifications&interface=ui)
* [App Configuration](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-getting-started)
* [IBM Cloud Projects](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-event-notifications-events&interface=ui)
* [Toolchain](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-event-notifications-cd&interface=ui)







 API sources 

You can send custom events from your backend application to the Event Notifications service by using API sources. To do this, you need to add an API source first.
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring//images/checkmark-icon.svg) 
 Agent for orchestrated environments $36 ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring//images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring//images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring//images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring//images/checkmark-icon.svg) 



For hosts running an agent for non-orchestrated environments or for hosts running an agent for orchestrated environments that exceed the base tier allotment for Prometheus, JMX, appchecks, and Statsd metrics, additional prices apply:



* Time series are priced according to the following tiers:



* Tier 1: The price per time-series is 0.08 USD for up to 100K time-series per month.
* Tier 2: The price per time-series is 0.05 USD for 100K to 1M time-series per month.
: See [Runtimes](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-runtimes).

Updated the Composer topic.
: See [Composer](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_composer).

Added information about adding an IBM Cloud Functions Channel to IBM Cloud Monitoring.
: See [IBM Cloud Monitoring](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-alerts-notify).

Added information for versioning your actions.
: See [Versioning your actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actionsactions-version).





 12 March 2021 

Added support for au-syd (Sydney) region.
: See [Regions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-cloudfunctions_regions).







 January 2021 



 29 January 2021 

Added a sitemap.
: See [Sitemap for Cloud Functions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-sitemap).

Updated information about packaging Go source files.
: See [Packaging multiple Go source files](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_go_multi_packages).







 December 2020 



 14 December 2020 

Added versions to Quick start template docs.
: See [Deploying quick start templates](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-templates).

Updated securing web actions to include information about X-Require-Whisk-Auth.
: See [Securing web actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actions_webactions_web_secure).
Because each response includes multiple final results, one per utterance, you must assemble the final results into a single string to see the full transcript.



 Example 1: Interim results and low latency are both false 

This example sets both interim_results and low_latency to false. The service returns only final results as a single JSON object.

var message = {
action: 'start',
content-type: 'audio/wav',
inactivity_timeout: -1,
interim_results: false,
low_latency: false
};

{
"result_index": 0,
"results": [
{
"final": true,
"alternatives":
{
"transcript": "thunderstorms could produce ",
"confidence": 0.94
}
]
},
{
"final": true,
"alternatives":
{
"transcript": "large hail ",
"confidence": 0.91
}
]
},
{
"final": true,
"alternatives":
{
"transcript": "and heavy rain ",
"confidence": 0.86
}
]
}
]
}
Show more





 Example 2: Interim results is false and low latency is true 

This example sets interim_results to false and low_latency to true. The service returns only final results as a single JSON object.

var message = {
action: 'start',
content-type: 'audio/wav',
inactivity_timeout: -1,
interim_results: false,
low_latency: true
};

{
"result_index": 0,
"results": [
{
"final": true,
"alternatives":
{
"transcript": "thunderstorms could produce ",
"confidence": 0.94
}
]
},
{
"final": true,
interim_results: false,
low_latency: true
};

{
"result_index": 0,
"results": [
{
"final": true,
"alternatives":
{
"transcript": "thunderstorms could produce ",
"confidence": 0.94
}
]
},
{
"final": true,
"alternatives":
{
"transcript": "large hail ",
"confidence": 0.91
}
]
},
{
"final": true,
"alternatives":
{
"transcript": "and heavy rain ",
"confidence": 0.86
}
]
}
]
}
Show more





 Example 3: Interim results is true and low latency is false 

This example sets interim_results to true and low_latency to false. The service returns only final results, but it returns each result as a separate JSON object.

var message = {
action: 'start',
content-type: 'audio/wav',
inactivity_timeout: -1,
interim_results: true,
low_latency: false
};

{
"result_index": 0,
"results": [
{
"final": true,
"alternatives":
{
"transcript": "thunderstorms could produce ",
"confidence": 0.94
}
]
}
]
}{
"result_index": 1,
"results": [
{
"final": true,
"alternatives":
{
"transcript": "large hail ",
"confidence": 0.91
}
]
}
]
}{
"result_index": 2,
"results": [
{
"final": true,
"alternatives":
{
The values are in [UNIX time format](http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.htmltag_04_15). 
 namespace and name The namespace and name of the entity. 
 logs An array of strings with the logs that are produced by the action during its activation. Each array element corresponds to a line output to stdout or stderr by the action, and includes the time and stream of the log output. The structure is as follows: TIMESTAMP STREAM: LOG_OUTPUT. 
 response A dictionary that defines the keys success, status, and result.<br><br><br><br> * status: The activation result, which might be one of the following values: success, application error, action developer error, or whisk internal error.<br> * success: true if and only if the status is success.<br><br><br> 
 result A dictionary that contains the activation result. If the activation was successful, the result contains the value that is returned by the action. If the activation was unsuccessful, result contains the error key, generally with an explanation of the failure.
Sending the data immediately reduces latency because the audio is available to the service as soon as it is ready to handle a recognition request.



* The client sends:

{
"action": "start",
"content-type": "audio/l16;rate=22050"
}
<binary audio data>
{
"action": "stop"
}
* The service responds:

{"state": "listening"}
{"results": [{"alternatives": {"transcript": "name the mayflower ",
"confidence": 0.91}], "final": true}], "result_index": 0}
{"state":"listening"}







 Second example exchange 

In the second exchange, the client sends audio that contains the string Second audio transcript. The client sends the audio in a single binary message and uses the same parameters that it specified in the first request.



* The client sends:

<binary audio data>
{
"action": "stop"
}
* The service responds:

{"results": [{"alternatives": {"transcript": "second audio transcript ",
"confidence": 0.99}], "final": true}], "result_index": 0}
{"state":"listening"}







 Third example exchange 

In the third exchange, the client again sends audio that contains the string Name the Mayflower. It sends a binary message with a single chunk of PCM audio data. But this time, the client sends a new start message that requests interim results from the service.



* The client sends:

{
"action": "start",
"content-type": "audio/l16;rate=22050",
"interim_results": true
}
<binary audio data>
{
"action": "stop"
}
* The service responds:

{"results": [{"alternatives": {"transcript": "name "}],
"final": false}], "result_index": 0}
Show more
* Get single property

val property: Property? = appConfiguration.getProperty("propertyId")
* Get all properties

val properties: HashMap<String, Property>? = appConfiguration.getProperties();
* Property evaluation

You can use the property.getCurrentValue() method to evaluate the value of the property. Pass a unique entityId as the parameter to perform the property evaluation. If the property is configured with segments in the App Configuration service, you can set the attributes values as a JSONObject.

JSONObject entityAttributes = new JSONObject();
try {
entityAttributes.put("city", "Bangalore");
entityAttributes.put("country", "India");
} catch (JSONException e) {
e.printStackTrace();
}

val appConfiguration = AppConfiguration.getInstance()
val property: Property? = appConfiguration.getProperty("propertyId")
val value = property.getCurrentValue("entityId", entityAttributes)







 Supported data types 

App Configuration service configures the feature flag and properties in the following data types: Boolean, Numeric, String. The String data type can be of the format of a text string, JSON or YAML. Accordingly, the SDK processes each format as shown in Table 1.



Table 1. Example outputs

 Feature or Property value Data type Data format Type of data returned by getCurrentValue() Example output 

 true BOOLEAN not applicable java.lang.Boolean true 
 25 NUMERIC not applicable java.lang.Integer 25 
 a string text STRING TEXT java.lang.String a string text
Note that the Estimator returns a list of values, as it can perform batched evaluations.

>>> print("expectation: ", expectation_value)
expectation: [-1.06329149]

The Estimator Runtime primitive offers a series of features and tuning options that do not have a legacy alternative to migrate from, but can help improve your performance and results. For more information, refer to the following:



* [Error mitigation tutorial](https://qiskit.org/documentation/partners/qiskit_ibm_runtime/tutorials/Error-Suppression-and-Error-Mitigation.html)
* [Setting execution options topic](https://qiskit.org/documentation/partners/qiskit_ibm_runtime/how_to/options.html)
* [Primitive execution options API reference](https://qiskit.org/documentation/partners/qiskit_ibm_runtime/stubs/qiskit_ibm_runtime.options.Options.htmlqiskit_ibm_runtime.options.Options)
* [How to run a session topic](https://qiskit.org/documentation/partners/qiskit_ibm_runtime/how_to/run_session.html)
The GET /v1/recognitions/{id} method is the only way to retrieve job results if



* The job was submitted without a callback URL.
* The job was submitted with a callback URL but without specifying the recognitions.completed_with_results event.
* The job is not one of the 100 latest outstanding jobs. When you omit the id path parameter, only the 100 latest jobs are returned.



However, you can still use the method to retrieve the results for a job that specified a callback URL and the recognitions.completed_with_results event. You can retrieve the results for any job as many times as you want while they remain available. A job and its results remain available until you delete them with the DELETE /v1/recognitions/{id} method or until the job's time to live expires, whichever comes first. By default, results expire after one week unless you specify a different time to live with the results_ttl parameter of the POST /v1/recognitions method.



 Check job status without results example 

The following example checks the status of the job with the specified ID:

IBM Cloud

curl -X GET -u "apikey:{apikey}" "{url}/v1/recognitions/{job_id}"

IBM Cloud Pak for Data

curl -X GET --header "Authorization: Bearer {token}" "{url}/v1/recognitions/{job_id}"

The job is not yet complete, so the response does not include the results.

{
"id": "4bb1dca0-f6b1-11e5-80bc-71fb7b058b20",
"created": "2016-08-17T19:13:23.622Z",
"updated": "2016-08-17T19:13:24.434Z",
"status": "processing"
}





 Check job status with results example 

The following example requests the status of the job with the specified ID:

IBM Cloud
responseData.logdnaId Defines the logging ID that is associated with the IBM Log Analysis instance. 









 Viewing events 

Events that are generated by an instance of the IBM Log Analysis service are automatically forwarded to the IBM Cloud Activity Tracker service instance that is available in the same location. For more information, see [Cloud services locations](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-cloud_services_locations).

IBM Cloud Activity Tracker can have only one instance per location. To view events, you must access the web UI of the IBM Cloud Activity Tracker service in the same location where your service instance is available. For more information, see [Launching the UI through the IBM Cloud UI](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-launch).





 Analyzing events 

Activity Tracker events only report success outcomes.

Activity Tracker events that report update actions do not include information about the delta of the change.
The service sends the signature via the X-Callback-Signature header with each notification. The client can use the secret to compute its own signature of each notification payload. If its signature matches the value of the X-Callback-Signature header, the client knows that the notification was sent by the service and that its contents have not been altered during transmission. This knowledge guarantees that the client is not the victim of a man-in-middle-attack.

HTTPS is ideal for production applications. But during application development and prototyping, the HTTP-based callback notifications that are supported by the service can simplify and accelerate the development process by avoiding the expense of HTTPS.





 Unregistering a callback URL 

You can unregister an allowlisted callback URL at any time by calling the POST /v1/unregister_callback method. Unregistering a callback URL can be useful for testing your application with the service. Once you unregister a callback URL, you can no longer use it with asynchronous recognition requests.



 Unregister a callback URL example 

The following example unregisters a previously registered callback URL:

IBM Cloud

curl -X POST -u "apikey:{apikey}" "{url}/v1/unregister_callback?callback_url=http://{user_callback_path}/results"

IBM Cloud Pak for Data

curl -X POST --header "Authorization: Bearer {token}" "{url}/v1/unregister_callback?callback_url=http://{user_callback_path}/results"









 Creating a job 

You create a recognition job by calling the POST /v1/recognitions method. How you learn the status and results of the job depends on the approach you use and the parameters you pass:



* To use callback notifications, include the callback_url query parameter to specify a URL to which the service is to send callback notifications when the status of the job changes. You can also specify the following optional query parameters:
responseData.logdnaId Defines the Activity Tracker ID that is associated with the Activity Tracker instance. 









 Viewing events 

Events that are generated by an instance of the Activity Tracker service are automatically forwarded to the Activity Tracker service instance that is available in the same location. For more information, see [Cloud services locations](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-cloud_services_locations).

Activity Tracker can have only one instance per location. To view events, you must access the web UI of the Activity Tracker service in the same location where your service instance is available. For more information, see [Launching the web UI through the IBM Cloud UI](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-launch).





 Analyzing events 

Activity Tracker hosted event search offerings events only report success outcomes.

Activity Tracker hosted event search offerings events that report update actions do not include information about the delta of the change.