Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Way to "connect" UBI events with queries #26

Open
jzonthemtn opened this issue Oct 17, 2024 · 9 comments
Open

Way to "connect" UBI events with queries #26

jzonthemtn opened this issue Oct 17, 2024 · 9 comments
Labels
RFC Request for Comment
Milestone

Comments

@jzonthemtn
Copy link
Collaborator

Right now, we don't have an easy straightforward way to link events and queries. There isn't any "glue" other than the query_id that links the two and this might not be sufficient.

In opensearch-project/user-behavior-insights#34 I want to capture the index(es) that were searched in the UBI queries index, but this might not be appropriate for all use-cases. A more granular approach is likely needed.

We should consider the addition of an application field that both queries and events can use to form this linking. The application can be provided in the query's ext block, and application can be used in the event schema. Having application on both would provide a low-level way to connect queries and events.

@epugh epugh added the RFC Request for Comment label Oct 17, 2024
@epugh
Copy link
Member

epugh commented Oct 17, 2024

FYI: the ext block is the specific way we add UBI to OpenSearch JSON based query DSL .

@epugh
Copy link
Member

epugh commented Oct 23, 2024

Are you suggesting that we should have an explicit application field added to the query_attributes and event_attributes???

I can imagine that you would have a typeahead and a global search, and you would want to distingush between these two sources of queries, when generating personlaization inputs or implicit judgement etc...

Is application the right word? source? origin???

@epugh epugh added this to the 1.2 milestone Oct 23, 2024
@jzonthemtn
Copy link
Collaborator Author

Question for everyone - is application the most appropriate name for the field?

@alexeyrodriguez
Copy link

Something that can help with naming. What are possible values of application? Types of search experience/feature: type-ahead or global-search. Will it also be used to separate multiple shops that an Open Search installation is supporting? The last two types can also mix of course. Any other?

@epugh I suppose you mean adding it to queries, since events already has application.

@wrigleyDan
Copy link

If we already have the application field in the events schema I'd vote for that name.

At least if that does not have any other meaning in the events schema? It feels like a field that should be present for both schemas.

@epugh
Copy link
Member

epugh commented Oct 23, 2024

Thanks for feedback team. I'm going to use application and try to provide some nicer examples in the spec...!

@jzonthemtn
Copy link
Collaborator Author

We should capture application from the ext in queries in the plugin, also. Care to write that issue in the plugin repo?

@epugh
Copy link
Member

epugh commented Oct 23, 2024

image

image

Here is two examples of application being on events and queries.

@epugh
Copy link
Member

epugh commented Oct 23, 2024

We should capture application from the ext in queries in the plugin, also. Care to write that issue in the plugin repo?

opensearch-project/user-behavior-insights#40

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RFC Request for Comment
Projects
None yet
Development

No branches or pull requests

4 participants