rasa_semantic_schema/dbt_project.yml at master · dlt-hub/rasa_semantic_schema · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
name: 'rasa_semantic_schema'
version: '1.2.0'
config-version: 2
require-dbt-version: [">=1.0.0", "<1.1.0"]


# provide a profile name to access particular warehouse, following profiles are available
# - rasa_semantic_schema_redshift to access Redshift warehouse
# - rasa_semantic_schema_bigquery to access BigQuery via environment variables (keyfile_json)
# - rasa_semantic_schema_bigquery_service_file to access BigQuery via service account file
# profile: 'rasa_semantic_schema_redshift'


vars:

  # configure external sessions and user ids

  # the session_started and user events fields used to identify users
  # use sender_id if no additional information is passed
  user_id: 'sender_id'
  # external session identifier passed into session_started and user events
  # use sender_id if no such session is passed
  external_session_id: 'sender_id'


  # in dictionary below you can configure metrics based on count of occurrences intents or actions
  # in conversations or sections
  count_metrics:
    # below are standard model performance metrics that could be useful regardless of particular bot business logic
    - intent_out_of_scope:
      # user wants something that bot understands but cannot do
      - out_of_scope
    - intent_nlu_fallback:
      # (bot does not understand what user wants. that's low confidence situation
      - nlu_fallback
    - action_default_fallback:
      # bot got into situation that does not know what to do next. so there's a problem in the story
      - action_default_fallback
    - action_unlikely_intent:
      #  flag a particular intent at particular step in conversation as unexpected
      - action_unlikely_intent

    # below are additional metrics ie. to count handoffs
    - intents_frustrated:
      # intents indicating that user is frustrated, angry, disappointed with the service
      - react_frustrated
    - intents_happy:
      # intents indicating that user is happy with the service
      - thankyou
    - intents_raise_dispute:
      # intents indicating that bot didn't perform as expected by the user and bot's action is disputed
      - raise_dispute
    - actions_agent_handoff:
      # actions indicating that user was redirected to human agent / outside service
      - utter_redirect_to_faqs
      - action_agent_handoff

  # a list of intents that indicate starting a story/skill, available on interaction and session level
  story_intents:
    - request_limit_change
    - enquire_transaction_failure
    - request_transaction_refund
    - view_bill_details
    - view_transactions
    - view_user_details

  # new session gap (old SDK compat) in minutes (defaults disables check)
  compat_old_session_gap_minutes: 5256000

# seeds:
#   # where to store seeds with scenario intents, funnel steps etc.
#   schema: views


# These configurations specify where dbt should look for different types of files.
# The `source-paths` config, for example, states that models in this project can be
# found in the "models/" directory. You probably won't need to change these!
model-paths: ["models"]
analysis-paths: ["analysis"]
test-paths: ["tests"]
seed-paths: ["seeds"]
macro-paths: ["macros"]
snapshot-paths: ["snapshots"]

target-path: "target"  # directory which will store compiled SQL files
clean-targets:         # directories to be removed by `dbt clean`
  - "target"
  - "dbt_packages"