From 3940d1281cd4e96b786f8d7ad2b867d174591890 Mon Sep 17 00:00:00 2001 From: Eric Pugh Date: Sat, 8 Jun 2024 07:58:15 -0400 Subject: [PATCH] Update links to point to the correct repos. --- _search-plugins/ubi/data-structures.md | 2 +- _search-plugins/ubi/schemas.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/_search-plugins/ubi/data-structures.md b/_search-plugins/ubi/data-structures.md index e0a7376e2b3..623ef0a539d 100644 --- a/_search-plugins/ubi/data-structures.md +++ b/_search-plugins/ubi/data-structures.md @@ -7,7 +7,7 @@ nav_order: 7 --- # Sample client data structures -The client data structures can be used to create events that follow the [UBI event schema specification](https://github.com/o19s/opensearch-ubi), +The client data structures can be used to create events that follow the [UBI event schema specification](https://github.com/o19s/ubi), which is described in further detail [here]({{site.url}}{{site.baseurl}}/search-plugins/ubi/schemas/). The developer provides an implementation for the following functions: diff --git a/_search-plugins/ubi/schemas.md b/_search-plugins/ubi/schemas.md index d41bddef61f..f3b66eddcab 100644 --- a/_search-plugins/ubi/schemas.md +++ b/_search-plugins/ubi/schemas.md @@ -119,7 +119,7 @@ There are 2 separate stores involed in supporting UBI data collection: ### 1) **UBI queries** All underlying query information and results ([`object_id`](#object_id)'s) are stored in the `ubi_queries` index, and remains largely invisible in the background. -**UBI Queries** [schema](https://github.com/o19s/opensearch-ubi/tree/2.14.0/src/main/resources/queries-mapping.json): +**UBI Queries** [schema](https://github.com/opensearch-project/user-behavior-insights/tree/main/src/main/resources/queries-mapping.json): Since UBI manages the `ubi_queries` index, the developer should never have to write directly to this store (except for importing data). - `timestamp` (events and queries) @@ -138,7 +138,7 @@ Since UBI manages the `ubi_queries` index, the developer should never have to wr ### 2) **UBI events** This is an index called `ubi_events` that the client side directly indexes events to, linking the event [`action_name`](#action_name), [`object_id`](#object_id)'s and [`query_id`](#query_id)'s together with any other important event information. -Since this schema is dynamic, the developer can add any new fields and structures (such as *user* information, *geo-location* information) at index time that are not in the current **UBI Events** [schema](https://github.com/o19s/opensearch-ubi/tree/2.14.0/src/main/resources/events-mapping.json): +Since this schema is dynamic, the developer can add any new fields and structures (such as *user* information, *geo-location* information) at index time that are not in the current **UBI Events** [schema](https://github.com/opensearch-project/user-behavior-insights/tree/main/src/main/resources/events-mapping.json):