Hi, I wonder if anyone tried Signoz with AWS Lambd...
# support
b
Hi, I wonder if anyone tried Signoz with AWS Lambda? The documentation only points logs but not traces. I have faced a problem that I described here, it's not caused because of Signoz, but I wonder if there's any solution I can do on Signoz? Maybe update clickhouse manually to remove missing spans? It seems keeping everything a whole string so not that easy i guess. https://stackoverflow.com/questions/78900023/aws-lambda-open-telemetry-missing-parent-span
s
Maybe update clickhouse manually to remove missing spans?
What do you mean by this? They are missing i.e they don't exist on SigNoz
b
I mean making an update on the database side so it will stop writing missing spans. Also it would have been easier if the documentation included traces. I feel like nobody ever tried sending traces from AWS lambda to Signoz before me, either I'm doing something wrong or I'm the first one ever did this therefore having this undocumented problem.
s
I would recommend fixing the issue at the sending step rather than trying to modify the DB records. Please make sure you call the
flush
on SDK before exiting the lambda https://opentelemetry.io/docs/specs/otel/trace/sdk/#forceflush