New Blog Post: Observing Lambdas

[theSuess]

As per submission guidelines, this is a proposal for a blog post with the following outline:

Observing Lambdas

An introduction to the opentelemetry-lambda collector extension layer. It explains how the lambda runtime complicates observability and how the decouple processor helps reduce latency and costs. It also includes instructions on how to use the extension layer to ship logs & traces.

Technologies used are the opentelemetry collector lambda extension layer and an arbitrary OTLP compatible storage solution.
The most relevant SIG for approval is most probably the one around the collector, but a review from the team members listed on the opentelemetry-lambda repo would be more specific.

[svrnm]

thanks @theSuess

@open-telemetry/lambda-extension-approvers @open-telemetry/collector-approvers PTAL, would you sponsor such a blog post?

"an arbitrary OTLP compatible storage solution"

can you be more specific? do you plan to show multiple solutions, only one and if so which ones?

[tylerbenson]

Sounds reasonable to me. No objection assuming it is vendor neutral.

[theSuess]

@svrnm in the draft I prepared, I give instructions for sending them to any OTLP ingestion endpoint using the OTLP exporter. At the end, I plan on showing the logs visualized in Grafana but without going into details regarding storage.

[svrnm]

@svrnm in the draft I prepared, I give instructions for sending them to any OTLP ingestion endpoint using the OTLP exporter. At the end, I plan on showing the logs visualized in Grafana but without going into details regarding storage.

As a piece of advice: you should have said "grafana" in the initial posting vs "an arbitrary OTLP compatible storage solution", as you work as a DevRel for Grafana (and disclose that), as you have an interest here to have grafana promoted. Due to our project's goal of being "vendor neutral" we have to be pedantic on that matter from time to time. Please also review our social media guidelines and our suggestions to prefer CNCF projects over non-CNCF projects in our contributin guidelines for blogs, e.g. if you only talk about traces use Jaeger.

However, since Grafana is open source and current defacto standard for visualization, this should be fine, as long as you leverage the OSS version exclusively.

Please provide a PR for the blog post and we are going to review it.

Thanks

[theSuess]

I've crated the PR as a draft: #5990

Grafana only shows up in an optional screencast at the very end and is not even mentioned by name, which is why I didn't mention it in the original post. The instructional part is completely backend and visualization agnostic.

As Grafana isn't mentioned in the post, I didn't disclose the affiliation in the initial post but will do so in any future contributions.

[svrnm]

I've crated the PR as a draft: #5990

I will take a look.

Grafana only shows up in an optional screencast at the very end and is not even mentioned by name, which is why I didn't mention it in the original post. The instructional part is completely backend and visualization agnostic.

That makes no difference: the video points to the commercial grafana backend, that we can not accept. Someone watching the video is no different to a reader of the text.

As Grafana isn't mentioned in the post, I didn't disclose the affiliation in the initial post but will do so in any future contributions.

Thanks.