Logs receiver + exporter
Is your feature request related to a problem? Please describe. Lambda runtime logs received, processed and exported in the same way in which the other telemetry signals, traces & metrics are handled.
Its seems to me that there must be some reasons as to why logs are not being handled currently. I am curious why and if there is no good reason id be very keen to contribute to these ends or enjoy the fruits of others contributions 😄
See below for an example issue currently raised pertaining to this. It seems like in this and indeed in other posts its also surprising to new consumers that its not included within the external extension functionality https://github.com/open-telemetry/opentelemetry-lambda/issues/1618#issuecomment-2527854979
Describe the solution you'd like
- add logs receiver
- add logs exporter
- add documentation to the effect of how to use the sdk to make local network calls in order to send logs produced by the runtime to the external extension to receive, process (I suggest ensuring the semantic convention is met re resource attribution) and ultimately export.
Describe alternatives you've considered I currently lift and shift your code and publish my own layers containing custom collector binaries I manage
Additional context
Could you share your custom otel layer? I'd like to see how it works and maybe create my own custom layer
This isn't open-telemetry, but here's an extension that sends lambda runtime logs to Loki. Hope this helps.
https://github.com/Jaeminst/aws-lambda-loki-extension