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
Hi
we are migrating from v2 to v3.
we have a custom logger that we pass the sdk.
In v2 the logs we got where build by your V2 SDK , and contained among other things the time it took for the request to finish.
Below is an example of log by V2 sdk - see the 0.528 seconds .
[AWS ec2 400 0.528s 0 retries] deleteSecurityGroup({ GroupId: 'sg-079bfdf0d369d0efe' })
In V3 , our logger in called with an object containing clientName, commandName, input , output and metadata. There is no information regarding the time the request took.
This information is critical for us and without this , we will have problems migrating.
Is there anything that can be done to get the request duration.
Thanks.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi
we are migrating from v2 to v3.
we have a custom logger that we pass the sdk.
In v2 the logs we got where build by your V2 SDK , and contained among other things the time it took for the request to finish.
Below is an example of log by V2 sdk - see the 0.528 seconds .
[AWS ec2 400 0.528s 0 retries] deleteSecurityGroup({ GroupId: 'sg-079bfdf0d369d0efe' })
In V3 , our logger in called with an object containing clientName, commandName, input , output and metadata. There is no information regarding the time the request took.
This information is critical for us and without this , we will have problems migrating.
Is there anything that can be done to get the request duration.
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions