feat(specs): add draft schema for Agentic Analytics#6167
feat(specs): add draft schema for Agentic Analytics#6167
Conversation
Co-Authored-By: Claude Opus 4.6 <[email protected]>
✔️ Code generated!
📊 Benchmark resultsBenchmarks performed on the method using a mock server, the results might not reflect the real-world performance.
|
specs/bundled/insights.yml
Outdated
| sessionID: | ||
| $ref: '#/components/schemas/sessionID' | ||
| index: | ||
| $ref: '#/components/schemas/index' |
There was a problem hiding this comment.
if possible please remove the index here?
typically an event may use multiple indices.
There was a problem hiding this comment.
this is an artefact from the bundling process which seems a bit broken. I'll see if I can put a PR in to fix this. In the mean time please could you review the source files /specs/insights (I mentioned this in the PR description but it may not have been clear).
| - agentID | ||
| - messageID | ||
| - toolCallID | ||
| - conversationID |
There was a problem hiding this comment.
this cannot work for us infortunately because events with only messageID should remain valid.
There was a problem hiding this comment.
No problem. How about we make messageID required?
There was a problem hiding this comment.
Also please could you give us some more context about the use of messageID and conversationID?
Also a bit more context about when toolCallID and agentID would and wouldn't be used.
For example, I'd understood that a message was always part of a conversation.
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
…com:algolia/api-clients-automation into vnts-121-draft-schema-for-agentic-analytics
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
3 participants
DO NOT MERGE - FOR DISCUSSION ONLY
JIRA Ticket: https://algolia.atlassian.net/browse/VNTS-136
This PR is provided for discussion purposes to capture Agentic Analytics requirements extensions to the insights API event schema.
It should not introduce any breaking changes but before publishing publicly we will treat the extensions as internal until testing has been completed.
Bundlers and linters tend to introduce whitespace changes so I recommend viewing changes with 'View Whitespace' turned off in settings.
Please comment on the source docs in
specs/insights/rather than the bundled specs.To view the resulting API in swagger doc, pull this branch then:
Start server:
Open browser to view UI docs at http://localhost:8080
Stop: