Open jhonatanforero opened 3 years ago
Ping @anuraaga @devinsba @jorgheymans
I will change the cron with this https://docs.aws.amazon.com/lambda/latest/dg/with-kinesis.html (event source) It's better.
Hi @anuraaga @devinsba @jorgheymans
Any updates? what do you think about it?
Hi Everyone!
Last year Aws lambda released a new feature -> https://aws.amazon.com/es/blogs/aws/new-for-aws-lambda-container-image-support/
Now, Its support container like docker image inside a lambda , this is a great feature! because we can run a collector from an image docker inside a Lambda.
So, I know you have a collector with docker image , but if we can use that collector inside a lambda, you need to create a function handler -> https://docs.aws.amazon.com/lambda/latest/dg/java-handler.html.
With that change, we can start a collector from a lambda with a cron -> https://docs.aws.amazon.com/lambda/latest/dg/services-cloudwatchevents-expressions.html I mean this is for a lazy scenario. So your client (sqs or Kinesis) will work!.
And we can use zipkin-lens UI with Cloudfront + API GTW for invoke services from the collector. (I need to review the feasible).
This is a hit for serverless projects because we dont want a cluster of Containers in our infra only for tracing about Costs I mean.
Think about that!.
Regards.