fix(amazonq): emit sessionDuration #6102
Merged
+7
−0
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.
Premature Builder ID Session Expiration Definition
Problem
In the
Premature Builder ID Session ExpirationCloudwatch graph, we do not have data for JB (either AmazonQForJetbrains or AwsToolkitForJetbrains products).This is because we the EMF metric only gets created when our
credentialStartUrlishttps://view.awsapps.com/startandsessionDuration< 90 days, which means we aren't sending the correct data from the clientSolution
Emit
sessionDurationfieldTesting
Ran in sandbox and emit data to kibana. This is somewhat experimental, as I'm not able to fully replicate this scenario, but at least we can see what data we get in cloudwatch now after emitting this new field
