vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Check mark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 
 Filter and search data ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 
 Use views to monitor events ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) !
[Check mark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) 
 Filter and search data ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Check mark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) 
 Use views to monitor logs !
* Search health check events for a specific DNS Services instance. ![search events by CRN](https://cloud.ibm.com/docs-content/v1/content/d56dbd8ab7d14086029681ee71679e14aea53723/dns-svcs/images/health-check-type-filter-crn.png){: caption="Figure 2. Search events by CRN" caption-side="bottom"
* Search health check events for a pool by specifying its name and its DNS Services instance. ![search events by CRN and pool name](https://cloud.ibm.com/docs-content/v1/content/d56dbd8ab7d14086029681ee71679e14aea53723/dns-svcs/images/health-check-type-filter-crn-pool.png){: caption="Figure 3. Search events by CRN and pool name" caption-side="bottom"
* Search health check events for an origin by specifying its name and its DNS Services instance. ![search events by CRN and origin name](https://cloud.ibm.com/docs-content/v1/content/d56dbd8ab7d14086029681ee71679e14aea53723/dns-svcs/images/health-check-type-filter-crn-origin.png){: caption="Figure 4. Search events by CRN and origin name" caption-side="bottom"
* Search health check events for an origin when its status becomes healthy by specifying its name and overall_health fields and also its DNS Services instance. !
In this case, nf85a2apeerorg1-5765d88c85-jglk2 represents the name of the peer pod.





 View smart contract logs 

The process to view the logs for a smart contract is similar to how you view your node logs but varies depending on whether your peer is running a Fabric v1.4 or v2.x image. The Fabric version that the peer is running is visible when you click on a peer node in the console:

Zoom

![How to find peer fabric version](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/peerversion.png)

Figure 2.How to find peer fabric version



 Hyperledger Fabric v1.4 peer image 

![version 1.4](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/1-4_Pill.png) When your peer is using the Hyperledger Fabric v1.4 image, additional strings are required in the search input box.



* Just like when you view node logs, you filter on the pod name, but it needs to be the name of the peer pod where the smart contract is running.
* Smart contracts run in a dind container in the pod, but the logs are forwarded to the chaincode-logs container which is of type fluentd. Therefore, to filter the logs to only include the smart contract events, you need to include app:fluentd in the search input box.
* Finally, you can append the name and optionally the version of the smart contract, marbles 1.0.0.



The full search string, including the namespace, would be similar to the following example:

pod:n4c817fpeer1org1-55885d5666-zq55t app:fluentd marbles 1.0.0

Zoom

!
Via: SIP/2.0/UDP agenta.atlanta.example.com;branch=z9hG4bK2293940223
To: <sip:b@atlanta.example.com>
From: <sip:a@atlanta.example.com>;tag=193402342
Call-ID: 898234234@agenta.atlanta.example.com
CSeq: 23 REFER
Max-Forwards: 7
Refer-To: sip:user@domain.com
X-Watson-Assistant-Token: 8f817472-8c57-4117-850d-fdf4fd23ba7
User-to-User: 637573746f6d2d757365722d746f2d75736572;encoding=hex
Contact: sip:a@atlanta.example.com
Content-Length: 0

If a custom User-to-User header is specified, then the session history key is set in the X-Watson-Assistant-Session-History-Key header:

REFER sip:b@atlanta.example.com SIP/2.0
Via: SIP/2.0/UDP agenta.atlanta.example.com;branch=z9hG4bK2293940223
To: <sip:b@atlanta.example.com>
From: <sip:a@atlanta.example.com>;tag=193402342
Call-ID: 898234234@agenta.atlanta.example.com
CSeq: 93809823 REFER
Max-Forwards: 70
Refer-To: sip:user@domain.com
User-to-User: 637573746f6d2d757365722d746f2d75736572;encoding=hex
Example 2: Adds user input.

from ibm_watson import AssistantV2
from ibm_cloud_sdk_core.authenticators import IAMAuthenticator

 Create Assistant service object.
authenticator = IAMAuthenticator('{apikey}') replace with API key
assistant = AssistantV2(
version = '2021-11-27',
authenticator = authenticator
)
assistant.set_service_url('{url}') replace with service instance URL
assistant_id = '{environment_id}' replace with environment ID

 Initialize with empty value to start the conversation.
message_input = {
'message_type:': 'text',
'text': ''
}

 Main input/output loop
while message_input['text'] != 'quit':

 Send message to assistant.
result = assistant.message_stateless(
assistant_id,
input = message_input
).get_result()

 Print responses from actions, if any. Supports only text responses.
if result['output']:
for response in result['output']:
if response['response_type'] == 'text':
print(response['text'])

 Prompt for the next round of input unless skip_user_input is True.
if not result['context']['system'].get('skip_user_input', False):
user_input = input('>> ')
message_input = {
'text': user_input
}

Show more

// Example 2: Adds user input.

const prompt = require('prompt-sync')();
const AssistantV2 = require('ibm-watson/assistant/v2');
const { IamAuthenticator } = require('ibm-watson/auth');

// Create Assistant service object.
const assistant = new AssistantV2({
version: '2021-11-27',
curl -X GET "https://<region>.appid.cloud.ibm.com/management/v4/<tenantID>/cloud_directory/Users?query=<identifyingSearchQuery>" -H "accept: application/json" -H "authorization: Bearer <token>"

Example:

curl -X GET https://us-south.appid.cloud.ibm.com/management/v4/e19a2778-3262-4986-8875-8khjafsdkhjsdafkjh/cloud_directory/Users?query=user@domain.com
-H "accept: application/json"
-H "authorization: Bearer eyJraWQiOiIyMDE3MTEyOSIsImFsZ...."
3. By using the ID that you obtained in the previous step, make a GET request to the cloud_directory/users endpoint to see their full user profile.

curl -X GET "https://<region>.appid.cloud.ibm.com/management/v4/<tenantID>/cloud_directory/Users/<userID>" -H "accept: application/json" -H "authorization: Bearer <token>"

Example response:

{
"sub": "c155c0ff-337a-46d3-a22a-a8f2cca08995",
"name": "Test User",
"email": "testuser@test.com",
"identities": [
{
"provider": "cloud_directory",
"id": "f1772fcc-ff70-4d88-81a0-07dd7a3d988f",
"idpUserInfo": {
"displayName": "Test User",
"active": true,
"mfaContext": {},
"emails":
{
"value": "testuser@test.com",
"primary": true
}
],
"meta": {
To get an AUTH_TOKEN and the GUID see, [Headers for IAM Tokens](https://cloud.ibm.com/docs/monitoring?topic=monitoring-mon-curlmon-curl-headers-iam).
* to and from are query parameters that you must define to configure the period of time for which you want information on the notifications.



For more information about the response format, see [notification schema](https://cloud.ibm.com/docs/monitoring?topic=monitoring-notifications_apinotifications-api-parm-req-schema).





 Fetch specific user notification 

You can use the following cURL command to get information about a notification channel:

curl -X GET <REST_API_ENDPOINT>/api/notificationChannels/<NOTIFICATION_ID> -H "Authorization: $AUTH_TOKEN" -H "IBMInstanceID: $GUID" -H "SysdigTeamID: $TEAM_ID" -H "content-type: application/json"

Where



* <REST_API_ENDPOINT>indicates the endpoint targetted by the REST API call. For more information, see [Monitoring REST API endpoints](https://cloud.ibm.com/docs/monitoring?topic=monitoring-endpointsendpoints_rest_api). For example, the public endpoint for an instance that is available in us-south is the following: https://us-south.monitoring.cloud.ibm.com/api
* You can pass multiple headers by using -H.

Authorization and IBMInstanceID are headers that are required for authentication.

SysdigTeamID is optional. When you specify this header, you limit the request to the data and resources available for the team specified.

To get an AUTH_TOKEN and the GUID see, [Headers for IAM Tokens](https://cloud.ibm.com/docs/monitoring?topic=monitoring-mon-curlmon-curl-headers-iam).
* <NOTIFICATION_ID> defines the ID of the notification that you want to modify.
[Yes](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/checkmark-icon.svg) ![Yes](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/checkmark-icon.svg) ![Yes](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/checkmark-icon.svg) 
 connect_to_agent ![Yes](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/checkmark-icon.svg) ![Yes](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/checkmark-icon.svg) ![Yes](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/checkmark-icon.svg) 
 date ![Yes](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/checkmark-icon.svg) 
 dtmf !
,"m1","u1"],"u2","u4","u5","u6","d2","m2"],"u10","u7","d3","u5","u6","m3"],"u9","u13","u3","d4","u8","m4"],"u10","u16","u7","u11","m5","d5"],"u14","d6","m6","u12"],"u13","u20","u15","u14","u12","d7","u9","m7"],"u16","u18","u19","d8","u17","u11","m8","u22"],"m9","d9","u17","u19"],"m10","u20","u15","u21","u24","d10"],"u29","u18","m11","d11","u22","u23"],"d12","u25","u21","u27","u32","m12","u24","u26"],"u30","u25","u27","d13","u28","m13"],"u30","u34","u29","d14","u31","u28","m14","u23"],"u37","d15","u33","u32","m
If you are creating a service ID for a pool of private workers, specify the name of the private workers pool, for example: Pipeline Private Workers for Acme.
5. Click Create.
6. Save your service ID for later use. The service ID is required on the Kubernetes cluster that is targeted for the Delivery Pipeline Private Worker installation.







 Creating a service ID by using the CLI 

