-
Notifications
You must be signed in to change notification settings - Fork 1.2k
feat: Serverless Google Cloud Run docs first draft #29481
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
feat: Serverless Google Cloud Run docs first draft #29481
Conversation
f6c0f17 to
52b730e
Compare
|
|
||
| ### Sidecar vs. In-Process Instrumentation for Google Cloud Run | ||
|
|
||
| A discussion of the tradeoffs between instrumenting Google Cloud Run services with a sidecar vs. in-process. Touch on cost things, performance, and decoupling your application from the Datadog tooling. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we'll do this in a future PR. i'd like to get some actual numbers for this if possible.
|
|
||
| The `DD_LOGS_ENABLED` environment variable is not required. | ||
|
|
||
| TODO: write something about `DD_SOURCE`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we'll do this in a future pr. this has to do with our logs pipelines and logs/trace correlation.
…least profiling works
020bcbb
into
aleksandr.pasechnik/serverless-gcp-docs-refresh
Merge instructions
We are building this on top of our long-lived branch which is tracked here: #29407
Merge readiness:
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:
Additional notes