You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We ran into some issues running tracing-honeycomb on AWS lambda.
Basically we experienced two problems:
Lambda functions resolves once it replies to the requestee, so libhoney would need flush its queued events before a response can be sent. This can take a while and lead to poor performance, as flushing libhoney is not instant.
We ran into some issues running tracing-honeycomb on AWS lambda.
Basically we experienced two problems:
Luckily, Honeycomb provides a layer that fixes this: https://docs.honeycomb.io/getting-data-in/integrations/aws/aws-lambda/
To make it work with tracing-honeycomb, it would need to send its spans to
stdout
instead of a libhoney client.We have been working on a fix that makes the
HoneycombTelemetry
generic over someReporter
, where you can pick either Stdout/Libhoney via a builder.Is this something you would like to see added to this repository?
We would be happy to add our implementation if so.
The text was updated successfully, but these errors were encountered: