### About We lack event instrumentation for when Custom and Foundational Agents are chatted with. ### Problem The first chat hits a backend endpoint we could instrument, but further chats within the session do not - they go directly to a websocket endpoint ([this one](https://gitlab.com/gitlab-org/gitlab/-/blob/76814ca994bfc8e4c9c604a5e9942c4a7b5ffd75/ee/lib/api/ai/duo_workflows/workflows.rb#L363), see [frontend code](https://gitlab.com/gitlab-org/gitlab/-/blob/92836f99cd5462dc3146147023a9b242e8dbef88/ee/app/assets/javascripts/ai/constants.js#L65)). We instrument our flow and external agent execution on the backend, but because we want to record an event per message that goes to the Custom/Foundational agent the frontend is best to instrument it. ### Proposal We should instrument using [the same `trigger_ai_catalog_item` event](https://gitlab.com/gitlab-org/gitlab/-/blob/d498b86403009a64f3ac25f57cffba4992cc2efb/ee/config/events/trigger_ai_catalog_item.yml#L5) that we already use for when [flows are executed](https://gitlab.com/gitlab-org/gitlab/-/blob/54d6969b78f56dcc440131a876fe9f35f78735a8/ee/app/services/ai/catalog/flows/execute_service.rb#L35) on the backend, and external agents are triggered https://gitlab.com/gitlab-org/gitlab/-/issues/558488. This should happen on the ~frontend. Record an event every time the user submits a chat to a custom or foundational agent in Duo Chat. See https://docs.gitlab.com/development/internal_analytics/internal_event_instrumentation/quick_start/ for technical guide Each chat with custom agent: ```javascript this.trackEvent('trigger_ai_catalog_item', { label: "agent", property: "chat", value: item.id }); ``` Each chat with foundational agent: ```javascript this.trackEvent('trigger_ai_catalog_item', { label: "foundational_agent", property: "chat", value: item.id }); ```