Open patricktyndall opened 1 year ago
I agree, it was very convenient to be able to save a link when calling a lambda, so that later you could quickly find the corresponding log. I also couldn't find a similar feature in either @serverless/sdk or @serverless/aws-lambda-sdk. Could you tell me please how can I get a similar link on the dashboard's page with the current Lamba trace?
+1
+1
Are you certain it's a bug?
Is the issue caused by a plugin?
Are you using the latest v3 release?
Is there an existing issue for this?
Issue description
Hi. Prior to this week's Dashboard release,
context.serverlessSdk.getDashboardUrl()
could be used to get a link to the dashboard for an invocation. Other identifiers were available as well (likegetTransactionId()
).These identifiers are extremely important for correlating errors in lambda to the associated serverless logs. We have now lost this capability. Now that dashboard URLs have changed, these links no longer work (I can't find a similar function in SDK V3).
How can we use the SDK to get an identifier or URL for the trace of a specific invocation?
Service configuration (serverless.yml) content
Command name and used flags
n/a
Command output
Environment information