Understand What Usage Data Is Logged

The following data is included in the deployment statistics and can be compared for the specified deployments. Statistics charts exclude data associated with any deleted deployments or versions.

Sessions

For deployment statistics, one session is counted in the statistics reports for each continuous interaction with a single deployed interview.

A continuous interaction:

  • can be via the provided interview web interface, or interview chat interaction with Oracle Digital Assistant

  • can be managed directly for a custom integration by one of the interview APIs such as the Flow Engine API or the Chat API

  • continues if the user chooses to restart the interview before timeout

  • ends when a timeout occurs. In this case a new interaction starts if the user restarts the interview.

Note: The sessions reported in deployment statistics are not the same as billable Tier 3 sessions. To report on billable usage, see service usage metrics.

Assessments

Assessments are either:

  1. An individual call to the Assess or GetAnswer SOAP web service actions, or
  2. An individual case within a call to the Batch Assess REST API, or
  3. An individual test case assessment made by a test run created through the Test Suites REST API, or
  4. An invocation of a decision service

Interactions

Interactions are an aggregation of sessions and assessments into a single metric. A single interaction is either:

  1. An individual interview session, or
  2. 20 web service assessments.

Interactions based on web service assessments are aggregated by the total number of assessments, not the number of service calls. For example:

  • 1 x call to the Batch Assess API with 21 cases = 2 interactions
  • 1 x call to the Batch Assess API with 15 cases = 1 interaction
  • 1 x call to the Batch Assess API with 15 cases + 5 x calls to the Assess SOAP service = 2 interactions
  • 1 x call to the Batch Assess API with 10 cases + 5 x calls to the Assess SOAP service = 1 interaction

Agents

Agents are either:

  1. B2C Service agents signed in via SSO, or
  2. authorized users as identified by the opauniqueuser parameter.

Referenced decision services

Referenced decision services are decision services assessments that have been invoked as a consequence of a separate assessment of an interview. They are not considered billable events.

Referenced decision services are not included in the preset Web service assessments chart, but a custom chart can be created to view their usage. Note when using a custom chart that only new calls to the decision service are included in the statistics. That is, decision service results are cached in Web Determinations such that it will only invoke the decision service if it doesn't already know the answer due to a previous call (or a new version of the decision service has been deployed).