Skip to content
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

Fargate support #15718

Open
johnf opened this issue Mar 17, 2025 · 3 comments
Open

Fargate support #15718

johnf opened this issue Mar 17, 2025 · 3 comments

Comments

@johnf
Copy link

johnf commented Mar 17, 2025

Problem Statement

I recently moved some step function steps from lambda to fargate. When errors occur, I'm missing the nice linkage to cloudwatch, etc.

Solution Brainstorm

I suspect code could be re-used from the lambda integration. If I had more time right now I'd explore it

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Mar 17, 2025
@andreiborza
Copy link
Member

Hi @johnf, thanks for filing this.

Could you elaborate what you'd want to see exactly?

@johnf
Copy link
Author

johnf commented Mar 18, 2025

@andreiborza Below are two sections that I get in Lambda which would be handy in Fargate

Image
This lets me jump straight to the Cloudwatch logs.

Image
The equivalent type of data for the Fargate would be handy. In particular, maybe the arguments to the docker container

Those are the main bits missing.

If you could detect that this was running in a step function and provide the input to the function, that would be amazing. But I'm not sure if that is possible. This would be valuable for Fargate and Lambda.

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Mar 18, 2025
@andreiborza
Copy link
Member

andreiborza commented Mar 18, 2025

Thanks! Hm, these are directly supplied to a lambda function's context but I don't think fargate exposes these as easily. I'm not super familiar with fargate and step functions but from looking around it looks like you'd have to use the aws-sdk to fetch these. Something we're probably unlikely to add.

You could try to do this yourself enhancing events in beforeSend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

3 participants