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

Show NestJS API endpoints as Resources in the Service Page for an AWS Lambda service #574

Open
bhrutledge opened this issue Sep 13, 2024 · 0 comments

Comments

@bhrutledge
Copy link

Expected Behavior

NestJS endpoints (e.g. GET /users/{id}, POST /users/} appear as Resources in the Service Catalog page

Actual Behavior

On the Service Catalog page, the only Resource that's listed is the Lambda. However, for FastAPI Python applications deployed in a similar manner, the Service Catalog page shows all of the API endpoints as Resources. I noticed that for the FastAPI applications, the "primary operation" is fastapi.request. For the NestJS applications, it's aws.lambda, with no additional option for anything related to NestJS.

I read about "Complex framework usage" in Node.js Compatibility Requirements, but it looks like initializing dd-trace is already done in datadog-lambda-js/src/runtime/module_importer.js

Steps to Reproduce the Problem

My NestJS application is deployed as a Lambda via the AWS CDK. I'm using the Datadog construct from datadog-cdk-constructs. I'm getting traces, logs, and metrics in Datadog.

Specifications

  • Datadog Lambda Layer version: extensionLayerVersion: 62 and nodeLayerVersion: 113
  • Node version:18.x
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

1 participant