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

Authorizer traces not correlated with API gateway traces for Go Lang #543

Open
ranayash45 opened this issue Oct 16, 2024 · 4 comments
Open

Comments

@ranayash45
Copy link

ranayash45 commented Oct 16, 2024

Expected Behaviour

Go Lang Based Custom Authorizer should link trace with Api-Gateway.

Actual Behavior

In current scenario, Trace of authorizer shown separately over data-dog.

Similar Issue:

Link: #252

Steps to Reproduce the Problem

  1. Create Go Lang Custom Authorizer.
  2. Attach to API Gateway, Enable DD Integration of API-Gateway.
  3. Check Service APM of API-Gateway and verify whether trace is linked or not.

Specifications

  • Serverless Framework version: aws-lambda-go v1.47.0, datadog-lambda-go v1.18.0
  • Datadog Serverless Plugin version: Using Lambda Extension version 58.
  • Lambda function runtime (Python 3.7, Node 10, etc.): Go Lang, Rust(Planned for future)

Stacktrace

Paste here
@ranayash45
Copy link
Author

Can someone from Datadog team help in this issue??

@sumedham
Copy link

Hey @ranayash45 - this isn't supported for Go runtimes today. Can you file an FR with the support team so we can keep track of this?

@ranayash45
Copy link
Author

ranayash45 commented Oct 28, 2024

I don't know the exact procedure, can you guide me on same? @sumedham

I just created one more issue with Prefix "FR"
#546

Hope this is what you are asking for.

@sumedham
Copy link

This will have to go through the Datadog Support workflow (found in the bottom left corner of our UI). Let me know if you have any follow-up questions. https://www.datadoghq.com/support/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants