-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[SHEETS-2095] Add new data sources in Sheets public documentation #31309
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
[SHEETS-2095] Add new data sources in Sheets public documentation #31309
Conversation
Preview links (active after the
|
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.
this looks good, thanks for your PR! may I suggest alphabetizing this list for scannability now or in the future?
Thanks, updated in e0bf294 |
content/en/sheets/_index.md
Outdated
@@ -71,12 +71,20 @@ Create tables and analyze the data pulled from the following data sources: | |||
|
|||
| Data Source | Product page | | |||
| -------------------- | ----------- | | |||
| APM Spans | [APM Explorer][18] | | |||
| Audit Events | [Audit Trail][15] | |
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.
The product page is called Audit Trail
and the Sheets UI says Audit Trail
too -- could we use that data source name here too, instead of Audit Events
?
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.
Done in e7d0f29
/merge |
View all feedbacks in Devflow UI.
Added to the queue but the mergequeue is not enabled for now.
This pull request was merged directly. |
…1309) * [SHEETS-2095] Add new data sources in Sheets public documentation * Order the data sources list in alphabetical order in Sheets * [SHEETS-2095] Replace Audit Events by Audit Trail
What does this PR do? What is the motivation?
We added new data sources to the Sheets product so we want to update the public documentation accordingly.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>
convention and include the forward slash (/
). Without this format, your pull request will not pass 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.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes