Here's an example of how you can use the search feature to see all delete operations:

1. Click + Criteria.
2. In the Filter field, select Operation.
3. In the Operator field, select Starts With.
4. In the value field, enter Delete.
5. Click Search.

In the results for that search, you'll see entries for any operations with names beginning with Delete, such as DeleteSkill or DeleteSkillIntent.

These are the event types that Oracle Digital Assistant service instances emit:

com.oraclecloud.digitalassistant.changeodacompartment.begin

com.oraclecloud.digitalassistant.changeodacompartment.end

com.oraclecloud.digitalassistant.createodainstance.begin

com.oraclecloud.digitalassistant.createodainstance.end

com.oraclecloud.digitalassistant.deleteodainstance.begin

com.oraclecloud.digitalassistant.deleteodainstance.end

com.oraclecloud.digitalassistant.updateodainstance

This is a reference event for Oracle Digital Assistant service instances.

{
  "id": "ocid1.eventschema.oc1.phx.abyhqljrfajridyag4epdbthdjuhwgkwxxog32ed4e36yx2zotmphyxe3z5q",
  "exampleEvent": {
    "eventID": "unique_id",
    "eventTime": "2019-10-09T13:58:03.575Z",
    "contentType": "application/json",
    "eventType": "com.oraclecloud.digitalassistant.createodainstance.end",
    "cloudEventsVersion": "0.1",
    "source": "DigitalAssistant",
    "extensions": {
      "compartmentId": "ocid1.compartment.oc1..unique_ID"
    },
    "eventTypeVersion": "2.0",
    "data": {
      "resourceName": "example_name",
      "compartmentId": "ocid1.compartment.oc1..unique_ID",
      "availabilityDomain": "all",
      "compartmentName": "example_name",
      "resourceId": "ocid1.odainstance.oc1.phx.unique_ID"
    }
  },
  "serviceName": "Digital Assistant",
  "displayName": "ODA Instance - Create End",
  "eventType": "com.oraclecloud.digitalassistant.createodainstance.end",
  "additionalDetails": [],
  "timeCreated": "2019-10-09T13:58:03.575Z"
}

Oracle Digital Assistant metrics are emitted with the metric namespace oci_digitalassistant.

Here are the available metrics for Oracle Digital Assistant instances.

You can view metrics by individual service instance or in aggregated form for all instances.

To view metrics for an individual service instance:

1. In the Infrastructure Console, click on the top left to open the navigation menu, select Analytics & AI, and then click Digital Assistant.
2. Select the instance's compartment.
3. Select the instance.
4. Scroll down to the Metrics section of the page to view the metrics.

To view aggregated metrics for all service instances:

1. In the Infrastructure Console, click on the top left to open the navigation menu, select Observability & Management, and then click Service Metrics.
2. In the Compartments dropdown, select the compartment for which you want to view metrics.
3. In the Metric Namespace, select oci_digitalassistant.

The Infrastructure Console provides various billing and payment tools that make it easy to monitor your Oracle Digital Assistant billing, service costs, and usage.

To view your billing and usage, perform the following steps:

1. Sign in to Oracle Cloud as the cloud account administrator. You can find your account name and login information in your welcome email.
2. In the Infrastructure Console, click on the top left to open the navigation menu, select Governance & Administration, and then select one of the following options:

   • Cost Analysis: provides easy-to-use visualization tools to help you track and optimize your spending.

   • Cost and Usage Report: view comma-separated value (CSV) files that can be used to get detailed breakdowns of resources for audit or invoice reconciliation.

     Note
     
     

     The first time you access usage reports, you must create a policy in your root compartment. Follow the instructions on the Usage Report page to create the policy, copying the statements as directed.

   • Budgets: set thresholds for your spending. You can set alerts on your budget to let you know when you might exceed your budget, and you can view all of your budgets and spending from one single place.

   • Invoices: view and download invoices for your usage.

For more information on the billing and payment tools, see Billing and Payment Tools Overview.

If you submit a service request (SR) and Oracle Support determines that it needs access to some of your data for debugging purposes, you can agree to give them temporary access to your service instance data. Here's the general flow of the process:

1. You submit an SR.
2. If Oracle Support determines that they need access to any of your data for debugging purposes, they will contact your administrator via email for approval to conduct a Break Glass session. (The email has a link to the Temporary Access Approval page of your Digital Assistant, where your administrator can click Approve or Reject.)
3. If your administrator approves the request, a temporary password is generated to enable Oracle Support to start a Break Glass session, in which they can access the required data.
4. Once Oracle support completes its work in the Break Glass session, they terminate the session. If they don't explicitly terminate the session, it expires automatically within the timeframe that you have agreed upon.

By default, Oracle provides and manages the TDE keys for encrypting the data in your Digital Assistant instance.

If your instance has Break Glass enabled, you can also replace the Oracle-provided private key with your own, which also enables you to rotate the keys as you require.

Oracle Digital Assistant is architected for high availability (HA). However, if you need to ensure that your instance can still function if a disaster strikes your instance's region, you can request to have cross-region failover set up.

When cross-region failover is set up and the primary instance goes down:

• Any runtime requests to the primary instance are redirected to the backup instance.
• A banner appears in the Digital Assistant UI that notes that the backup instance is being used.
• You should not do any work on skills, digital assistants, channels, Insights, or other artifacts (whether through the UI or through REST APIs) in the backup instance. Any changes you make in the backup instance will not be preserved when the primary instance is restored.

When the outage ends:

