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
Gen 2 onCall handlers don't have traces #1487
Labels
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
ciriousjoker
changed the title
Gen 2 cloud functions don't have traces
Gen 2 onCall handlers don't have traces
Nov 14, 2023
Seeing the same issue, making debugging on stackdriver much more troublesome than V1 functions. |
Thanks for bringing this to our attention, PR is out that wraps onCall handlers with trace context. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related issues
[REQUIRED] Version info
node: v16.19.0
firebase-functions: v4.5.0
firebase-tools: v12.7.0
firebase-admin: v11.11.0
[REQUIRED] Test case
[REQUIRED] Steps to reproduce
[REQUIRED] Expected behavior
Should have a trace.
[REQUIRED] Actual behavior
Doesn't, "same trace" is greyed out.
Were you able to successfully deploy your functions?
Yes, deployment works.
Related:
Reason for this is most likely, that unlike the
onRequest
function, theonCall
handler isn't wrapped inwrapTraceContext()
.The text was updated successfully, but these errors were encountered: