what's a canonical way folks have got their lambda...
# general
i
what's a canonical way folks have got their lambda logs into signoz? also, what's recommendation? thankyou
p
@nitya-signoz should have more insights on this
i
thanks Pranay
i've got zapped log fields all ready to go from lambda with otelcol-contrib collector layer with signoz collector on k8s ready to rendezvous from lambda subnet (AWS)
n
Don’t have suggestions as of now, but from what I understand from the above statements you have already got it working right? You just want to know what can be other ways to achieve the same/best practices?
i
well, essentially yes. imagine greenfield lambda loggin to its stdout/stderr as per usual and now need to land those logs to signoz otel log collector. what's the best practices? there are tons of good documentation on non-lambda in the signoz.io website but couldn't find much on lambda based deployments 🙂
s
AWS maintains a lambda extension to make working with opentelemetry easy https://github.com/open-telemetry/opentelemetry-lambda. I didn’t try it myself, but I have seen people use it to send traces/metrics/logs to another vendor. You may want to give it a look.
i
thanks
So, a current interim solution that Nitya pointed out a week ago (thanks Nitya) is to use
filelog
receiver (we built custom lambda extension based on
opentelemetry-lambda
with
filelog
receiver). that receiver then hands off log (with traces as zap fields) to otlp exporter. lambda->/tmp/app.log->filelogreceiver->otlpexporter->signoz. this has worked so far.
until Go client library+sdk supports logging signal out of the box, this interim solution works for us.
/tmp
is recommended in lambda because AWS says it can scale from 512Mb to 10G.
(enough for us)
n
Interesting, thanks for sharing this. @Ashu I think we can create a blog/tutorial with inputs from Ishwor on collecting AWS lambda logs.
a
Thanks @nitya-signoz , that would be great. Let me reach out to @Ishwor Gurung with some plans for that.
102 Views