Closed adjohn closed 5 years ago
@mrickard this is affecting at least one user contacting support! Thanks!
@mrickard was this resolved with the commit to unpin the sls framework version?
@ewindisch I think so: the two likely culprits were 1) a regression in recent versions of the module (as identified by @adjohn) 2) a default assignment of "id" to the awsRequestId for locally invoked events (as identified by @kolanos)
I pinned the version and assigned a UUID to the request IDs for locally invoked functions, so these two potential causes for non-logging functions were addressed in the merge.
Great if/as this is confirmed we should close the issue! Thanks. I'll communicate to the user I was speaking with and have them upgrade.
Excellent. In my tests I'm getting both local and AWS invocations in a dashboard.
There seems to be a regression with the latest versions of the serverless framework when using
sls invoke local
and IOpipe. There are no errors, but the telemetry is not sent to IOpipe when running invoke local.The workaround is to downgrade serverless framework to version 1.32.0