From the IBM Cloud CLI, type the following command:

$ ibmcloud iam service-id-create {worker-pool-name} -d "{worker-pool-description}"

Creating service ID {worker-pool-name} bound to current account as username@domain.com...OK
Service ID {worker-pool-name} is created successfully

Name {worker-pool-name}
Description {worker-pool-description}
CRN crn:v1:bluemix:public:iam-identity::a/8d63fb1cc5e99e86dd7229dddff75fef::serviceid:ServiceId-38ffff31-3ea3-4ecc-9732-190f7a993097
Bound To crn:v1:bluemix:public:::a/8d63fb1cc5e99e86dd7229dddff75fef:::
Version 1-6df15bde97b6e87f583a557f8731888f
Locked false
UUID ServiceId-38ffff31-3ea3-4ecc-9732-190f7a993097







 Creating an API key 

An API key is a unique code that is passed to an API to identify the application or user that is calling it. To prevent malicious use of an API, you can use API keys to track and control how that API is used. For more information about API keys, see [Understanding API keys](https://cloud.ibm.com/docs/account?topic=account-manapikey).



 Creating an API key in the console 



1.
const session = require('express-session')
const passport = require('passport');
const WebAppStrategy = require("ibmcloud-appid").WebAppStrategy;
const CALLBACK_URL = "/ibm/cloud/appid/callback";
2. Set up your express app to use express-session middleware.

const app = express();
app.use(session({
secret: "123456",
resave: true,
saveUninitialized: true
}));
app.use(passport.initialize());
app.use(passport.session());

You must configure the middleware with the proper session storage for production environments. For more information, see the [express.js](https://expressjs.com/).
3. Obtain your credentials in one of the following ways.



* By navigating to the Applications tab of the App ID dashboard. If you don't have an application in the list, you can click Add application to create a one.
* By making a POST request to the [/management/v4/<tenantId>/applications endpoint](https://us-south.appid.cloud.ibm.com/swagger-ui//Management%20API%20-%20Applications/mgmt.registerApplication).

Request format:

curl -X POST https://us-south.appid.cloud.ibm.com/management/v4/39a37f57-a227-4bfe-a044-93b6e6060b61/applications/ -H 'Content-Type: application/json' -H 'Authorization: Bearer <IAMToken>' -d '{"name": "ApplicationName"}'

Example response:

{
"clientId": "111c22c3-38ea-4de8-b5d4-338744d83b0f",
(https://cloud.ibm.com/docs/appid?topic=appid-adding-overview)[Configure Cloud Directory Set up your own user registry to allow users to sign in with an email and password.](https://cloud.ibm.com/docs/appid?topic=appid-cloud-directory)[Controlling access Define which users and applications can access specific features or perform specific actions in your apps.](https://cloud.ibm.com/docs/appid?topic=appid-access-control)

 Video library 

[![carousel thumbnail](https://cloud.ibm.com/docs-content/v1/content/appid//images/appid-about-video-thumbnail.png)<br><br>About App ID](https://cloud.ibm.com/docs/appid?topic=appid-about)[![carousel thumbnail](https://cloud.ibm.com/docs-content/v1/content/appid//images/appid-nodejs-video-thumbnail.png)<br><br>Technologies Under the Hood](https://cloud.ibm.com/docs/appid?topic=appid-key-concepts)[![carousel thumbnail](https://cloud.ibm.com/docs-content/v1/content/appid//images/appid-mng-api-video-thumbnail.png)<br><br>Using the App ID Management API](https://cloud.ibm.com/docs/appid?topic=appid-regions-endpointsapi-try)[![carousel thumbnail](https://cloud.ibm.com/docs-content/v1/content/appid//images/appid-nodejs-video-thumbnail.png)<br><br>Protecting Node.js Backend Applications](https://cloud.ibm.com/docs/appid?topic=appid-backend)[![carousel thumbnail]
[MAS-MS-Password-Change-9](https://cloud.ibm.com/docs-content/v1/content/ce5408d6eecb7244ea40dac01f6d3acf7ff60148/mas-saas/images/MAS-MS-Password-Change-9.png)

Figure 9. MAS Login Set Password







 How to Create an IBMid 

To register for product support and create cases (tickets) for MAS SaaS, you will need an IBMid. Note: If you already have an IBMid, please proceed to [How to Register for Maximo Application Suite Support](https://cloud.ibm.com/docs/mas-saas?topic=mas-saas-getting-started-with-ibm-maximo-application-suite-saashow-to-register-for-mas-support)



1. To create an IBMid, click the following link: [https://myibm.ibm.com](https://myibm.ibm.com)
2. Click Create an IBMid

Zoom

![MAS-MS-IBMid-Click-Create](https://cloud.ibm.com/docs-content/v1/content/ce5408d6eecb7244ea40dac01f6d3acf7ff60148/mas-saas/images/MAS-MS-IBMid-Click-Create.png)

Figure 1. Create IBMid
3. Enter the applicable information (you will need to provide a valid email address) and click Next

Zoom

![MAS-MS-IBMid-Enter-Applicable-Information](https://cloud.ibm.com/docs-content/v1/content/ce5408d6eecb7244ea40dac01f6d3acf7ff60148/mas-saas/images/MAS-MS-IBMid-Enter-Applicable-Information.png)

Figure 2. IBMid - Enter Applicable Information
4.
[MAS-MS-Password-Change-9](https://cloud.ibm.com/docs-content/v1/content/ce5408d6eecb7244ea40dac01f6d3acf7ff60148/mas-saas/images/MAS-MS-Password-Change-9.png)

Figure 9. MAS Login Set Password







 How to Create an IBMid 

To register for product support and create cases (tickets) for MAS SaaS, you will need an IBMid. Note: If you already have an IBMid, please proceed to [How to Register for Maximo Application Suite Support](https://cloud.ibm.com/docs/mas-saashow-to-register-for-mas-support)



1. To create an IBMid, click the following link: [https://myibm.ibm.com](https://myibm.ibm.com)
2. Click Create an IBMid

Zoom

![MAS-MS-IBMid-Click-Create](https://cloud.ibm.com/docs-content/v1/content/ce5408d6eecb7244ea40dac01f6d3acf7ff60148/mas-saas/images/MAS-MS-IBMid-Click-Create.png)

Figure 1. Create IBMid
3. Enter the applicable information (you will need to provide a valid email address) and click Next

Zoom

![MAS-MS-IBMid-Enter-Applicable-Information](https://cloud.ibm.com/docs-content/v1/content/ce5408d6eecb7244ea40dac01f6d3acf7ff60148/mas-saas/images/MAS-MS-IBMid-Enter-Applicable-Information.png)

Figure 2. IBMid - Enter Applicable Information
4. Upon submission, a confirmation code will be sent from ibmacct@iam.ibm.com to the email address you provided

Zoom

!
curl -X POST https://us-south.appid.cloud.ibm.com/management/v4/39a37f57-a227-4bfe-a044-93b6e6060b61/applications/ -H 'Content-Type: application/json' -H 'Authorization: Bearer <IAMToken>' -d '{"name": "ApplicationName"}'

Example response:

{
"clientId": "111c22c3-38ea-4de8-b5d4-338744d83b0f",
"tenantId": "39a37f57-a227-4bfe-a044-93b6e6060b61",
"secret": "ZmE5ZDQ5ODctMmA1ZS00OGRiLWExZDMtZTA1MjkyZTc4MDB4",
"name": "ApplicationName",
"oAuthServerUrl": "https://us-south.appid.cloud.ibm.com/oauth/v4/39a37f57-a227-4bfe-a044-93b6e6060b61"
}



4. Optional: Decide how to format your redirect URI. The redirect can be formatted in two different ways.



* Manually in a new WebAppStrategy({redirectUri: "...."})
* As an environment variable named redirectUri



If neither are provided, the App ID SDK tries to retrieve the application_uri of the app that is running on IBM Cloud and append a default suffix /ibm/cloud/appid/callback.
5. By using the information obtained in the previous steps, initialize the SDK.

passport.use(new WebAppStrategy({
tenantId: "<tenantID>",
clientId: "<clientID>",
secret: "<secret>",
oauthServerUrl: "<oauthServerURL>",
nzsql -host X.XX.XXX.XXX -u admin -pw password
Welcome to nzsql, the IBM Netezza SQL interactive terminal.
Type: h for help with SQL commands
? for help on internal slash commands
g or terminate with semicolon to execute query
q to quit

SYSTEM.ADMIN(ADMIN)=>
Show more
2. Register an AzureAD external authentication system.
Specify the clientid and tenantid parameters.

REGISTER EXTERNAL AUTHENTICATION SYSTEM 'AzureAD' with clientid 'AZURE CLIENT ID' tenantid 'AZURE TENANT ID';
SET VARIABLE
3. Create a user or users with the external authentication method set to AzureAD.

CREATE USER "USER" with auth external 'AzureAD';
4. Verify whether the user was created successfully.

q

nzsql -u '"USER"' -pw PASSWORD

Example:

q

nzsql -u '"xyz@example.example.com"' -pw XXXXXXXXXXXXXX
Welcome to nzsql, the IBM Netezza SQL interactive terminal.

Type: h for help with SQL commands
? for help on internal slash commands
g or terminate with semicolon to execute query
q to quit

SSL enabled connection. Cipher: ECDHE-RSA-AES256-GCM-SHA384, bits: 256, protocol: TLSv1.2

SYSTEM.ADMIN(xyz@example.example.com)=>
* Click Add a new Identifier button.

Zoom

![Add new Identifier button](https://cloud.ibm.com/docs-content/v1/content/4c9a07fe500838e5e55e71e73131ef20b44a6c66/event-notifications/images/en-apns-new-identifier-button.png)

Figure 6. Add new Identifier button
* Select the Web Push IDs option.

Zoom

![Web Push IDs option](https://cloud.ibm.com/docs-content/v1/content/4c9a07fe500838e5e55e71e73131ef20b44a6c66/event-notifications/images/en_safari_webpushid_option.png)

Figure 7. Web Push IDs option
* Provide Identifier and description for your Web Push ID, identifier is unique reverse-domain string for your Web Push ID such as web.com.example.domain (the string must start with web). If your website is yourwebsite.com add the identifier as web.com.yourwebsite.

Zoom

![Web Push IDs](https://cloud.ibm.com/docs-content/v1/content/4c9a07fe500838e5e55e71e73131ef20b44a6c66/event-notifications/images/en_safari_webpushid.png)

Figure 8. Web Push IDs
* Continue and then click Create certificate on the next page.

Zoom

![Create Certificate Button](https://cloud.ibm.com/docs-content/v1/content/4c9a07fe500838e5e55e71e73131ef20b44a6c66/event-notifications/images/en_createcertificate_button.png)

Figure 9. Create Certificate Button

Zoom

!
Be sure to give the service ID a description that helps you retrieve the service ID later, such as including the project name. For a complete listing of the iam service-id-create command and its options, see the [ibmcloud iam service-id-create](https://cloud.ibm.com/docs/account?topic=cli-ibmcloud_commands_iamibmcloud_iam_service_id_create) command.

For example, the following command creates a service ID called codeengine-myproject-id with the description Service ID for IBM Cloud Container Registry in Code Engine project myproject:

ibmcloud iam service-id-create codeengine-myproject-id --description "Service ID for IBM Cloud Container Registry in Code Engine project my proj"
2. Create a custom IBM Cloud IAM policy for your service ID that grants access to IBM Cloud Container Registry with the iam service-policy-create command. For a complete listing of the iam service-policy-create command and its options, see the [ibmcloud iam service-policy-create](https://cloud.ibm.com/docs/account?topic=cli-ibmcloud_commands_iamibmcloud_iam_service_policy_create) command.

For example, the following command creates a policy for codeengine-myproject-id service ID with the role of Reader:

ibmcloud iam service-policy-create codeengine-myproject-id --roles Reader --service-name container-registry

The following table summarizes the options that are used with the iam service-policy-create command in this example. For more information about the command and its options, see the [ibmcloud iam service-policy-create](https://cloud.ibm.com/docs/account?topic=cli-ibmcloud_commands_iamibmcloud_iam_service_policy_create) command.



Table 4. iam service-policy-create command components

 Option Description 

 <service_ID> Required. Replace with the codeengine-<project_name>-id service ID that you previously created.