crates-io: Forward index.crates.io request logs to Datadog#1079
Open
Turbo87 wants to merge 1 commit into
Open
Conversation
Mirror the webapp service's Datadog logging on the index Fastly service, reusing the existing per-environment datadog-token SSM parameter. The existing S3 request logging is left in place.
356b7d8 to
2d08250
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a
logging_datadogblock to theindex.crates.ioFastly service so its request logs reach Datadog, the same way the webapp and static services already do.The block reuses the existing module-scoped
datadog-tokenSSM parameter, so I think no new credentials should be needed. The existing S3 request logging (/fastly-requests/index.crates.io/) is left untouched and keeps flowing alongside the new Datadog stream./cc @rust-lang/infra