[editor] Starting Point for Telemetry #804
Closed
Conversation
This file contains 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
rholinshead
requested review from
saqadri,
suyoglastmileai,
Ankush-lastmile,
jonathanlastmileai and
rossdanlm
as code owners
jonathanlastmileai
approved these changes
Jan 10, 2024
Ankush-lastmile
pushed a commit
that referenced
this pull request
Jan 11, 2024
rebased version #804 onto main
Ankush-lastmile
pushed a commit
that referenced
this pull request
Jan 11, 2024
rebased version of #804 onto main
Ankush-lastmile
pushed a commit
that referenced
this pull request
Jan 13, 2024
rebased version of #804 onto main
|
Closing in favour of #864 |
Ankush-lastmile
pushed a commit
that referenced
this pull request
Jan 14, 2024
rebased version of #804 onto main
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
[editor] Starting Point for Telemetry
Add the required configuration for datadog browser logging to our local editor. Pass this through as logEvent so that other deployments can handle logging of supported events their own way.
Just added a couple event for now & set
logEventin context for use by any component under the EditorContainer.Testing:
DEV:
aiconfig edit --aiconfig-path=python/src/aiconfig/editor/travel.aiconfig.json --server-mode='debug_servers'PROD:
aiconfig edit --aiconfig-path=python/src/aiconfig/editor/travel.aiconfig.json --server-mode='prod'