• Service to the primary instance is restored.
• Any Insights data that has accumulated on the backup instance is preserved and combined with existing Insights data associated with the primary instance.
• Artifacts such as skills and digital assistants are restored to the state they were in when the primary instance went down. (Practically speaking, this simply means any changes that you happen to make to these artifacts in the backup instance won't be preserved.)

To set up cross-region failover:

1. File a service request (SR) for cross-region failover and, in the request, mention the instance URL of the primary Digital Assistant instance.
2. Once the Support team has responded to you with information on which backup regions are available, subscribe to a backup region in the OCI Console.

   The Support team will then create the backup instance.

During the failover setup, a system-level skill (named Echo) is set up in the instance you have specified and exposed through a web channel (named heartbeat) in that instance. From the backup region, the primary instance is then regularly polled for its health status through this skill.

To set up a private endpoint for Digital Assistant, you follow these general steps:

1. Make sure that you have the required permissions to configure private endpoints and attach them to Digital Assistant instances.
2. If you don't already have them in place, on the OCI Console, create a virtual cloud network (VCN) and its associated resources, including:
   • At least one subnet.
   • Route tables to route the traffic through the subnet to its destinations.
   • Security lists or network security groups to establish a set of ingress and egress security rules that you'll use for the private endpoint.
   • Optionally, an Internet gateway to give Internet access to the VCN.
   • Optionally, an NAT (Network Address Translation) gateway, which gives resources that don't have public IP addresses access to the Internet without exposing them to incoming Internet connections.

   See the OCI documentation for VCNs and subnets.

3. Create the private endpoint and associate it with your Digital Assistant instance.
4. In Digital Assistant, configure a data service or REST service that points to the endpoint.

To set up private endpoints, you need to have the proper permissions in the Infrastructure Console.

There are two resource types for private endpoints that encompass these required permissions:

• oda-private-endpoints - enables you to configure private endpoints and SCAN proxies.
• oda-private-endpoint-attachments - enables you to attach a private endpoint a Digital Assistant instance.

Permissions for those resource types are also part of the oda-family resource type. So if you are covered by a policy statement to manage oda-family resource types in the compartment where your private endpoint is, you don't have to create separate policies for your private endpoints.

The following are examples of broad policies to enable creation and configuration of private endpoints and attach them to Digital Assistant instances.

allow group <group-name> to manage oda-private-endpoints in compartment <private-endpoint-compartment>
allow group <group-name> to manage oda-private-endpoint-attachments in compartment <private-endpoint-compartment>

For more detail on how policies work, see Digital Assistant Policies.

1. In the Infrastructure Console, click on the top left to open the navigation menu, select Analytics & AI, and select Digital Assistant (which appears under the AI Services category on the page).
2. In the left navigation of the AI Services page that appears, click Private endpoints.
3. If you haven't already done so, create the compartment where you want to keep the private endpoint and, optionally, add the VCN and subnet you will be using to that compartment.

   See Understanding Compartments and Managing Compartments.

4. Click Create private endpoint and fill in the required fields, including the VCN and private subnet.
5. Once the endpoint is created, click Associate ODA Instance, select the compartment that contains the Digital Assistant instance that you want to be able to use the private endpoint, and then select that instance.

Once you have created a private endpoint, you need to add a service for that private endpoint to use it in Digital Assistant.

• To add a data service for the private endpoint, see Connect to the Data Service.
• To add a REST service for the private endpoint, see Add a REST Service for an Endpoint.

If you are using your private endpoint for a RAC-enabled database, you also need to configure a SCAN proxy for the private endpoint.

To set up a SCAN proxy:

1. Get the SCAN DNS name and port number for the database.
   • If the database is an on-premises database, get it from the database administrator.
   • If the database is on OCI, do the following in the Infrastructure Console:
     1. Navigate to the DB System Details page for the database and select the DB system information tab.
     2. In the Network section of the page, copy the SCAN DNS name and paste it in a convenient place.
     3. Note the Port Number.
2. In the Infrastructure Console, click on the top left to open the navigation menu, select Analytics & AI, and select Private endpoints (which appears under the AI Services category on the page).
3. Select your private endpoint.
4. In the Resources section of the page, select SCAN proxies.
5. Click Add SCAN proxy.
6. In the Add SCAN proxy dialog, select the type (FQDN (for fully-qualified domain name) or IP address) and then fill in the rest of the required fields.
   • If you have selected FQDN as the proxy type, use the database's SCAN DNS name for the Host name and the database's port number as the Port.
   • If you have selected IP address as the proxy type, click Add SCAN Listener to add IP addresses and port numbers for one or more SCAN listeners in the database.

In general, the process for importing packages using the API (either directly or via the CLI or one of the SDKs) is:

1. If it doesn't yet exist, create the Oracle Digital Assistant instance where you want to import the package.
   1. Call CreateOdaInstance to create the instance.
   2. From the response to the CreateOdaInstance call, take the opc-work-request-id response header value and use it to call GetWorkRequest to monitor the progress of the instance creation operation.
   3. Once the instance creation has completed, using the value of the odaInstanceId attribute that was returned in the response body to call GetOdaInstance.
2. Call ListPackages to see what packages are available for the instance (or instances) that you specify.
3. For any available packages that you want to import, call GetPackage to get the package's import contract.

   The import contract specifies conditions that need to be satisfied before you can import the package. This might include things like specifying an auth provider and filling in values for custom parameters.

4. Satisfy the import contract.

   You do so by constructing a payload that provides values for all of the required parameters in the import contract. The payload might looks something like this:

   {
       "packageId": "<packageId-OCID>",
       "parameterValues": {
           "authProvider.providerX.clientSecret": "some value",
           "authProvider.providerX.authorizationEndpointUrl": "http://host:80/file",
           "authProvider.providerX.revokeEndpointUrl": "http://host:80/file",
           "authProvider.providerX.allowedScopes": "some value",
           "authProvider.providerX.tokenEndpointUrl": "http://host:80/file",
           "authProvider.IDCS_OAuthForIDR.allowedScopes": "some value",
           "authProvider.providerX.clientId": "some value",
           "skillParameter.da.backendRestEndPoint": "http://host:80/file",
       }
   }

   To simplify this task, the GetPackage response contains a section called defaultParameterValues that you can use to assemble the parameter value portion of the payload.

5. Import the package into the instance(s).
   1. Call CreateImportedPackage using the payload you just assembled.
   2. From the response to the CreateImportedPackage call, take the opc-work-request-id response header value and use it to call GetWorkRequest to monitor the progress of the package import operation.
   3. Once the package import has completed, using the value of the odaInstanceId attribute that was returned in the response body to call GetImportedPackage to view the package details.

If an update for a package is available, you can add that updated package to the instance through the UpdateImportedPackage operation.