Skip to content

DOCS-10600: Tracing API Gateway #28916

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

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open

DOCS-10600: Tracing API Gateway #28916

wants to merge 6 commits into from

Conversation

cswatt
Copy link
Contributor

@cswatt cswatt commented Apr 22, 2025

What does this PR do? What is the motivation?

Merge instructions

Merge readiness:

  • Ready for merge

For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

To have your PR automatically merged after it receives the required reviews, add the following PR comment:

/merge

Additional notes

@cswatt cswatt added the WORK IN PROGRESS No review needed, it's a wip ;) label Apr 22, 2025
@cswatt cswatt requested review from a team as code owners April 22, 2025 19:03
@github-actions github-actions bot added Architecture Everything related to the Doc backend Images Images are added/removed with this PR labels Apr 22, 2025
Copy link
Contributor

Preview links (active after the build_preview check completes)

New or renamed files


#### Supported versions and web frameworks

| Runtime | Datadog Tracer version | Frameworks |
Copy link
Contributor

@nevilgeorge nevilgeorge Apr 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's split Datadog Tracer version into two columns to make it more readable: Datadog tracer and Tracer version.

image

^ doesn't look very nice.


### Prerequisites
- Amazon API Gateway is configured on your environment. Datadog recommends testing on a development environment before releasing to production.
- The API Gateway is using the REST API option (API Gateway V1). The HTTP API (V2) is not supported.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, can we be consistent with V1 and V2?

| Runtime | Datadog Tracer version | Frameworks |
| ------- | -------------- | ---------- |
| Node.js | `dd-trace-js` v[4.50.0][1]+ or v[5.26.0][2]+ | express, fastify, hapi, koa, microgateway-core, next, paperplane, restify, router, apollo |
| Go | `dd-trace-go` v[1.72.1][3]+ | chi.v5 / chi, dimfeld/httptreemux.v5, echo.v4 / echo v4 / echo v3, emicklei/go-restful / go-restful / go-restful.v3, fiber / gofiber/fiber.v2, gin-gonic/gin / Gin, gorilla/mux / Gorilla Mux, julienschmidt/httprouter, valyala/fasthttp.v1, zenazn/goji.v1, 99designs/gqlgen |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This list looks messy because we duplicate info.

Here's a list of just the package names, I think it'll be better to just use that.
chi
httptreemux
echo
go-restful
fiber
gin
gorilla mux
httprouter
fasthttp
goji

(I removed gqlgen because it shouldn't have been on this list.)

Comment on lines 53 to 58
| x-dd-proxy | 'aws-apigateway' |
| x-dd-proxy-request-time-ms | context.requestTimeEpoch |
| x-dd-proxy-domain-name | context.domainName |
| x-dd-proxy-httpmethod | context.httpMethod |
| x-dd-proxy-path | context.path |
| x-dd-proxy-stage | context.stage |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

both header and value should be in markdown code formatting.


---

{{< callout url="#" btn_hidden="false" header="Join the Preview" >}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed over Slack, let's remove this button.

It would still be helpful to indicate this is a preview some way though. In the Google Doc documentation, I've been using the following snippet:

image

Is there a recommended way to indicate a feature is in preview in the official documentation?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Architecture Everything related to the Doc backend Images Images are added/removed with this PR WORK IN PROGRESS No review needed, it's a wip ;)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants