[Improve] Track successful Roomote trial inference use - #1785
Draft
roomote-roomote[bot] wants to merge 1 commit into
Draft
[Improve] Track successful Roomote trial inference use#1785roomote-roomote[bot] wants to merge 1 commit into
roomote-roomote[bot] wants to merge 1 commit into
Conversation
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Roomote now emits an anonymous activation event when the managed trial inference gateway receives a successful upstream response to an inference request.
The signal is not emitted for model discovery, provider errors, exhausted credits, or upstream connection failures. Focused gateway coverage pins each of those boundaries.
Why this change was made
The existing setup and task-created milestones stop before the provider handles a model request. That made expected onboarding drop-off indistinguishable from failures between task creation and first inference usage.
Impact
Activation analytics can now distinguish deployments that merely configured trial inference from those that successfully reached managed inference. Runtime inference behavior is unchanged.