You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
telemetry(amazonq): Add telemetry tracing for amazon q inline (aws#5655)
## Problem
- The flow from when a message is shown to the user and
rejected/accepted by the user isn't instrumented with any way to trace
events
## Solution
- Create a trace from when the event is shown (either by manual
invocation or auto trigger) and then connect all the telemetry events
through a traceId.
### Implementation details
- The traceId is initially created when manual invocation/auto trigger
occurs
- For every telemetry event thats in the function hierarchy of the
manual invocation/auto trigger, they automatically assume the same
traceId
- When an event listener is called it uses the traceId we've set in
TelemetryHelper to setup the next traceId. This is because the event no
longer belongs to the same context
- Inside of commands we use `telemetry.record` because it allows us to
override the default telemetry id that gets automatically created and
instead associate it with the known trace
@@ -68,99 +74,107 @@ export class RecommendationService {
68
74
return
69
75
}
70
76
71
-
if(isCloud9('any')){
72
-
// C9 manual trigger key alt/option + C is ALWAYS enabled because the VSC version C9 is on doesn't support setContextKey which is used for CODEWHISPERER_ENABLED
73
-
// therefore we need a connection check if there is ANY connection(regardless of the connection's state) connected to CodeWhisperer on C9
// C9 manual trigger key alt/option + C is ALWAYS enabled because the VSC version C9 is on doesn't support setContextKey which is used for CODEWHISPERER_ENABLED
86
+
// therefore we need a connection check if there is ANY connection(regardless of the connection's state) connected to CodeWhisperer on C9
0 commit comments