Tj202/pr views (#40)

* Adding notice

* Removed wrong notice

* Adding analytics view

* minor changes

* updating view to use a single GROUP BY

* Creating views in the keyspace given now

---------

Co-authored-by: Glenn Galvizo <[email protected]>

docs/source/guide.rst

@@ -137,9 +137,9 @@ Agent analysts will follow this workflow:
    For logs stored locally, you can find them in the :file:`./agent-activity` directory.
    *We recommend the former, as it allows for easy ad-hoc analysis through Couchbase Query and/or Couchbase Analytics.*
 
-2. **Log Transformations**: For users with Couchbase Analytics enabled, we provide four views (expressed as
-   Couchbase Analytics UDFs) to help you get started with conversational-based agents.
-   All UDFs below belong to the scope :file:`agent_activity`.
+2. **Log Transformations**: For users with Couchbase Analytics enabled, we provide the following views (expressed as
+   Couchbase Analytics Views) to help you get started with conversational-based agents.
+   All Views below belong to the scope :file:`agent_activity`.
 
    .. admonition:: Sessions ``(sid, start_t, vid, msgs)``
 

libs/agentc_core/agentc_core/analytics/create.py

@@ -54,8 +54,7 @@ def create_analytics_udfs(cluster: couchbase.cluster.Cluster, bucket: str) -> No
         with open(ddl_file, "r") as fp:
             raw_ddl_string = fp.read()
             ddl_string = (
-                raw_ddl_string.replace("[ANALYTICS?]", "ANALYTICS")
-                .replace("[BUCKET_NAME]", bucket)
+                raw_ddl_string.replace("[BUCKET_NAME]", bucket)
                 .replace("[SCOPE_NAME]", DEFAULT_AUDIT_SCOPE)
                 .replace("[LOG_COLLECTION_NAME]", DEFAULT_AUDIT_COLLECTION)
             )

libs/agentc_core/agentc_core/analytics/ddls/all_sessions.sqlpp

@@ -1,4 +1,4 @@
-CREATE OR REPLACE ANALYTICS VIEW Sessions AS
+CREATE OR REPLACE ANALYTICS VIEW `[BUCKET_NAME]`.`[SCOPE_NAME]`.Sessions AS
 WITH
     DeDuplicatedLogs AS (
         FROM

libs/agentc_core/agentc_core/analytics/ddls/exchanges.sqlpp

@@ -1,6 +1,6 @@
 -- Note: all_sessions.sqlpp should be run before this script.
 -- TODO (GLENN): The purpose of this view is to aid in using Ragas, but we should use the raw_logs instead.
-CREATE OR REPLACE ANALYTICS VIEW LatestMessages AS
+CREATE OR REPLACE ANALYTICS VIEW `[BUCKET_NAME]`.`[SCOPE_NAME]`.LatestMessages AS
 WITH LatestGenerations AS (
     FROM
         `[BUCKET_NAME]`.`[SCOPE_NAME]`.`[LOG_COLLECTION_NAME]` AS s

libs/agentc_core/agentc_core/analytics/ddls/last_session.sqlpp

@@ -1,9 +1,9 @@
 -- Note: all_sessions.sqlpp should be run before this script.
-CREATE OR REPLACE [ANALYTICS?] FUNCTION
+CREATE OR REPLACE ANALYTICS FUNCTION
     `[BUCKET_NAME]`.`[SCOPE_NAME]`.LastSession () {
         (
             FROM
-                `[BUCKET_NAME]`.`[SCOPE_NAME]`.Sessions() AS s
+                `[BUCKET_NAME]`.`[SCOPE_NAME]`.Sessions AS s
             SELECT VALUE
                 s.sid
             ORDER BY

libs/agentc_core/agentc_core/analytics/ddls/llm_generations.sqlpp

@@ -0,0 +1,11 @@
+CREATE OR REPLACE ANALYTICS VIEW LLMGenerations AS
+    SELECT
+        session,
+        grouping_id,
+        ( FROM g gi SELECT VALUE gi.rl ) AS generation
+    FROM
+        `[BUCKET_NAME]`.`[SCOPE_NAME]`.`[LOG_COLLECTION_NAME]` AS rl
+    GROUP BY
+        rl.session AS session,
+        rl.`grouping` AS grouping_id
+        GROUP AS g;

libs/agentc_core/agentc_core/analytics/ddls/tool_calls.sqlpp

@@ -1,5 +1,5 @@
 -- Note: all_sessions.sqlpp should be run before this script.
-CREATE OR REPLACE ANALYTICS VIEW ToolCalls AS
+CREATE OR REPLACE ANALYTICS VIEW `[BUCKET_NAME]`.`[SCOPE_NAME]`.ToolCalls AS
 FROM
     -- The tool calls our LLM has authored.
     Sessions AS s1,

libs/agentc_core/agentc_core/analytics/ddls/trajectories.sqlpp

@@ -1,5 +1,5 @@
 -- Note: all_sessions.sqlpp should be run before this script.
-CREATE OR REPLACE ANALYTICS VIEW Walks AS
+CREATE OR REPLACE ANALYTICS VIEW `[BUCKET_NAME]`.`[SCOPE_NAME]`.Walks AS
 FROM
     Sessions AS s,
     s.msgs AS msg