-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable tracing from Step Functions to flow to Open Telemetry Collector #588
Comments
Hi, probably similar issue aws-observability/aws-otel-collector#1845 (comment). Did you manage to find a workaround? |
No, we put our open telemetry effort on hold for now, with this being a major blocker. |
We would like to try again to use Open Telemetry but now Step Functions are core to our system and would need a solution to have Step Function actions flow into Open Telemetry traces. Has there been any effort to include mechanisms so Step Functions are part of OTel traces? |
Have the same problem. @rberger have you found a way forward yet? |
Nope, we still can't really use Open Telemetry due to this as Step Functions are core to our entire infrastructure. We are kind of using X-Ray |
As far as I can tell, there does not seem to be a way to have Step Functions participate in an Open Telemetry Trace. We are adopting Step Functions very heavily now and also adopting Open Telemetry. Had expected that there would be a way for Step Functions to send trace data to Open Telemetry, but it seems it can only send to X-Ray.
Is there a way to have that Step Function trace info be sent to Open Telemetry? If not, is there maybe a way to have the Step Function X-Ray traces sent to Open Telemetry?
The text was updated successfully, but these errors were encountered: