Reorganize event management pages #20401
Merged
Conversation
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
|
Created DOCS-6603 |
drichards-87
requested changes
Nov 2, 2023
|
|
||
| - Normalize disparate sources of events by remapping attributes. For example, use the same reserved [service tags][19] everywhere. | ||
| - Enrich events with external data saved in a [Reference Table][20] (beta). For example, map a service name with your service directory to enrich events with team ownership information, links to dashboards, or links to documentation. | ||
| {{< img src="service_management/events/events_explorer.png" alt="Events explorer display" >}} |
There was a problem hiding this comment.
I noticed that this screenshot has a Datadog employee email in it. I would recommend retaking this screenshot. If you need to, you can change the email displayed in the UI (and make it something generic) using developer tools > Inspect in the browser. Reach out if you need any help doing that.
There was a problem hiding this comment.
I reevaluated whether we need another picture of the Events Explorer and removed. Thanks for catching this!
Co-authored-by: DeForest Richards <[email protected]>
…aDog/documentation into esther/docs-5997-ingest-usage-events
drichards-87
approved these changes
Nov 3, 2023
MaelNamNam
pushed a commit
that referenced
this pull request
Jan 17, 2024
* Add usage and ingest pages to menu work on usage * Rearrange content and image files * Change reference links from other docs * Apply suggestions from code review Co-authored-by: DeForest Richards <[email protected]> * Remove image reference --------- Co-authored-by: DeForest Richards <[email protected]>
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.
What does this PR do? What is the motivation?
Merge instructions