From 62dca25f4c10525f2276d99eda85cd450af49ef7 Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Mon, 15 Jun 2026 14:48:46 -0400 Subject: [PATCH 1/3] Move Events images from service_management/ to events/ Relocates static/images/service_management/events/ to static/images/events/ and updates all markdown references across 42 files to match. Co-Authored-By: Claude Sonnet 4.6 --- content/en/events/_index.md | 2 +- content/en/events/correlation/_index.md | 2 +- content/en/events/correlation/analytics.md | 6 +++--- content/en/events/correlation/configuration.md | 8 ++++---- content/en/events/correlation/intelligent.md | 8 ++++---- .../en/events/correlation/maintenance_windows.md | 2 +- content/en/events/correlation/patterns.md | 8 ++++---- content/en/events/correlation/triage_and_notify.md | 6 +++--- content/en/events/explorer/_index.md | 2 +- content/en/events/explorer/analytics.md | 8 ++++---- content/en/events/explorer/facets.md | 4 ++-- content/en/events/explorer/navigate.md | 4 ++-- .../guides/migrating_to_new_events_features.md | 8 ++++---- content/en/events/guides/usage.md | 6 +++--- .../events/pipelines_and_processors/grok_parser.md | 2 +- content/en/events/triage_inbox.md | 4 ++-- content/en/extend/_index.md | 2 +- content/en/extend/integrations/agent_integration.md | 2 +- .../glossary/terms/processing_pipeline_(Events).md | 2 +- content/en/metrics/guide/rate-limit.md | 2 +- content/en/monitors/status/events.md | 2 +- .../events/correlation/case_analytics.png | Bin .../events/correlation/correlation_helper.mp4 | Bin .../events/correlation/event_analytics.png | Bin .../events/correlation/event_management.png | Bin .../correlation/intelligent/intelligent_config.png | Bin .../intelligent/intelligent_config_updated.png | Bin .../intelligent/intelligent_correlation.png | Bin .../correlation/intelligent/intelligent_project.png | Bin .../correlation/pattern/preview_pattern_output.png | Bin .../pattern/recommended_patterns_preview.png | Bin .../triage/event_management_case_detail.png | Bin .../events/correlation/triage/triage.png | Bin .../events/events-analytics.png | Bin .../events/events-explorer.mp4 | Bin .../events/explorer/display-values.png | Bin .../events/explorer/event-attribute.png | Bin .../events/explorer/events-overview.png | Bin .../events/explorer/facet-to-graph.png | Bin .../events/explorer/facets-location.png | Bin .../events/explorer/navigate.png | Bin .../events/explorer/split-graph.png | Bin .../events/explorer/time-interval.png | Bin .../events/graph-events.png | Bin .../{service_management => }/events/grok-parser.png | Bin .../events/guides/events-migration-monitor-new.png | Bin .../events/guides/usage/event_overlays.png | Bin .../events/guides/usage/events-dashboard.mp4 | Bin .../events/guides/usage/generate-metrics.png | Bin .../events/triage_inbox/event_mgmt_inbox.mp4 | Bin .../event_mgmt_inbox_right_hand_panel.png | Bin 51 files changed, 45 insertions(+), 45 deletions(-) rename static/images/{service_management => }/events/correlation/case_analytics.png (100%) rename static/images/{service_management => }/events/correlation/correlation_helper.mp4 (100%) rename static/images/{service_management => }/events/correlation/event_analytics.png (100%) rename static/images/{service_management => }/events/correlation/event_management.png (100%) rename static/images/{service_management => }/events/correlation/intelligent/intelligent_config.png (100%) rename static/images/{service_management => }/events/correlation/intelligent/intelligent_config_updated.png (100%) rename static/images/{service_management => }/events/correlation/intelligent/intelligent_correlation.png (100%) rename static/images/{service_management => }/events/correlation/intelligent/intelligent_project.png (100%) rename static/images/{service_management => }/events/correlation/pattern/preview_pattern_output.png (100%) rename static/images/{service_management => }/events/correlation/pattern/recommended_patterns_preview.png (100%) rename static/images/{service_management => }/events/correlation/triage/event_management_case_detail.png (100%) rename static/images/{service_management => }/events/correlation/triage/triage.png (100%) rename static/images/{service_management => }/events/events-analytics.png (100%) rename static/images/{service_management => }/events/events-explorer.mp4 (100%) rename static/images/{service_management => }/events/explorer/display-values.png (100%) rename static/images/{service_management => }/events/explorer/event-attribute.png (100%) rename static/images/{service_management => }/events/explorer/events-overview.png (100%) rename static/images/{service_management => }/events/explorer/facet-to-graph.png (100%) rename static/images/{service_management => }/events/explorer/facets-location.png (100%) rename static/images/{service_management => }/events/explorer/navigate.png (100%) rename static/images/{service_management => }/events/explorer/split-graph.png (100%) rename static/images/{service_management => }/events/explorer/time-interval.png (100%) rename static/images/{service_management => }/events/graph-events.png (100%) rename static/images/{service_management => }/events/grok-parser.png (100%) rename static/images/{service_management => }/events/guides/events-migration-monitor-new.png (100%) rename static/images/{service_management => }/events/guides/usage/event_overlays.png (100%) rename static/images/{service_management => }/events/guides/usage/events-dashboard.mp4 (100%) rename static/images/{service_management => }/events/guides/usage/generate-metrics.png (100%) rename static/images/{service_management => }/events/triage_inbox/event_mgmt_inbox.mp4 (100%) rename static/images/{service_management => }/events/triage_inbox/event_mgmt_inbox_right_hand_panel.png (100%) diff --git a/content/en/events/_index.md b/content/en/events/_index.md index a5fd694c356..e4b9b3542b0 100644 --- a/content/en/events/_index.md +++ b/content/en/events/_index.md @@ -25,7 +25,7 @@ further_reading: text: "Ensure high service availability with Datadog Service Management" --- -{{< img src="service_management/events/correlation/event_management.png" alt="what is event management" style="width:100%;" >}} +{{< img src="events/correlation/event_management.png" alt="what is event management" style="width:100%;" >}} ## Overview diff --git a/content/en/events/correlation/_index.md b/content/en/events/correlation/_index.md index 434f689adb9..5304106afc9 100644 --- a/content/en/events/correlation/_index.md +++ b/content/en/events/correlation/_index.md @@ -4,7 +4,7 @@ aliases: - /service_management/events/correlation/ disable_toc: false further_reading: -- link: "service_management/events/" +- link: "events/" tag: "Documentation" text: "Event Management" - link: "/incident_response/case_management/" diff --git a/content/en/events/correlation/analytics.md b/content/en/events/correlation/analytics.md index 72384264acd..4f3d42101bd 100644 --- a/content/en/events/correlation/analytics.md +++ b/content/en/events/correlation/analytics.md @@ -3,7 +3,7 @@ title: Analytics from Cases and Events aliases: - /service_management/events/correlation/analytics/ further_reading: -- link: "service_management/events/correlation/" +- link: "events/correlation/" tag: "Documentation" text: "Learn about Event Correlation" --- @@ -15,7 +15,7 @@ Keep track of your teams' workload by charting and creating dashboards for event ## Case Metrics -{{< img src="service_management/events/correlation/case_analytics.png" alt="Configure case analytics" style="width:100%;" >}} +{{< img src="events/correlation/case_analytics.png" alt="Configure case analytics" style="width:100%;" >}} You can query Case analytics in a variety of graph widgets to analyze team productivity and identify patterns in issues. Display analytic graphs on both Dashboards and Notebooks. To get started, in the widget configuration, select {{< ui >}}Cases{{< /ui >}} in the data source dropdown under the *Graph your data* section. @@ -36,7 +36,7 @@ The following widgets support Case Analytics: Break down event metrics by source, host, service, and more. Find out where your problematic alerts are coming from and learn if your operational load is increasing or decreasing over time. -{{< img src="service_management/events/correlation/event_analytics.png" alt="Configure event analytics" style="width:100%;" >}} +{{< img src="events/correlation/event_analytics.png" alt="Configure event analytics" style="width:100%;" >}} To get started, in the widget configuration, select {{< ui >}}Events{{< /ui >}} in the data source dropdown under the *Graph your data* section. diff --git a/content/en/events/correlation/configuration.md b/content/en/events/correlation/configuration.md index a3959a4a178..d8a922a9063 100644 --- a/content/en/events/correlation/configuration.md +++ b/content/en/events/correlation/configuration.md @@ -3,10 +3,10 @@ title: Configuration aliases: - /service_management/events/correlation/configuration/ further_reading: -- link: "service_management/events/correlation/triage_and_notify" +- link: "events/correlation/triage_and_notify" tag: "Documentation" text: "Learn about triaging and notifiying on cases" -- link: "service_management/events/correlation/analytics" +- link: "events/correlation/analytics" tag: "Documentation" text: "Analytics on cases" --- @@ -22,8 +22,8 @@ There are two types of correlations: ### Configure Correlation {{< whatsnext desc=" " >}} - {{< nextlink href="service_management/events/correlation/patterns" >}}Pattern-based correlation{{< /nextlink >}} - {{< nextlink href="service_management/events/correlation/intelligent" >}}Intelligent correlation{{< /nextlink >}} + {{< nextlink href="events/correlation/patterns" >}}Pattern-based correlation{{< /nextlink >}} + {{< nextlink href="events/correlation/intelligent" >}}Intelligent correlation{{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/en/events/correlation/intelligent.md b/content/en/events/correlation/intelligent.md index c890c1750c4..a64e4a37e97 100644 --- a/content/en/events/correlation/intelligent.md +++ b/content/en/events/correlation/intelligent.md @@ -3,7 +3,7 @@ title: Intelligent Correlation aliases: - /service_management/events/correlation/intelligent/ further_reading: -- link: "service_management/events/correlation/triage_and_notify" +- link: "events/correlation/triage_and_notify" tag: "Documentation" text: "Learn about triaging and notifiying on cases" --- @@ -18,17 +18,17 @@ To get started: 1. From there you can preview the intelligent correlations that are created from your organization. -{{< img src="service_management/events/correlation/intelligent/intelligent_config_updated.png" alt="Configure intelligent correlation" style="width:100%;" >}} +{{< img src="events/correlation/intelligent/intelligent_config_updated.png" alt="Configure intelligent correlation" style="width:100%;" >}} ## Receiving your first case -{{< img src="service_management/events/correlation/intelligent/intelligent_project.png" alt="Event Management - Intelligent Correlation" style="width:100%;" >}} +{{< img src="events/correlation/intelligent/intelligent_project.png" alt="Event Management - Intelligent Correlation" style="width:100%;" >}} When you navigate to [Event Correlations][3], find a project called {{< ui >}}Intelligent Correlation{{< /ui >}}. From this project, you can see the cases created by Intelligent Correlation. Intelligent Correlation generates cases automatically after it finds related alerts: -{{< img src="service_management/events/correlation/intelligent/intelligent_correlation.png" alt="Case detail page of case created from intelligent correlation, showing related alerts in the Investigation tab" style="width:100%;" >}} +{{< img src="events/correlation/intelligent/intelligent_correlation.png" alt="Case detail page of case created from intelligent correlation, showing related alerts in the Investigation tab" style="width:100%;" >}} diff --git a/content/en/events/correlation/maintenance_windows.md b/content/en/events/correlation/maintenance_windows.md index 672323a9ff7..9667fc67205 100644 --- a/content/en/events/correlation/maintenance_windows.md +++ b/content/en/events/correlation/maintenance_windows.md @@ -3,7 +3,7 @@ title: Maintenance Windows aliases: - /service_management/events/correlation/maintenance_windows/ further_reading: -- link: "service_management/events/correlation/" +- link: "events/correlation/" tag: "Documentation" text: "Learn about Event Correlation" --- diff --git a/content/en/events/correlation/patterns.md b/content/en/events/correlation/patterns.md index 2cad66422f5..325eb4a9873 100644 --- a/content/en/events/correlation/patterns.md +++ b/content/en/events/correlation/patterns.md @@ -3,7 +3,7 @@ title: Pattern-based Correlation aliases: - /service_management/events/correlation/patterns/ further_reading: -- link: "service_management/events/correlation/triage_and_notify" +- link: "events/correlation/triage_and_notify" tag: "Documentation" text: "Learn about triaging and notifiying on cases" --- @@ -14,7 +14,7 @@ Pattern-based correlation allows you to control how the events are correlated. D To get you started, Datadog automatically suggests [pattern-based correlations][1] according to your environment. Click any of the recommendations to open the configuration for the recommended pattern. Configuration fields are pre-populated. -{{< img src="service_management/events/correlation/pattern/recommended_patterns_preview.png" alt="Correlation recommended patterns with the preview panel showing potential cases the pattern would create" style="width:100%;" >}} +{{< img src="events/correlation/pattern/recommended_patterns_preview.png" alt="Correlation recommended patterns with the preview panel showing potential cases the pattern would create" style="width:100%;" >}} ## Create a pattern @@ -25,7 +25,7 @@ To create a pattern: 1. You can adjust a suggested pattern by clicking {{< ui >}}+ Continue With Pattern{{< /ui >}}. This takes you to the pre-populated configuration page for additional tuning. Or, you can choose to create your own pattern by clicking {{< ui >}}+ Personalize From Scratch{{< /ui >}} First, events are deduplicated to alert based on event aggregation key. Then, alerts are correlated to a case based on configuration. -{{< img src="service_management/events/correlation/correlation_helper.mp4" alt="When events matches defined sources, filter, they get deduplicated to alerts. Alerts are correlated based on grouping attributes, and its events are de-duplicated withint the defined time window before the process repeats in a new case. You can modify these configuration in settings" video=true >}} +{{< img src="events/correlation/correlation_helper.mp4" alt="When events matches defined sources, filter, they get deduplicated to alerts. Alerts are correlated based on grouping attributes, and its events are de-duplicated withint the defined time window before the process repeats in a new case. You can modify these configuration in settings" video=true >}} For more information on how to sends events with aggregation key, see [send events to datadog][5]. Events without an aggregation key are deduped to one single alert within the timeframe. ### Suggested patterns @@ -69,7 +69,7 @@ Preview the possible patterns and cases your configuration would potentially cre Use this data to preview the impact of your correlations and understand the expected output of a pattern. -{{< img src="service_management/events/correlation/pattern/preview_pattern_output.png" alt="Configuration for pattern-based correlation highlighting the preview panel; panel shows the number of ingested events that match your configuration, how many of those events alert, how much deduplication would occur, and the number of cases that would result." style="width:100%;" >}} +{{< img src="events/correlation/pattern/preview_pattern_output.png" alt="Configuration for pattern-based correlation highlighting the preview panel; panel shows the number of ingested events that match your configuration, how many of those events alert, how much deduplication would occur, and the number of cases that would result." style="width:100%;" >}} **Notes**: the default title in the preview case is the first alert in correlation. After you save a pattern, the event management case title is intelligently generated. diff --git a/content/en/events/correlation/triage_and_notify.md b/content/en/events/correlation/triage_and_notify.md index 48346f63156..86d9aee42bb 100644 --- a/content/en/events/correlation/triage_and_notify.md +++ b/content/en/events/correlation/triage_and_notify.md @@ -3,12 +3,12 @@ title: Triage and Notify aliases: - /service_management/events/correlation/triage_and_notify/ further_reading: -- link: "service_management/events/correlation/" +- link: "events/correlation/" tag: "Documentation" text: "Learn about Event Correlation" --- -{{< img src="service_management/events/correlation/triage/triage.png" alt="Case detail page with an event side panel. Investigate correlated events from a case and analyze related metrics" style="width:100%;" >}} +{{< img src="events/correlation/triage/triage.png" alt="Case detail page with an event side panel. Investigate correlated events from a case and analyze related metrics" style="width:100%;" >}} Event Management correlates related events and automatically consolidates them into a single case. Bring in all the context of related logs, related metrics, and alerting monitors to triage and troubleshoot issues in one place. @@ -16,7 +16,7 @@ From the [Correlation][1] page, find the pattern you want to analyze and click { ## Event Management Case -{{< img src="service_management/events/correlation/triage/event_management_case_detail.png" alt="Case detail page - Overview" style="width:100%;" >}} +{{< img src="events/correlation/triage/event_management_case_detail.png" alt="Case detail page - Overview" style="width:100%;" >}} | Feature | Description | diff --git a/content/en/events/explorer/_index.md b/content/en/events/explorer/_index.md index f84743b0c0c..8d1ab791962 100644 --- a/content/en/events/explorer/_index.md +++ b/content/en/events/explorer/_index.md @@ -13,7 +13,7 @@ further_reading: text: "Troubleshoot faster with improved Datadog Events" --- -{{< img src="service_management/events/events-explorer.mp4" alt="Sorting events by attributes and exploring analytics" video=true >}} +{{< img src="events/events-explorer.mp4" alt="Sorting events by attributes and exploring analytics" video=true >}} Use the Events Explorer to aggregate and view events coming into Datadog. Group or filter events by attribute and graphically represent them with event analytics. Use the query syntax to filter events using Boolean and wildcard operators. diff --git a/content/en/events/explorer/analytics.md b/content/en/events/explorer/analytics.md index 6c0a8f58072..152d9bca2fc 100644 --- a/content/en/events/explorer/analytics.md +++ b/content/en/events/explorer/analytics.md @@ -27,13 +27,13 @@ You can export analytics visualizations to create widgets in a dashboard or note Use the query to control what's displayed in your Events Analytics: 1. Choose an attribute or tag to graph, and add it as a facet. Graphing a facet displays the unique count of the variable. - {{< img src="service_management/events/explorer/facet-to-graph.png" alt="Shows the list of facets that can be graphed." style="width:100%;" >}} + {{< img src="events/explorer/facet-to-graph.png" alt="Shows the list of facets that can be graphed." style="width:100%;" >}} 2. Use a facet to group your graph by. You must add an attribute as a facet to be able to use it here. - {{< img src="service_management/events/explorer/split-graph.png" alt="Shows the list of facets that you can group data by." style="width:100%;" >}} + {{< img src="events/explorer/split-graph.png" alt="Shows the list of facets that you can group data by." style="width:100%;" >}} 3. Choose the time interval for your graph. Changing the global timeframe changes the list of available timestep values. You can display the results as a timeseries, table, or top list. - {{< img src="service_management/events/explorer/time-interval.png" alt="Shows the list of possible time intervals, including the default, 5 seconds." style="width:100%;" >}} + {{< img src="events/explorer/time-interval.png" alt="Shows the list of possible time intervals, including the default, 5 seconds." style="width:100%;" >}} 4. Choose to display either the top or bottom values according to the selected measure. - {{< img src="service_management/events/explorer/display-values.png" alt="Choose to display the values from the top or from the bottom." style="width:100%;" >}} + {{< img src="events/explorer/display-values.png" alt="Choose to display the values from the top or from the bottom." style="width:100%;" >}} ## Further reading diff --git a/content/en/events/explorer/facets.md b/content/en/events/explorer/facets.md index 7dc73a0a89c..b0532d4eb8b 100644 --- a/content/en/events/explorer/facets.md +++ b/content/en/events/explorer/facets.md @@ -3,7 +3,7 @@ title: Facets aliases: - /service_management/events/explorer/facets/ further_reading: -- link: "service_management/events/explorer/attributes" +- link: "events/explorer/attributes" tag: "Documentation" text: "Learn about reserved attributes" --- @@ -14,7 +14,7 @@ By default, Datadog indexes event attributes as facets. Facets are accessible fr A facet displays the distinct members of an attribute or a tag and provides basic analytics, such as the number of events represented. Facets allow you to pivot or filter your datasets based on a given attribute. To filter, select the values that you want to see. -{{< img src="service_management/events/explorer/facets-location.png" alt="Facets side-panel" style="width:100%;" >}} +{{< img src="events/explorer/facets-location.png" alt="Facets side-panel" style="width:100%;" >}} ### Create a facet diff --git a/content/en/events/explorer/navigate.md b/content/en/events/explorer/navigate.md index 2400cad19f4..0ede4e9217d 100644 --- a/content/en/events/explorer/navigate.md +++ b/content/en/events/explorer/navigate.md @@ -4,7 +4,7 @@ aliases: - /service_management/events/explorer/navigate/ --- -{{< img src="service_management/events/explorer/navigate.png" alt="How to navigate the Events Explorer" style="width:100%;" >}} +{{< img src="events/explorer/navigate.png" alt="How to navigate the Events Explorer" style="width:100%;" >}} ## Overview @@ -16,7 +16,7 @@ Click any event in the Events Explorer to open the event side panel, which shows ### Attributes tab -{{< img src="service_management/events/explorer/event-attribute.png" alt="An example Event Attributes tab" style="width:100%;" >}} +{{< img src="events/explorer/event-attribute.png" alt="An example Event Attributes tab" style="width:100%;" >}} The {{< ui >}}Attributes{{< /ui >}} tab of the side panel lists event attributes as JSON. Click an attribute to add it to or exclude it from the existing query, or to add a column for this attribute. diff --git a/content/en/events/guides/migrating_to_new_events_features.md b/content/en/events/guides/migrating_to_new_events_features.md index fc250059f50..71572bfd367 100644 --- a/content/en/events/guides/migrating_to_new_events_features.md +++ b/content/en/events/guides/migrating_to_new_events_features.md @@ -44,18 +44,18 @@ The Events Explorer displays the most recent events generated by your infrastruc ### Event Analytics -{{< img src="service_management/events/events-analytics.png" alt="Events Analytics display filtered by 'source:cloudtrail'" >}} +{{< img src="events/events-analytics.png" alt="Events Analytics display filtered by 'source:cloudtrail'" >}} In addition to viewing and searching events in the Explorer, you can now graph as a timeseries, top list or table and group the number of events for a given query. See [Event Analytics][2] to learn more. You may also [generate metrics][3] with 15-month retention from any event search query to create monitors and alerts based on historical events. -{{< img src="service_management/events/generate-metrics.png" alt="Image of metrics with the events search query." >}} +{{< img src="events/generate-metrics.png" alt="Image of metrics with the events search query." >}} ### Graph events in dashboards -{{< img src="service_management/events/graph-events.png" alt="Events Analytics">}} +{{< img src="events/graph-events.png" alt="Events Analytics">}} You can now graph events for a given query inside your dashboards as a timeseries graph, query value, top list, table and more. @@ -67,7 +67,7 @@ Event monitors have been ported to use the same standardized set of features as When you create event monitors, the new query search field uses autocomplete, rather than the legacy fill-in-the-blank query. -{{< img src="service_management/events/guides/events-migration-monitor-new.png" alt="New UI for monitor query syntax" style="width:100%;" >}} +{{< img src="events/guides/events-migration-monitor-new.png" alt="New UI for monitor query syntax" style="width:100%;" >}} The new query search allows you to use complex queries in event monitors with new capabilities such as Boolean operators or wildcards. diff --git a/content/en/events/guides/usage.md b/content/en/events/guides/usage.md index e8ca67c5632..bdb0e9340ad 100644 --- a/content/en/events/guides/usage.md +++ b/content/en/events/guides/usage.md @@ -16,7 +16,7 @@ further_reading: [Generate metrics][5] with 15-month retention from any event search query to create and monitor historical events and alerts. Events ingested with a timestamp within the past 20 minutes are considered for aggregation. For more information, see [Event Analytics][6]. -{{< img src="service_management/events/guides/usage/generate-metrics.png" alt="Image of metrics with the events search query." >}} +{{< img src="events/guides/usage/generate-metrics.png" alt="Image of metrics with the events search query." >}} ## Examples of what to do with events @@ -26,13 +26,13 @@ Use the [Events Explorer][7] to aggregate and view events coming into Datadog. G ### Dashboards -{{< img src="service_management/events/guides/usage/events-dashboard.mp4" alt="A graph widget that uses events as the source" video=true >}} +{{< img src="events/guides/usage/events-dashboard.mp4" alt="A graph widget that uses events as the source" video=true >}} You can use events as a data source in [graph widgets][8] to build timeseries, tables, and top list widgets of your event search queries. For example, the [Monitor Notifications Overview][9] dashboard analyzes monitor alert event trends to help you improve your configuration and reduce alert fatigue. #### Overlays -{{< img src="service_management/events/guides/usage/event_overlays.png" alt="Option to view event overlays on an example dashboard" style="width:100%;" >}} +{{< img src="events/guides/usage/event_overlays.png" alt="Option to view event overlays on an example dashboard" style="width:100%;" >}} Overlays visualize corresponding events on top of your graphs. Use the Dashboard [Event Overlays][10] feature to identify when a recent change is causing performance issues within your application or services and find the source of the problem. diff --git a/content/en/events/pipelines_and_processors/grok_parser.md b/content/en/events/pipelines_and_processors/grok_parser.md index f1ae1ea14c7..03bcbff1c36 100644 --- a/content/en/events/pipelines_and_processors/grok_parser.md +++ b/content/en/events/pipelines_and_processors/grok_parser.md @@ -10,7 +10,7 @@ description: Create custom grok rules to parse the full message or specific attr Create custom grok rules to parse the full message or a specific attribute of your raw event. As a best practice, it is recommended to use at most 10 parsing rules within a grok processor. -{{< img src="service_management/events/grok-parser.png" alt="Parsing example 1" style="width:80%;">}} +{{< img src="events/grok-parser.png" alt="Parsing example 1" style="width:80%;">}} Click {{< ui >}}Parse My Events{{< /ui >}} to kickstart a set of three parsing rules for the events flowing through the underlying pipeline. Refine attribute naming from there, and add new rules for other type of events if needed. This feature requires that the corresponding events are being indexed, and actually flowing in—you can temporarily deactivate or sample down exclusion filters to make this work for you. diff --git a/content/en/events/triage_inbox.md b/content/en/events/triage_inbox.md index cb07bbe204d..eaea49df297 100644 --- a/content/en/events/triage_inbox.md +++ b/content/en/events/triage_inbox.md @@ -23,7 +23,7 @@ Datadog Event Management [Triage Inbox][4] simplifies incident response by conso Case triage and investigation begins in the Triage Inbox, where you can sort, filter, and manage incoming cases. Collaborate with teammates, both within and outside of Datadog, to coordinate responses. From there, you can prioritize, assign, investigate, and escalate cases as needed to drive faster resolution. -{{< img src="/service_management/events/triage_inbox/event_mgmt_inbox.mp4" alt="Event Management Inbox, sorting by priority, highlighting changing status and priority capabilities" video=true >}} +{{< img src="/events/triage_inbox/event_mgmt_inbox.mp4" alt="Event Management Inbox, sorting by priority, highlighting changing status and priority capabilities" video=true >}} ## Getting Started @@ -47,7 +47,7 @@ On the right hand split-view side panel, you can perform the following: - {{< ui >}}Escalate issues{{< /ui >}}: Trigger an incident or page an on-call responder using [Incident Management][1], [On-Call][2], [Workflow Automation][3], or third-party tools. - {{< ui >}}Sync with external tools{{< /ui >}}: Keep Jira and ServiceNow records in sync to ensure external stakeholders stay up to date. - {{< img src="/service_management/events/triage_inbox/event_mgmt_inbox_right_hand_panel.png" alt="Event Management Inbox right hand panel, highlighting Escalate drop down" style="width:100%;" >}} + {{< img src="/events/triage_inbox/event_mgmt_inbox_right_hand_panel.png" alt="Event Management Inbox right hand panel, highlighting Escalate drop down" style="width:100%;" >}} ## Take Action diff --git a/content/en/extend/_index.md b/content/en/extend/_index.md index 0e6759cc873..6d0f1d129dc 100644 --- a/content/en/extend/_index.md +++ b/content/en/extend/_index.md @@ -106,7 +106,7 @@ A [custom check][11], also know as a custom Agent check, lets you send internal {{< whatsnext desc="Learn about the types of data you can submit to Datadog and how to submit them:" >}} {{< nextlink href="/metrics" >}}Custom Metrics: A deep-dive into custom metrics at Datadog. This section explains metrics types, what they represent, how to submit them, and how they are used throughout Datadog.{{< /nextlink >}} - {{< nextlink href="service_management/events/guides/" >}}Events: Explore how to submit events to Datadog with custom Agent checks, DogStatsD, or the Datadog API.{{< /nextlink >}} + {{< nextlink href="events/guides/" >}}Events: Explore how to submit events to Datadog with custom Agent checks, DogStatsD, or the Datadog API.{{< /nextlink >}} {{< nextlink href="/extend/service_checks" >}}Service Checks: Explore how to submit the up or down status of a specific service to Datadog.{{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/en/extend/integrations/agent_integration.md b/content/en/extend/integrations/agent_integration.md index ee857441b5b..ee69fc1c453 100644 --- a/content/en/extend/integrations/agent_integration.md +++ b/content/en/extend/integrations/agent_integration.md @@ -485,7 +485,7 @@ Make sure to update all references to the version number across the integration' [1]: https://docs.datadoghq.com/agent/ [2]: https://docs.datadoghq.com/metrics/ -[3]: https://docs.datadoghq.com/service_management/events/ +[3]: https://docs.datadoghq.com/events/ [4]: /extend/service_checks/ [5]: https://docs.datadoghq.com/logs/log_collection/agent_checks/ [6]: https://docs.datadoghq.com/agent/guide/integration-management/?tab=linux#install diff --git a/content/en/glossary/terms/processing_pipeline_(Events).md b/content/en/glossary/terms/processing_pipeline_(Events).md index 44812afa044..55a9554aad6 100644 --- a/content/en/glossary/terms/processing_pipeline_(Events).md +++ b/content/en/glossary/terms/processing_pipeline_(Events).md @@ -6,4 +6,4 @@ related_terms: - pipeline --- For Datadog Events, a processing pipeline is a set sequence of data-structuring actions on event attributes when they are ingested. Users can configure processing pipelines to normalize and enrich events. -For more information, see the documentation. \ No newline at end of file +For more information, see the documentation. \ No newline at end of file diff --git a/content/en/metrics/guide/rate-limit.md b/content/en/metrics/guide/rate-limit.md index 3f3e8482c60..ad559f12d96 100644 --- a/content/en/metrics/guide/rate-limit.md +++ b/content/en/metrics/guide/rate-limit.md @@ -65,7 +65,7 @@ After making the changes to remove the unbounded tags, submit a request to [Data {{< partial name="whats-next/whats-next.html" >}} [1]: /account_management/billing/custom_metrics/?tab=countrate#effect-of-adding-tags -[2]: https://docs.datadoghq.com/service_management/events/ +[2]: https://docs.datadoghq.com/events/ [3]: https://docs.datadoghq.com/monitors/types/event/ [4]: https://docs.datadoghq.com/metrics/guide/custom_metrics_governance/ [5]: https://docs.datadoghq.com/help/ \ No newline at end of file diff --git a/content/en/monitors/status/events.md b/content/en/monitors/status/events.md index 781d2cd41fc..63e35eb7e95 100644 --- a/content/en/monitors/status/events.md +++ b/content/en/monitors/status/events.md @@ -2,7 +2,7 @@ title: Status Events description: "View and manage monitor events on the status page including quick actions, event details, and troubleshooting tools." further_reading: -- link: "service_management/events/" +- link: "events/" tag: "Documentation" text: "Event Management" --- diff --git a/static/images/service_management/events/correlation/case_analytics.png b/static/images/events/correlation/case_analytics.png similarity index 100% rename from static/images/service_management/events/correlation/case_analytics.png rename to static/images/events/correlation/case_analytics.png diff --git a/static/images/service_management/events/correlation/correlation_helper.mp4 b/static/images/events/correlation/correlation_helper.mp4 similarity index 100% rename from static/images/service_management/events/correlation/correlation_helper.mp4 rename to static/images/events/correlation/correlation_helper.mp4 diff --git a/static/images/service_management/events/correlation/event_analytics.png b/static/images/events/correlation/event_analytics.png similarity index 100% rename from static/images/service_management/events/correlation/event_analytics.png rename to static/images/events/correlation/event_analytics.png diff --git a/static/images/service_management/events/correlation/event_management.png b/static/images/events/correlation/event_management.png similarity index 100% rename from static/images/service_management/events/correlation/event_management.png rename to static/images/events/correlation/event_management.png diff --git a/static/images/service_management/events/correlation/intelligent/intelligent_config.png b/static/images/events/correlation/intelligent/intelligent_config.png similarity index 100% rename from static/images/service_management/events/correlation/intelligent/intelligent_config.png rename to static/images/events/correlation/intelligent/intelligent_config.png diff --git a/static/images/service_management/events/correlation/intelligent/intelligent_config_updated.png b/static/images/events/correlation/intelligent/intelligent_config_updated.png similarity index 100% rename from static/images/service_management/events/correlation/intelligent/intelligent_config_updated.png rename to static/images/events/correlation/intelligent/intelligent_config_updated.png diff --git a/static/images/service_management/events/correlation/intelligent/intelligent_correlation.png b/static/images/events/correlation/intelligent/intelligent_correlation.png similarity index 100% rename from static/images/service_management/events/correlation/intelligent/intelligent_correlation.png rename to static/images/events/correlation/intelligent/intelligent_correlation.png diff --git a/static/images/service_management/events/correlation/intelligent/intelligent_project.png b/static/images/events/correlation/intelligent/intelligent_project.png similarity index 100% rename from static/images/service_management/events/correlation/intelligent/intelligent_project.png rename to static/images/events/correlation/intelligent/intelligent_project.png diff --git a/static/images/service_management/events/correlation/pattern/preview_pattern_output.png b/static/images/events/correlation/pattern/preview_pattern_output.png similarity index 100% rename from static/images/service_management/events/correlation/pattern/preview_pattern_output.png rename to static/images/events/correlation/pattern/preview_pattern_output.png diff --git a/static/images/service_management/events/correlation/pattern/recommended_patterns_preview.png b/static/images/events/correlation/pattern/recommended_patterns_preview.png similarity index 100% rename from static/images/service_management/events/correlation/pattern/recommended_patterns_preview.png rename to static/images/events/correlation/pattern/recommended_patterns_preview.png diff --git a/static/images/service_management/events/correlation/triage/event_management_case_detail.png b/static/images/events/correlation/triage/event_management_case_detail.png similarity index 100% rename from static/images/service_management/events/correlation/triage/event_management_case_detail.png rename to static/images/events/correlation/triage/event_management_case_detail.png diff --git a/static/images/service_management/events/correlation/triage/triage.png b/static/images/events/correlation/triage/triage.png similarity index 100% rename from static/images/service_management/events/correlation/triage/triage.png rename to static/images/events/correlation/triage/triage.png diff --git a/static/images/service_management/events/events-analytics.png b/static/images/events/events-analytics.png similarity index 100% rename from static/images/service_management/events/events-analytics.png rename to static/images/events/events-analytics.png diff --git a/static/images/service_management/events/events-explorer.mp4 b/static/images/events/events-explorer.mp4 similarity index 100% rename from static/images/service_management/events/events-explorer.mp4 rename to static/images/events/events-explorer.mp4 diff --git a/static/images/service_management/events/explorer/display-values.png b/static/images/events/explorer/display-values.png similarity index 100% rename from static/images/service_management/events/explorer/display-values.png rename to static/images/events/explorer/display-values.png diff --git a/static/images/service_management/events/explorer/event-attribute.png b/static/images/events/explorer/event-attribute.png similarity index 100% rename from static/images/service_management/events/explorer/event-attribute.png rename to static/images/events/explorer/event-attribute.png diff --git a/static/images/service_management/events/explorer/events-overview.png b/static/images/events/explorer/events-overview.png similarity index 100% rename from static/images/service_management/events/explorer/events-overview.png rename to static/images/events/explorer/events-overview.png diff --git a/static/images/service_management/events/explorer/facet-to-graph.png b/static/images/events/explorer/facet-to-graph.png similarity index 100% rename from static/images/service_management/events/explorer/facet-to-graph.png rename to static/images/events/explorer/facet-to-graph.png diff --git a/static/images/service_management/events/explorer/facets-location.png b/static/images/events/explorer/facets-location.png similarity index 100% rename from static/images/service_management/events/explorer/facets-location.png rename to static/images/events/explorer/facets-location.png diff --git a/static/images/service_management/events/explorer/navigate.png b/static/images/events/explorer/navigate.png similarity index 100% rename from static/images/service_management/events/explorer/navigate.png rename to static/images/events/explorer/navigate.png diff --git a/static/images/service_management/events/explorer/split-graph.png b/static/images/events/explorer/split-graph.png similarity index 100% rename from static/images/service_management/events/explorer/split-graph.png rename to static/images/events/explorer/split-graph.png diff --git a/static/images/service_management/events/explorer/time-interval.png b/static/images/events/explorer/time-interval.png similarity index 100% rename from static/images/service_management/events/explorer/time-interval.png rename to static/images/events/explorer/time-interval.png diff --git a/static/images/service_management/events/graph-events.png b/static/images/events/graph-events.png similarity index 100% rename from static/images/service_management/events/graph-events.png rename to static/images/events/graph-events.png diff --git a/static/images/service_management/events/grok-parser.png b/static/images/events/grok-parser.png similarity index 100% rename from static/images/service_management/events/grok-parser.png rename to static/images/events/grok-parser.png diff --git a/static/images/service_management/events/guides/events-migration-monitor-new.png b/static/images/events/guides/events-migration-monitor-new.png similarity index 100% rename from static/images/service_management/events/guides/events-migration-monitor-new.png rename to static/images/events/guides/events-migration-monitor-new.png diff --git a/static/images/service_management/events/guides/usage/event_overlays.png b/static/images/events/guides/usage/event_overlays.png similarity index 100% rename from static/images/service_management/events/guides/usage/event_overlays.png rename to static/images/events/guides/usage/event_overlays.png diff --git a/static/images/service_management/events/guides/usage/events-dashboard.mp4 b/static/images/events/guides/usage/events-dashboard.mp4 similarity index 100% rename from static/images/service_management/events/guides/usage/events-dashboard.mp4 rename to static/images/events/guides/usage/events-dashboard.mp4 diff --git a/static/images/service_management/events/guides/usage/generate-metrics.png b/static/images/events/guides/usage/generate-metrics.png similarity index 100% rename from static/images/service_management/events/guides/usage/generate-metrics.png rename to static/images/events/guides/usage/generate-metrics.png diff --git a/static/images/service_management/events/triage_inbox/event_mgmt_inbox.mp4 b/static/images/events/triage_inbox/event_mgmt_inbox.mp4 similarity index 100% rename from static/images/service_management/events/triage_inbox/event_mgmt_inbox.mp4 rename to static/images/events/triage_inbox/event_mgmt_inbox.mp4 diff --git a/static/images/service_management/events/triage_inbox/event_mgmt_inbox_right_hand_panel.png b/static/images/events/triage_inbox/event_mgmt_inbox_right_hand_panel.png similarity index 100% rename from static/images/service_management/events/triage_inbox/event_mgmt_inbox_right_hand_panel.png rename to static/images/events/triage_inbox/event_mgmt_inbox_right_hand_panel.png From e1dcff044bd8422adc760b18d2c6962a592687c2 Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Tue, 16 Jun 2026 09:32:37 -0400 Subject: [PATCH 2/3] Apply suggestion from @domalessi Co-authored-by: domalessi <111786334+domalessi@users.noreply.github.com> --- content/en/events/guides/migrating_to_new_events_features.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/events/guides/migrating_to_new_events_features.md b/content/en/events/guides/migrating_to_new_events_features.md index 71572bfd367..7fab663ca49 100644 --- a/content/en/events/guides/migrating_to_new_events_features.md +++ b/content/en/events/guides/migrating_to_new_events_features.md @@ -50,7 +50,7 @@ In addition to viewing and searching events in the Explorer, you can now graph a You may also [generate metrics][3] with 15-month retention from any event search query to create monitors and alerts based on historical events. -{{< img src="events/generate-metrics.png" alt="Image of metrics with the events search query." >}} +{{< img src="events/guides/usage/generate-metrics.png" alt="Image of metrics with the events search query." >}} ### Graph events in dashboards From a59c32205b22ac03dc56abcbce56c561c5112604 Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Tue, 16 Jun 2026 09:35:42 -0400 Subject: [PATCH 3/3] Update Events image paths in translated content Updates service_management/events/ image references to events/ across ja, ko, fr, and es files to match the English path migration. Co-Authored-By: Claude Sonnet 4.6 --- content/es/administrators_guide/plan.md | 2 +- content/es/developers/_index.md | 2 +- content/es/developers/dogstatsd/_index.md | 4 ++-- .../integrations/agent_integration.md | 2 +- .../es/dora_metrics/data_collected/_index.md | 2 +- content/es/error_tracking/dynamic_sampling.md | 2 +- .../error_tracking/manage_data_collection.md | 2 +- content/es/events/guides/agent.md | 2 +- content/es/events/guides/dogstatsd.md | 2 +- .../events/guides/recommended_event_tags.md | 2 +- content/es/events/ingest.md | 2 +- .../pipelines_and_processors/grok_parser.md | 4 ++-- .../es/getting_started/tagging/using_tags.md | 2 +- .../terms/processing_pipeline_(Events).md | 2 +- content/es/integrations/catchpoint.md | 2 +- content/es/integrations/crowdstrike.md | 2 +- content/es/integrations/event-viewer.md | 2 +- content/es/integrations/feed.md | 4 ++-- .../guide/events-from-sns-emails.md | 2 +- .../harness-harness-notifications.md | 2 +- .../harness_harness_notifications.md | 2 +- content/es/integrations/redmine.md | 2 +- content/es/integrations/slack.md | 2 +- content/es/integrations/snowflake_web.md | 2 +- content/es/integrations/win32_event_log.md | 2 +- .../error_tracking/manage_data_collection.md | 2 +- .../best-practices-for-log-management.md | 2 +- content/es/metrics/guide/rate-limit.md | 2 +- content/es/metrics/overview.md | 2 +- content/es/monitors/downtimes/_index.md | 2 +- .../integrate-monitors-with-statuspage.md | 2 +- content/es/monitors/status/events.md | 2 +- content/es/monitors/types/event.md | 4 ++-- content/es/reference_tables/_index.md | 2 +- .../es/service_management/events/_index.md | 14 +++++------ .../events/correlation/_index.md | 8 +++---- .../events/correlation/analytics.md | 6 ++--- .../events/correlation/configuration.md | 4 ++-- .../events/correlation/intelligent.md | 8 +++---- .../events/correlation/patterns.md | 14 +++++------ .../events/explorer/_index.md | 18 +++++++------- .../events/explorer/analytics.md | 8 +++---- .../events/explorer/attributes.md | 4 ++-- .../events/explorer/navigate.md | 4 ++-- .../events/explorer/saved_views.md | 6 ++--- .../events/guides/_index.md | 14 +++++------ .../events/guides/dogstatsd.md | 2 +- .../migrating_to_new_events_features.md | 16 ++++++------- .../events/guides/recommended_event_tags.md | 2 +- .../service_management/events/guides/usage.md | 12 +++++----- .../es/service_management/events/ingest.md | 6 ++--- .../events/pipelines_and_processors/_index.md | 24 +++++++++---------- .../aggregation_key.md | 2 +- .../pipelines_and_processors/grok_parser.md | 6 ++--- content/es/synthetics/explore/_index.md | 2 +- .../mobile_app_tests/results.md | 2 +- .../watchdog/faulty_deployment_detection.md | 2 +- content/fr/administrators_guide/plan.md | 2 +- content/fr/developers/_index.md | 2 +- content/fr/developers/dogstatsd/_index.md | 4 ++-- .../integrations/agent_integration.md | 2 +- .../pipelines_and_processors/grok_parser.md | 4 ++-- .../fr/getting_started/application/_index.md | 6 ++--- .../fr/getting_started/tagging/using_tags.md | 2 +- .../guide/events-from-sns-emails.md | 2 +- .../integrate-monitors-with-statuspage.md | 2 +- .../events/correlation/analytics.md | 6 ++--- .../events/explorer/analytics.md | 8 +++---- .../events/explorer/attributes.md | 4 ++-- .../events/explorer/facets.md | 4 ++-- .../events/explorer/navigate.md | 4 ++-- .../events/guides/_index.md | 14 +++++------ .../migrating_to_new_events_features.md | 16 ++++++------- .../events/guides/recommended_event_tags.md | 2 +- .../events/pipelines_and_processors/_index.md | 18 +++++++------- content/ja/account_management/org_settings.md | 2 +- content/ja/coterm/usage.md | 2 +- content/ja/developers/_index.md | 2 +- content/ja/developers/dogstatsd/_index.md | 4 ++-- .../integrations/agent_integration.md | 2 +- content/ja/dora_metrics/setup/_index.md | 2 +- content/ja/error_tracking/dynamic_sampling.md | 2 +- .../events/guides/recommended_event_tags.md | 2 +- .../ja/getting_started/application/_index.md | 4 ++-- .../terms/processing_pipeline_(Events).md | 2 +- content/ja/integrations/catchpoint.md | 2 +- content/ja/integrations/crowdstrike.md | 2 +- .../guide/events-from-sns-emails.md | 2 +- .../harness_harness_notifications.md | 2 +- content/ja/integrations/redmine.md | 2 +- content/ja/integrations/slack.md | 2 +- content/ja/integrations/snowflake_web.md | 2 +- content/ja/integrations/win32_event_log.md | 2 +- .../best-practices-for-log-management.md | 2 +- content/ja/logs/log_configuration/archives.md | 2 +- content/ja/metrics/overview.md | 2 +- content/ja/monitors/downtimes/_index.md | 2 +- .../integrate-monitors-with-statuspage.md | 2 +- content/ja/monitors/status/events.md | 2 +- content/ja/monitors/types/event.md | 4 ++-- .../partners/getting_started/data-intake.md | 2 +- .../ja/service_management/events/_index.md | 14 +++++------ .../events/correlation/_index.md | 8 +++---- .../events/correlation/configuration.md | 8 +++---- .../events/correlation/intelligent.md | 8 +++---- .../events/correlation/patterns.md | 14 +++++------ .../events/explorer/_index.md | 18 +++++++------- .../events/explorer/analytics.md | 8 +++---- .../events/guides/_index.md | 14 +++++------ .../events/guides/dogstatsd.md | 2 +- .../migrating_to_new_events_features.md | 16 ++++++------- .../events/guides/recommended_event_tags.md | 2 +- .../service_management/events/guides/usage.md | 14 +++++------ .../events/pipelines_and_processors/_index.md | 18 +++++++------- .../pipelines_and_processors/grok_parser.md | 6 ++--- content/ja/synthetics/explore/_index.md | 2 +- .../watchdog/faulty_deployment_detection.md | 2 +- content/ko/account_management/org_settings.md | 2 +- content/ko/administrators_guide/plan.md | 2 +- content/ko/developers/_index.md | 2 +- content/ko/developers/dogstatsd/_index.md | 4 ++-- .../integrations/agent_integration.md | 2 +- .../ko/dora_metrics/data_collected/_index.md | 2 +- .../events/guides/recommended_event_tags.md | 2 +- .../ko/getting_started/application/_index.md | 4 ++-- .../ko/getting_started/tagging/using_tags.md | 2 +- content/ko/integrations/catchpoint.md | 2 +- content/ko/integrations/crowdstrike.md | 2 +- .../guide/events-from-sns-emails.md | 2 +- content/ko/integrations/redmine.md | 2 +- .../error_tracking/manage_data_collection.md | 2 +- content/ko/logs/log_configuration/archives.md | 2 +- content/ko/metrics/guide/rate-limit.md | 2 +- content/ko/monitors/downtimes/_index.md | 2 +- .../integrate-monitors-with-statuspage.md | 2 +- .../ko/service_management/events/_index.md | 14 +++++------ .../events/correlation/_index.md | 8 +++---- .../events/correlation/analytics.md | 6 ++--- .../events/correlation/configuration.md | 4 ++-- .../events/correlation/intelligent.md | 8 +++---- .../events/correlation/patterns.md | 14 +++++------ .../events/explorer/_index.md | 18 +++++++------- .../events/explorer/analytics.md | 8 +++---- .../events/explorer/attributes.md | 4 ++-- .../events/explorer/facets.md | 4 ++-- .../events/explorer/navigate.md | 4 ++-- .../events/explorer/saved_views.md | 6 ++--- .../events/guides/_index.md | 2 +- .../migrating_to_new_events_features.md | 16 ++++++------- .../events/guides/recommended_event_tags.md | 2 +- .../ko/service_management/events/ingest.md | 6 ++--- .../events/pipelines_and_processors/_index.md | 18 +++++++------- .../pipelines_and_processors/grok_parser.md | 6 ++--- .../service_management/events/triage_inbox.md | 8 +++---- .../watchdog/faulty_deployment_detection.md | 2 +- 155 files changed, 386 insertions(+), 386 deletions(-) diff --git a/content/es/administrators_guide/plan.md b/content/es/administrators_guide/plan.md index 66b5932208a..d4d83c0d977 100644 --- a/content/es/administrators_guide/plan.md +++ b/content/es/administrators_guide/plan.md @@ -347,7 +347,7 @@ Crea una metodología de despliegue detallada en la fase de [compilación][41] c [28]: /es/integrations/network/ [29]: /es/network_monitoring/cloud_network_monitoring/ [30]: /es/service_catalog/ -[31]: /es/service_management/events/ +[31]: /es/events/ [32]: /es/error_tracking/ [33]: /es/api_catalog/ [34]: /es/agent/fleet_automation/ diff --git a/content/es/developers/_index.md b/content/es/developers/_index.md index e10ed31b71f..e4dff512cd8 100644 --- a/content/es/developers/_index.md +++ b/content/es/developers/_index.md @@ -105,7 +105,7 @@ El [check personalizado][11], también conocido como check personalizado del Age {{< whatsnext desc="Descubre los tipos de datos que puedes enviar a Datadog y aprende a enviarlos:" >}} {{< nextlink href="/metrics" >}}Métricas personalizadas: una profundización en las métricas personalizadas de Datadog. Esta sección describe los tipos de métricas, lo que estas representan, cómo enviarlas y cómo son utilizadas por Datadog.{{< /nextlink >}} - {{< nextlink href="service_management/events/guides/" >}}Eventos: descubre cómo enviar eventos a Datadog utilizando checks personalizados del Agent, DogStatsD o la API de Datadog.{{< /nextlink >}} + {{< nextlink href="events/guides/" >}}Eventos: descubre cómo enviar eventos a Datadog utilizando checks personalizados del Agent, DogStatsD o la API de Datadog.{{< /nextlink >}} {{< nextlink href="/developers/service_checks" >}}Checks de servicios: descubre cómo enviar los estados de ascenso y descenso de un servicio específico a Datadog.{{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/es/developers/dogstatsd/_index.md b/content/es/developers/dogstatsd/_index.md index 2464d797c8d..3fa26a38e4f 100644 --- a/content/es/developers/dogstatsd/_index.md +++ b/content/es/developers/dogstatsd/_index.md @@ -603,7 +603,7 @@ DogStatsD y StatsD son en general similares, sin embargo, DogStatsD contiene car {{< whatsnext desc="">}} {{< nextlink href="/metrics/custom_metrics/dogstatsd_metrics_submission/" >}}Enviar métricas a Datadog con DogStatsD.{{< /nextlink >}} -{{< nextlink href="/service_management/events/guides/dogstatsd/" >}}Enviar eventos a Datadog con DogStatsD.{{< /nextlink >}} +{{< nextlink href="/events/guides/dogstatsd/" >}}Enviar eventos a Datadog con DogStatsD.{{< /nextlink >}} {{< nextlink href="/developers/service_checks/dogstatsd_service_checks_submission/" >}}Enviar checks de servicio a Datadog con DogStatsD.{{< /nextlink >}} {{< /whatsnext >}} @@ -618,7 +618,7 @@ Si te interesa aprender más sobre el formato de datagram utilizado por DogStats [3]: https://hub.docker.com/r/datadog/dogstatsd [4]: https://gcr.io/datadoghq/dogstatsd [5]: /es/metrics/custom_metrics/ -[6]: /es/service_management/events/guides/dogstatsd/ +[6]: /es/events/guides/dogstatsd/ [7]: /es/developers/service_checks/dogstatsd_service_checks_submission/ [8]: /es/getting_started/tagging/unified_service_tagging [9]: /es/developers/dogstatsd/datagram_shell/ diff --git a/content/es/developers/integrations/agent_integration.md b/content/es/developers/integrations/agent_integration.md index 8f26aa5f63a..a493129264a 100644 --- a/content/es/developers/integrations/agent_integration.md +++ b/content/es/developers/integrations/agent_integration.md @@ -488,7 +488,7 @@ Además de cualquier cambio en el código, se requiere lo siguiente cuando se ac [15]: /es/developers/integrations/check_references/#service-check-file [16]: https://packaging.python.org/en/latest/tutorials/packaging-projects/ [17]: https://docs.datadoghq.com/es/agent/ -[18]: https://docs.datadoghq.com/es/service_management/events/ +[18]: https://docs.datadoghq.com/es/events/ [19]: https://desktop.github.com/ [20]: https://docs.datadoghq.com/es/developers/integrations/create_a_tile [21]: https://github.com/Datadog/integrations-extras diff --git a/content/es/dora_metrics/data_collected/_index.md b/content/es/dora_metrics/data_collected/_index.md index 7c877059e83..07bdfb5ebbf 100644 --- a/content/es/dora_metrics/data_collected/_index.md +++ b/content/es/dora_metrics/data_collected/_index.md @@ -76,7 +76,7 @@ Estas métricas pueden consultarse mediante programación utilizando los endpoin {{< partial name="whats-next/whats-next.html" >}} -[1]: /es/service_management/events/explorer/ +[1]: /es/events/explorer/ [2]: /es/api/latest/metrics/#query-timeseries-points [3]: /es/api/latest/metrics/#query-timeseries-data-across-multiple-products [5]: https://app.datadoghq.com/event/explorer?query=source%3Asoftware_delivery_insights diff --git a/content/es/error_tracking/dynamic_sampling.md b/content/es/error_tracking/dynamic_sampling.md index abfa74ec1e0..34ff124392c 100644 --- a/content/es/error_tracking/dynamic_sampling.md +++ b/content/es/error_tracking/dynamic_sampling.md @@ -49,7 +49,7 @@ Cuando se aplica el muestreo dinámico, los siguientes pasos son recomendados: {{< partial name="whats-next/whats-next.html" >}} -[1]: /es/service_management/events/ +[1]: /es/events/ [2]: https://app.datadoghq.com/error-tracking/settings/rate-limits [3]: /es/logs/error_tracking/manage_data_collection#add-a-rule [4]: https://app.datadoghq.com/error-tracking/settings \ No newline at end of file diff --git a/content/es/error_tracking/manage_data_collection.md b/content/es/error_tracking/manage_data_collection.md index f602dc56426..84182340ae5 100644 --- a/content/es/error_tracking/manage_data_collection.md +++ b/content/es/error_tracking/manage_data_collection.md @@ -148,5 +148,5 @@ Cuando se aplica el muestreo dinámico, los siguientes pasos son recomendados: [1]: https://app.datadoghq.com/error-tracking/settings/rules [2]: /es/error_tracking/troubleshooting/?tab=java#errors-are-not-found-in-error-tracking -[4]: /es/service_management/events/ +[4]: /es/events/ [5]: https://app.datadoghq.com/error-tracking/settings/rate-limits \ No newline at end of file diff --git a/content/es/events/guides/agent.md b/content/es/events/guides/agent.md index c8e704ccee9..fe0f1560c2d 100644 --- a/content/es/events/guides/agent.md +++ b/content/es/events/guides/agent.md @@ -1,6 +1,6 @@ --- aliases: -- /es/service_management/events/guides/agent/ +- /es/events/guides/agent/ further_reading: - link: /developers/custom_checks/write_agent_check/ tag: Documentación diff --git a/content/es/events/guides/dogstatsd.md b/content/es/events/guides/dogstatsd.md index e5e29ee8c51..cc20a4a3ded 100644 --- a/content/es/events/guides/dogstatsd.md +++ b/content/es/events/guides/dogstatsd.md @@ -1,7 +1,7 @@ --- aliases: - /es/developers/events/dogstatsd/ -- /es/service_management/events/guides/dogstatsd/ +- /es/events/guides/dogstatsd/ description: Información general de las características de DogStatsD, incluidos los tipos de datos y el etiquetado. further_reading: diff --git a/content/es/events/guides/recommended_event_tags.md b/content/es/events/guides/recommended_event_tags.md index afce1c08ec3..749b43df69d 100644 --- a/content/es/events/guides/recommended_event_tags.md +++ b/content/es/events/guides/recommended_event_tags.md @@ -1,6 +1,6 @@ --- aliases: -- /es/service_management/events/guides/recommended_event_tags/ +- /es/events/guides/recommended_event_tags/ description: Obtén información sobre las etiquetas de eventos recomendadas y cómo añadirlas. further_reading: diff --git a/content/es/events/ingest.md b/content/es/events/ingest.md index a3a098f4806..3b7254a827a 100644 --- a/content/es/events/ingest.md +++ b/content/es/events/ingest.md @@ -1,6 +1,6 @@ --- aliases: -- /es/service_management/events/ingest/ +- /es/events/ingest/ title: Enviar eventos a Datadog --- diff --git a/content/es/events/pipelines_and_processors/grok_parser.md b/content/es/events/pipelines_and_processors/grok_parser.md index b035896df44..4261e174b87 100644 --- a/content/es/events/pipelines_and_processors/grok_parser.md +++ b/content/es/events/pipelines_and_processors/grok_parser.md @@ -1,6 +1,6 @@ --- aliases: -- /es/service_management/events/pipelines_and_processors/grok_parser/ +- /es/events/pipelines_and_processors/grok_parser/ description: Crea reglas grok personalizadas para analizar el mensaje completo o atributos específicos de eventos en bruto en datos estructurados. title: Analizador Grok @@ -10,7 +10,7 @@ title: Analizador Grok Crea reglas grok personalizadas para analizar el mensaje completo o un atributo específico de su evento en bruto. Como mejor práctica, se recomienda utilizar un máximo de 10 reglas de análisis dentro de un procesador grok. -{{< img src="service_management/events/grok-parser.png" alt="Ejemplo de análisis 1" style="width:80%;">}} +{{< img src="events/grok-parser.png" alt="Ejemplo de análisis 1" style="width:80%;">}} Haga clic en **Analizar Mis Eventos** para iniciar un conjunto de tres reglas de análisis para los eventos que fluyen a través de la canalización subyacente. Refine la nomenclatura de los atributos desde allí y agregue nuevas reglas para otros tipos de eventos si es necesario. Esta función requiere que los eventos correspondientes estén siendo indexados y fluyendo realmente; puede desactivar temporalmente o reducir los filtros de exclusión para que esto funcione para usted. diff --git a/content/es/getting_started/tagging/using_tags.md b/content/es/getting_started/tagging/using_tags.md index 741dd43d037..5bf586963c0 100644 --- a/content/es/getting_started/tagging/using_tags.md +++ b/content/es/getting_started/tagging/using_tags.md @@ -386,7 +386,7 @@ Consulta esta lista para encontrar los enlaces a cada una de las siguientes secc {{< partial name="whats-next/whats-next.html" >}} [1]: /es/getting_started/tagging/assigning_tags/ -[2]: /es/service_management/events/explorer +[2]: /es/events/explorer [3]: /es/integrations/ [4]: /es/infrastructure/hostmap/ [5]: /es/infrastructure/ diff --git a/content/es/glossary/terms/processing_pipeline_(Events).md b/content/es/glossary/terms/processing_pipeline_(Events).md index 1c556f97e28..3c814aa1cfc 100644 --- a/content/es/glossary/terms/processing_pipeline_(Events).md +++ b/content/es/glossary/terms/processing_pipeline_(Events).md @@ -6,4 +6,4 @@ related_terms: title: pipeline de procesamiento --- Para los eventos de Datadog, un pipeline de procesamiento es una secuencia establecida de acciones de estructuración de datos en los atributos del evento cuando se ingieren. Los usuarios pueden configurar pipelines de procesamiento para normalizar y enriquecer eventos. -Para obtener más información, consulta la documentación. \ No newline at end of file +Para obtener más información, consulta la documentación. \ No newline at end of file diff --git a/content/es/integrations/catchpoint.md b/content/es/integrations/catchpoint.md index 53241406c03..c9757bdbdcb 100644 --- a/content/es/integrations/catchpoint.md +++ b/content/es/integrations/catchpoint.md @@ -66,7 +66,7 @@ Para recibir alertas de Catchpoint en tu flujo de eventosinicia sesión en el po } ``` -Catchpoint envía las alertas directamente al [Explorador de eventos](https://docs.datadoghq.com/service_management/events/) en Datadog. +Catchpoint envía las alertas directamente al [Explorador de eventos](https://docs.datadoghq.com/events/) en Datadog. ![evento de catchpoint](images/screenshot.png) diff --git a/content/es/integrations/crowdstrike.md b/content/es/integrations/crowdstrike.md index ae9ed2d8560..de8738385e2 100644 --- a/content/es/integrations/crowdstrike.md +++ b/content/es/integrations/crowdstrike.md @@ -27,7 +27,7 @@ No requiere instalación. #### Activación del streaming de eventos -Antes de poder conectarte al [Event Stream](https://docs.datadoghq.com/service_management/events/explorer/), [ponte en contacto con el equipo de asistencia de CrowdStrike](https://supportportal.crowdstrike.com/) para habilitar el flujo de APIs en tu cuenta de cliente. +Antes de poder conectarte al [Event Stream](https://docs.datadoghq.com/events/explorer/), [ponte en contacto con el equipo de asistencia de CrowdStrike](https://supportportal.crowdstrike.com/) para habilitar el flujo de APIs en tu cuenta de cliente. #### Conexión de tu cuenta de CrowdStrike diff --git a/content/es/integrations/event-viewer.md b/content/es/integrations/event-viewer.md index 474b552fbce..536f17bddc2 100644 --- a/content/es/integrations/event-viewer.md +++ b/content/es/integrations/event-viewer.md @@ -54,7 +54,7 @@ El check de log de eventos de Windows se incluye en el paquete del [Datadog Agen Los logs de eventos de Windows se pueden recopilar mediante uno o ambos de los siguientes métodos. -- Como [eventos de Datadog](https://docs.datadoghq.com/service_management/events/) +- Como [eventos de Datadog](https://docs.datadoghq.com/events/) - Como [logs de Datadog](https://docs.datadoghq.com/logs/) Ambos métodos se configuran en `win32_event_log.d/conf.yaml` en la carpeta `conf.d/` en la raíz del [directorio de configuración del Agent](https://docs.datadoghq.com/agent/guide/agent-configuration-files/#agent-configuration-directory). Consulta el [win32_event_log.d/conf.yaml de ejemplo](https://github.com/DataDog/integrations-core/blob/master/win32_event_log/datadog_checks/win32_event_log/data/conf.yaml.example) para conocer todas las opciones de configuración disponibles. Para una opción de inicio rápido para enviar logs de eventos de seguridad, consulta [Send default Security logs](#send-default-security-logs). diff --git a/content/es/integrations/feed.md b/content/es/integrations/feed.md index 5242655d099..c39bd70bcea 100644 --- a/content/es/integrations/feed.md +++ b/content/es/integrations/feed.md @@ -6,7 +6,7 @@ categories: custom_kind: integración description: Recopilar eventos de RSS Feed en Datadog further_reading: -- link: https://docs.datadoghq.com/service_management/events/usage +- link: https://docs.datadoghq.com/events/usage tag: documentación text: Proporcionar documentación integration_version: 1.0.0 @@ -55,4 +55,4 @@ Consulta el [Events Explorer](https://app.datadoghq.com/event/explorer) para ver Documentación útil adicional, enlaces y artículos: -- [Uso de eventos](https://docs.datadoghq.com/service_management/events/usage) \ No newline at end of file +- [Uso de eventos](https://docs.datadoghq.com/events/usage) \ No newline at end of file diff --git a/content/es/integrations/guide/events-from-sns-emails.md b/content/es/integrations/guide/events-from-sns-emails.md index cbbcdbbe26c..cdd18eae9ca 100644 --- a/content/es/integrations/guide/events-from-sns-emails.md +++ b/content/es/integrations/guide/events-from-sns-emails.md @@ -39,7 +39,7 @@ Configura alertas basadas en los correos electrónicos de tu tema de SNS con un {{< partial name="whats-next/whats-next.html" >}} -[1]: /es/service_management/events/guides/email/ +[1]: /es/events/guides/email/ [2]: https://app.datadoghq.com/event/explorer [3]: /es/monitors/types/event/ [4]: /es/events/explorer/ diff --git a/content/es/integrations/harness-harness-notifications.md b/content/es/integrations/harness-harness-notifications.md index ee7ed964201..0d6d05224bb 100644 --- a/content/es/integrations/harness-harness-notifications.md +++ b/content/es/integrations/harness-harness-notifications.md @@ -28,7 +28,7 @@ title: Notificaciones de Harness --- ## Información general -Harness es una plataforma CI/CD de autoservicio que permite a ingenieros y DevOps crear, probar, desplegar y comprobar software bajo demanda. Con esta integración, puedes enviar notificaciones de eventos de pipelines de Harness a Datadog de forma continua, lo que te garantiza una visibilidad en tiempo real de las actualizaciones críticas de pipelines en tus flujos de trabajo de monitorización existentes. Estas notificaciones están disponibles en el [Explorador de eventos](https://docs.datadoghq.com/service_management/events/explorer/) de Datadog y se muestran en el dashboard predefinido. +Harness es una plataforma CI/CD de autoservicio que permite a ingenieros y DevOps crear, probar, desplegar y comprobar software bajo demanda. Con esta integración, puedes enviar notificaciones de eventos de pipelines de Harness a Datadog de forma continua, lo que te garantiza una visibilidad en tiempo real de las actualizaciones críticas de pipelines en tus flujos de trabajo de monitorización existentes. Estas notificaciones están disponibles en el [Explorador de eventos](https://docs.datadoghq.com/events/explorer/) de Datadog y se muestran en el dashboard predefinido. **Nota**: La posibilidad de configurar las notificaciones de Datadog en Harness está detrás de un indicador de función. Ponte en contacto con el [servicio de asistencia de Harness](mailto:support@harness.io) para activar esta función. Consulta la [documentación de Harness](https://developer.harness.io/docs/continuous-delivery/x-platform-cd-features/cd-steps/notify-users-of-pipeline-events/#datadog-notifications) para obtener más información sobre esta integración. diff --git a/content/es/integrations/harness_harness_notifications.md b/content/es/integrations/harness_harness_notifications.md index 30d12f4f3a9..9f91a54c351 100644 --- a/content/es/integrations/harness_harness_notifications.md +++ b/content/es/integrations/harness_harness_notifications.md @@ -109,7 +109,7 @@ Los canales de notificación se pueden activar, desactivar o eliminar desde la p ¿Necesitas ayuda? Ponte en contacto con el [servicio de asistencia de Harness][5]. -[1]: https://docs.datadoghq.com/es/service_management/events/explorer/ +[1]: https://docs.datadoghq.com/es/events/explorer/ [2]: mailto:support@harness.io [3]: https://developer.harness.io/docs/continuous-delivery/x-platform-cd-features/cd-steps/notify-users-of-pipeline-events/#datadog-notifications [4]: https://docs.datadoghq.com/es/account_management/api-app-keys/ diff --git a/content/es/integrations/redmine.md b/content/es/integrations/redmine.md index de0be93ab41..5c1e46468af 100644 --- a/content/es/integrations/redmine.md +++ b/content/es/integrations/redmine.md @@ -59,5 +59,5 @@ La integración Redmine no incluye checks de servicio. ¿Necesitas ayuda? Ponte en contacto con el [servicio de asistencia de Datadog][3]. [1]: https://app.datadoghq.com/integrations/redmine -[2]: https://docs.datadoghq.com/es/service_management/events/explorer/ +[2]: https://docs.datadoghq.com/es/events/explorer/ [3]: https://docs.datadoghq.com/es/help/ \ No newline at end of file diff --git a/content/es/integrations/slack.md b/content/es/integrations/slack.md index be443a88e8f..ecf7b73c9b4 100644 --- a/content/es/integrations/slack.md +++ b/content/es/integrations/slack.md @@ -118,7 +118,7 @@ También puedes enviar notificaciones a Slack desde [monitores][3] y [eventos][4 [1]: https://app.datadoghq.com/integrations/slack [2]: https://slack.com/apps/A0F7XDT7F-datadog-legacy [3]: https://docs.datadoghq.com/monitors/notifications/ -[4]: https://docs.datadoghq.com/service_management/events/explorer/notifications/ +[4]: https://docs.datadoghq.com/events/explorer/notifications/ {{% /tab %}} {{< /tabs >}} diff --git a/content/es/integrations/snowflake_web.md b/content/es/integrations/snowflake_web.md index fcc87e8107f..6d7d842ebff 100644 --- a/content/es/integrations/snowflake_web.md +++ b/content/es/integrations/snowflake_web.md @@ -700,7 +700,7 @@ Documentación útil adicional, enlaces y artículos: [10]: images/custom_query.png [11]: images/snowflake_metrics.png [12]: https://docs.datadoghq.com/es/reference_tables/?tab=manualupload -[13]: https://docs.datadoghq.com/es/service_management/events/explorer/ +[13]: https://docs.datadoghq.com/es/events/explorer/ [14]: https://docs.snowflake.com/en/user-guide/views-introduction [15]: https://www.datadoghq.com/product/cloud-cost-management/ [16]: https://docs.snowflake.com/en/user-guide/views-materialized diff --git a/content/es/integrations/win32_event_log.md b/content/es/integrations/win32_event_log.md index e86a092ddd3..87fcf464ec7 100644 --- a/content/es/integrations/win32_event_log.md +++ b/content/es/integrations/win32_event_log.md @@ -632,7 +632,7 @@ Más enlaces, artículos y documentación útiles: [1]: https://docs.microsoft.com/en-us/windows/win32/eventlog/event-logging [2]: https://app.datadoghq.com/account/settings/agent/latest?platform=windows -[3]: https://docs.datadoghq.com/es/service_management/events/ +[3]: https://docs.datadoghq.com/es/events/ [4]: https://docs.datadoghq.com/es/logs/ [5]: https://docs.datadoghq.com/es/agent/guide/agent-configuration-files/#agent-configuration-directory [6]: https://github.com/DataDog/integrations-core/blob/master/win32_event_log/datadog_checks/win32_event_log/data/conf.yaml.example diff --git a/content/es/logs/error_tracking/manage_data_collection.md b/content/es/logs/error_tracking/manage_data_collection.md index 9eb15cda495..c9dbfc9608f 100644 --- a/content/es/logs/error_tracking/manage_data_collection.md +++ b/content/es/logs/error_tracking/manage_data_collection.md @@ -97,4 +97,4 @@ Esta métrica está disponible por defecto sin coste adicional, y tus datos se c [1]: https://app.datadoghq.com/error-tracking/settings/rules [2]: /es/logs/error_tracking/#setup [3]: /es/logs/explorer/search_syntax/ -[4]: /es/service_management/events/ \ No newline at end of file +[4]: /es/events/ \ No newline at end of file diff --git a/content/es/logs/guide/best-practices-for-log-management.md b/content/es/logs/guide/best-practices-for-log-management.md index 7531c664b02..fc5f66c19a8 100644 --- a/content/es/logs/guide/best-practices-for-log-management.md +++ b/content/es/logs/guide/best-practices-for-log-management.md @@ -230,7 +230,7 @@ Si quieres ver las actividades de los usuarios, como quién ha cambiado las opci [14]: https://app.datadoghq.com/logs [15]: /es/logs/explorer/search/ [16]: /es/logs/indexes/#set-daily-quota -[17]: /es/service_management/events/explorer/facets +[17]: /es/events/explorer/facets [18]: https://app.datadoghq.com/dash/integration/logs_estimated_usage [19]: https://app.datadoghq.com/dashboard/lists?q=Log+Management+-+Estimated+Usage [20]: /es/logs/log_configuration/indexes/#exclusion-filters diff --git a/content/es/metrics/guide/rate-limit.md b/content/es/metrics/guide/rate-limit.md index 973afa9171b..862234b1a41 100644 --- a/content/es/metrics/guide/rate-limit.md +++ b/content/es/metrics/guide/rate-limit.md @@ -64,7 +64,7 @@ Después de hacer los cambios para eliminar las etiquetas sin límites, envía u {{< partial name="whats-next/whats-next.html" >}} [1]: /es/account_management/billing/custom_metrics/?tab=countrate#effect-of-adding-tags -[2]: https://docs.datadoghq.com/es/service_management/events/ +[2]: https://docs.datadoghq.com/es/events/ [3]: https://docs.datadoghq.com/es/monitors/types/event/ [4]: https://docs.datadoghq.com/es/metrics/guide/custom_metrics_governance/ [5]: https://docs.datadoghq.com/es/help/ \ No newline at end of file diff --git a/content/es/metrics/overview.md b/content/es/metrics/overview.md index 1c4955e0a11..d727122e231 100644 --- a/content/es/metrics/overview.md +++ b/content/es/metrics/overview.md @@ -141,7 +141,7 @@ Utiliza la barra de búsqueda de esta sección para ver los datos y las opciones [15]: /es/tracing/trace_pipeline/generate_metrics/ [16]: /es/real_user_monitoring/platform/generate_metrics/ [17]: /es/infrastructure/process/increase_process_retention/#generate-a-process-based-metric -[18]: /es/service_management/events/guides/usage/#custom-metrics +[18]: /es/events/guides/usage/#custom-metrics [19]: /es/metrics/metrics-without-limits/ [20]: /es/metrics/distributions/ [21]: /es/metrics/custom_metrics/historical_metrics/ diff --git a/content/es/monitors/downtimes/_index.md b/content/es/monitors/downtimes/_index.md index dba6ec21051..bfbb30cccbc 100644 --- a/content/es/monitors/downtimes/_index.md +++ b/content/es/monitors/downtimes/_index.md @@ -196,7 +196,7 @@ Datadog puede silenciar proactivamente monitores relacionados con el apagado man [7]: /es/monitors/notify/#overview [8]: /es/integrations/#cat-notification [9]: /es/monitors/status/ -[10]: /es/service_management/events/explorer +[10]: /es/events/explorer [11]: /es/api/latest/downtimes/#cancel-a-downtime [12]: /es/account_management/#preferences [13]: /es/integrations/amazon_ec2/#ec2-automuting diff --git a/content/es/monitors/guide/integrate-monitors-with-statuspage.md b/content/es/monitors/guide/integrate-monitors-with-statuspage.md index 72531353af2..8b3ce3ed3eb 100644 --- a/content/es/monitors/guide/integrate-monitors-with-statuspage.md +++ b/content/es/monitors/guide/integrate-monitors-with-statuspage.md @@ -59,7 +59,7 @@ Para crear un [monitor de métricas][8] que se active con las alertas de Statusp [1]: https://www.atlassian.com/software/statuspage [2]: /es/integrations/statuspage -[3]: /es/service_management/events/explorer/ +[3]: /es/events/explorer/ [4]: https://app.datadoghq.com/integrations [5]: https://app.datadoghq.com/event/explorer [6]: /es/dashboards/guide/custom_time_frames/ diff --git a/content/es/monitors/status/events.md b/content/es/monitors/status/events.md index 973089b7af8..06b699f819b 100644 --- a/content/es/monitors/status/events.md +++ b/content/es/monitors/status/events.md @@ -1,6 +1,6 @@ --- further_reading: -- link: service_management/events/ +- link: events/ tag: Documentación text: Gestión de eventos title: Status Events diff --git a/content/es/monitors/types/event.md b/content/es/monitors/types/event.md index da9f06da789..0cbed1a98ac 100644 --- a/content/es/monitors/types/event.md +++ b/content/es/monitors/types/event.md @@ -4,7 +4,7 @@ aliases: - /es/monitors/create/types/event/ description: Monitor de eventos recopilados por Datadog further_reading: -- link: /service_management/events/ +- link: /events/ tag: Documentación text: Descripción general de gestión de eventos - link: /monitors/notify/ @@ -94,7 +94,7 @@ La variable de plantilla es `{{event.tags.env}}`. El resultado de utilizar esta {{< partial name="whats-next/whats-next.html" >}} [1]: https://app.datadoghq.com/monitors#create/event -[2]: /es/service_management/events/explorer/searching +[2]: /es/events/explorer/searching [3]: /es/help/ [4]: /es/monitors/configuration/#advanced-alert-conditions [5]: /es/monitors/notify/ \ No newline at end of file diff --git a/content/es/reference_tables/_index.md b/content/es/reference_tables/_index.md index a570ce8b9f5..a018c38a6be 100644 --- a/content/es/reference_tables/_index.md +++ b/content/es/reference_tables/_index.md @@ -14,7 +14,7 @@ further_reading: - link: /sheets/#lookup tag: Documentación text: Consulta de hojas -- link: /service_management/events/pipelines_and_processors/lookup_processor/ +- link: /events/pipelines_and_processors/lookup_processor/ tag: Documentación text: Procesador de búsqueda de eventos - link: '/cloud_cost_management/tag_pipelines/#map-multiple-tags' diff --git a/content/es/service_management/events/_index.md b/content/es/service_management/events/_index.md index 47517fa2020..97e0405f9c9 100644 --- a/content/es/service_management/events/_index.md +++ b/content/es/service_management/events/_index.md @@ -7,7 +7,7 @@ further_reading: - link: /api/latest/events/ tag: Documentación text: API de eventos de Datadog -- link: /service_management/events/guides/recommended_event_tags/ +- link: /events/guides/recommended_event_tags/ tag: Documentación text: Prácticas recomendadas para etiquetar eventos - link: https://www.datadoghq.com/blog/identify-sensitive-data-leakage-in-apm-rum-with-sensitive-data-scanner/ @@ -20,7 +20,7 @@ is_beta: true title: Event Management --- -{{< img src="service_management/events/correlation/event_management.png" alt="¿Qué es Event Management?" style="width:100%;" >}} +{{< img src="events/correlation/event_management.png" alt="¿Qué es Event Management?" style="width:100%;" >}} ## Información general @@ -31,11 +31,11 @@ La recopilación de eventos es compatible con más de 100 integraciones de Data ## Componentes {{< whatsnext desc="Características de Event Management:">}} - {{< nextlink href="/service_management/events/ingest/" >}}Ingesta de eventos: aprende a enviar eventos a Datadog{{< /nextlink >}} - {{< nextlink href="/service_management/events/pipelines_and_processors/">}}Pipelines y procesadores: enriquece y normaliza tus eventos{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/" >}}Events Explorer: visualiza, busca y envía notificaciones de eventos que llegan a Datadog{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/usage/" >}}Uso de eventos: analiza, investiga y monitoriza eventos {{< /nextlink >}} - {{< nextlink href="/service_management/events/correlation/" >}}Correlación: reduce la fatiga de alertas y la cantidad de tickets/notificaciones que recibes {{< /nextlink >}} + {{< nextlink href="/events/ingest/" >}}Ingesta de eventos: aprende a enviar eventos a Datadog{{< /nextlink >}} + {{< nextlink href="/events/pipelines_and_processors/">}}Pipelines y procesadores: enriquece y normaliza tus eventos{{< /nextlink >}} + {{< nextlink href="/events/explorer/" >}}Events Explorer: visualiza, busca y envía notificaciones de eventos que llegan a Datadog{{< /nextlink >}} + {{< nextlink href="/events/guides/usage/" >}}Uso de eventos: analiza, investiga y monitoriza eventos {{< /nextlink >}} + {{< nextlink href="/events/correlation/" >}}Correlación: reduce la fatiga de alertas y la cantidad de tickets/notificaciones que recibes {{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/es/service_management/events/correlation/_index.md b/content/es/service_management/events/correlation/_index.md index 8b68d9d01b1..0758e7c8d62 100644 --- a/content/es/service_management/events/correlation/_index.md +++ b/content/es/service_management/events/correlation/_index.md @@ -6,7 +6,7 @@ algolia: - patrón de correlación disable_toc: false further_reading: -- link: service_management/events/ +- link: events/ tag: Documentación text: Event Management - link: service_management/case_management/ @@ -23,9 +23,9 @@ La correlación de eventos agrupa los eventos en función de sus relaciones o de * Hacer que todos los equipos afectados sean conscientes de un único problema en lugar de trabajar en silos {{< whatsnext desc="Comienza con:">}} - {{< nextlink href="/service_management/events/correlation/configuration" >}}Correlación: comienza con nuestros dos tipos diferentes de correlación{{< /nextlink >}} - {{< nextlink href="/service_management/events/correlation/triage_and_notify/" >}}Clasificación y notificación: consulta, clasifica y recibe notificaciones o tickets sobre las correlaciones que se han creado para ti{{< /nextlink >}} - {{< nextlink href="/service_management/events/correlation/analytics/" >}}Análisis: analiza e investiga las métricas de las correlaciones, por ejemplo, el número de casos asignados o la cantidad por servicio, entre otras cosas {{< /nextlink >}} + {{< nextlink href="/events/correlation/configuration" >}}Correlación: comienza con nuestros dos tipos diferentes de correlación{{< /nextlink >}} + {{< nextlink href="/events/correlation/triage_and_notify/" >}}Clasificación y notificación: consulta, clasifica y recibe notificaciones o tickets sobre las correlaciones que se han creado para ti{{< /nextlink >}} + {{< nextlink href="/events/correlation/analytics/" >}}Análisis: analiza e investiga las métricas de las correlaciones, por ejemplo, el número de casos asignados o la cantidad por servicio, entre otras cosas {{< /nextlink >}} {{< /whatsnext >}} ## Referencias adicionales diff --git a/content/es/service_management/events/correlation/analytics.md b/content/es/service_management/events/correlation/analytics.md index 92b4aaf8dce..1d05ef4d479 100644 --- a/content/es/service_management/events/correlation/analytics.md +++ b/content/es/service_management/events/correlation/analytics.md @@ -1,6 +1,6 @@ --- further_reading: -- link: service_management/events/correlation/ +- link: events/correlation/ tag: Documentación text: Más información sobre la correlación de eventos title: Análisis de casos y eventos @@ -13,7 +13,7 @@ Realiza un seguimiento de la carga de trabajo de los equipos mediante gráficos ## Métricas de casos -{{< img src="service_management/events/correlation/case_analytics.png" alt="Configurar análisis de casos" style="width:100%;" >}} +{{< img src="events/correlation/case_analytics.png" alt="Configurar análisis de casos" style="width:100%;" >}} Puedes consultar los análisis de caso en una variedad de widgets de gráficos para analizar la productividad del equipo e identificar patrones en los problemas. Visualiza gráficos analíticos tanto en dashboards como notebooks. Para empezar, en la configuración del widget, selecciona **Cases** (Casos) en el menú desplegable de la fuente de datos en la sección *Graph your data* (Graficar tus datos). @@ -34,7 +34,7 @@ Los siguientes widgets admiten análisis de casos: Desglosa métricas de eventos por fuente, host, servicio, etc. Averigua de dónde proceden tus alertas problemáticas, y si tu carga operativa aumenta o disminuye con el tiempo. -{{< img src="service_management/events/correlation/event_analytics.png" alt="Configurar análisis de eventos" style="width:100%;" >}} +{{< img src="events/correlation/event_analytics.png" alt="Configurar análisis de eventos" style="width:100%;" >}} Para empezar, en la configuración del widget, selecciona **Events** (Eventos) en el menú desplegable de fuente de datos, en la sección *Graph your data* (Graficar tus datos). diff --git a/content/es/service_management/events/correlation/configuration.md b/content/es/service_management/events/correlation/configuration.md index 943d7746b35..f764be9c966 100644 --- a/content/es/service_management/events/correlation/configuration.md +++ b/content/es/service_management/events/correlation/configuration.md @@ -1,9 +1,9 @@ --- further_reading: -- link: service_management/events/correlation/triage_and_notify +- link: events/correlation/triage_and_notify tag: Documentación text: Aprender a clasificar y notificar los casos -- link: service_management/events/correlation/analytics +- link: events/correlation/analytics tag: Documentación text: Análisis de casos title: Configuración diff --git a/content/es/service_management/events/correlation/intelligent.md b/content/es/service_management/events/correlation/intelligent.md index c84ef110e86..8f2172da4c7 100644 --- a/content/es/service_management/events/correlation/intelligent.md +++ b/content/es/service_management/events/correlation/intelligent.md @@ -1,6 +1,6 @@ --- further_reading: -- link: service_management/events/correlation/triage_and_notify +- link: events/correlation/triage_and_notify tag: Documentación text: Más información sobre la clasificación y notificación de casos title: Correlación inteligente @@ -16,17 +16,17 @@ Para empezar: 1. Desde ahí, puedes previsualizar las correlaciones inteligentes que se crean desde tu organización. -{{< img src="service_management/events/correlation/intelligent/intelligent_config_updated.png" alt="Configurar la correlación inteligente" style="width:100%;" >}} +{{< img src="events/correlation/intelligent/intelligent_config_updated.png" alt="Configurar la correlación inteligente" style="width:100%;" >}} ## Recibir tu primer caso -{{< img src="service_management/events/correlation/intelligent/intelligent_project.png" alt="Gestión de eventos - Correlación inteligente" style="width:100%;" >}} +{{< img src="events/correlation/intelligent/intelligent_project.png" alt="Gestión de eventos - Correlación inteligente" style="width:100%;" >}} Cuando estés en [Correlaciones de eventos][3], busca un proyecto llamado **Correlación Inteligente**. Desde este proyecto, puedes ver los casos creados por la correlación inteligente. La correlación inteligente genera casos automáticamente después de encontrar alertas relacionadas: -{{< img src="service_management/events/correlation/intelligent/intelligent_correlation.png" alt="Página de detalles de casos del caso creado a partir de la correlación inteligente, donde se muestra las alertas relacionadas en la pestaña Investigación" style="width:100%;" >}} +{{< img src="events/correlation/intelligent/intelligent_correlation.png" alt="Página de detalles de casos del caso creado a partir de la correlación inteligente, donde se muestra las alertas relacionadas en la pestaña Investigación" style="width:100%;" >}} diff --git a/content/es/service_management/events/correlation/patterns.md b/content/es/service_management/events/correlation/patterns.md index 09db27582e9..c9632f3c695 100644 --- a/content/es/service_management/events/correlation/patterns.md +++ b/content/es/service_management/events/correlation/patterns.md @@ -1,6 +1,6 @@ --- further_reading: -- link: service_management/events/correlation/triage_and_notify +- link: events/correlation/triage_and_notify tag: Documentación text: Más información sobre la clasificación y notificación de casos title: Correlación basada en patrones @@ -12,7 +12,7 @@ La correlación basada en patrones te permite controlar cómo se correlacionan l Para empezar, Datadog sugiere automáticamente [correlaciones basadas en patrones][1], en función de tu entorno. Haz clic en cualquiera de las recomendaciones para abrir la página de configuración correspondiente al patrón recomendado. Los campos de configuración ya están rellenados. -{{< img src="service_management/events/correlation/pattern/recommended_patterns_preview.png" alt="Patrones de correlación recomendados con el panel de vista previa que muestra los posibles casos que crearía el patrón" style="width:100%;" >}} +{{< img src="events/correlation/pattern/recommended_patterns_preview.png" alt="Patrones de correlación recomendados con el panel de vista previa que muestra los posibles casos que crearía el patrón" style="width:100%;" >}} ## Crear un patrón @@ -23,7 +23,7 @@ Para crear un patrón: 1. Puedes ajustar un patrón sugerido haciendo clic en **+ Continue With Pattern** (+ Continuar con el patrón). Esto le llevará a la página de configuración para realizar ajustes adicionales. También puedes crear tu propio patrón haciendo clic en **+ Personalize From Scratch** (+ Personalizar desde cero). Primero, los eventos se deduplican en alertas en función de la clave de agregación de eventos. Luego, las alertas se correlacionan con un caso en función de la configuración. -{{< img src="service_management/events/correlation/correlation_helper.mp4" alt="Cuando los eventos coinciden con las fuentes definidas, se filtran y se deduplican en alertas. Las alertas se correlacionan en función de los atributos de agrupación y sus eventos se deduplican dentro del periodo de tiempo definido, antes de que el proceso se repita en un nuevo caso. Puedes modificar esta configuración en los parámetros." vídeo=true >}} +{{< img src="events/correlation/correlation_helper.mp4" alt="Cuando los eventos coinciden con las fuentes definidas, se filtran y se deduplican en alertas. Las alertas se correlacionan en función de los atributos de agrupación y sus eventos se deduplican dentro del periodo de tiempo definido, antes de que el proceso se repita en un nuevo caso. Puedes modificar esta configuración en los parámetros." vídeo=true >}} Para obtener más información sobre cómo enviar eventos con claves de agregación, consulta el [envío de eventos a Datadog][5]. Los eventos sin claves de agregación se deduplican en una única alerta dentro del periodo de tiempo. ### Patrones sugeridos @@ -67,7 +67,7 @@ Previsualiza los posibles patrones y casos que tu configuración podría crear. Utiliza estos datos para previsualizar el impacto de tus correlaciones y comprender el resultado esperado de un patrón. -{{< img src="service_management/events/correlation/pattern/preview_pattern_output.png" alt="Configuración de una correlación basada en patrones donde se resalta el panel de vista previa que muestra el número de eventos ingeridos que coinciden con la configuración, la cantidad de esos eventos que generan alertas, la cantidad de deduplicación que podría ocurrir y el número de casos que resultarían." style="width:100%;" >}} +{{< img src="events/correlation/pattern/preview_pattern_output.png" alt="Configuración de una correlación basada en patrones donde se resalta el panel de vista previa que muestra el número de eventos ingeridos que coinciden con la configuración, la cantidad de esos eventos que generan alertas, la cantidad de deduplicación que podría ocurrir y el número de casos que resultarían." style="width:100%;" >}} **Nota**: El título por defecto en la vista previa del caso es la primera alerta en correlación. Luego de guardar un patrón, el título de caso de la gestión de eventos se genera de forma inteligente. @@ -86,6 +86,6 @@ Después de actualizar un patrón existente, todos los casos activos se dejarán [1]: https://app.datadoghq.com/event/correlation [2]: https://app.datadoghq.com/event/correlation/rule/new -[3]: /es/service_management/events/explorer/facets/#create-a-facet -[4]: /es/service_management/events/explorer/facets -[5]: /es/service_management/events/ingest/ \ No newline at end of file +[3]: /es/events/explorer/facets/#create-a-facet +[4]: /es/events/explorer/facets +[5]: /es/events/ingest/ \ No newline at end of file diff --git a/content/es/service_management/events/explorer/_index.md b/content/es/service_management/events/explorer/_index.md index fde7b250863..0531abd7f93 100644 --- a/content/es/service_management/events/explorer/_index.md +++ b/content/es/service_management/events/explorer/_index.md @@ -12,19 +12,19 @@ further_reading: title: Events Explorer --- -{{< img src="service_management/events/events-explorer.mp4" alt="Ordenar eventos por atributos y explorar el análisis" video=true >}} +{{< img src="events/events-explorer.mp4" alt="Ordenar eventos por atributos y explorar el análisis" video=true >}} Utiliza el Events Explorer para agregar y ver los eventos que llegan a Datadog. Agrupa o filtra eventos por atributo y represéntalos gráficamente con el análisis de eventos. Utiliza la sintaxis de consulta para filtrar eventos mediante operadores booleanos y comodines. {{< whatsnext desc="Características del Events Explorer:" >}} - {{< nextlink href="/service_management/events/explorer/searching" >}}Búsqueda{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/navigate" >}}Navegar por el Explorer{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/customization" >}}Personalización{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/facets" >}}Facetas{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/attributes" >}}Atributos{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/notifications" >}}Enviar notificaciones{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/analytics" >}}Análisis{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/saved_views" >}}Vistas guardadas{{< /nextlink >}} + {{< nextlink href="/events/explorer/searching" >}}Búsqueda{{< /nextlink >}} + {{< nextlink href="/events/explorer/navigate" >}}Navegar por el Explorer{{< /nextlink >}} + {{< nextlink href="/events/explorer/customization" >}}Personalización{{< /nextlink >}} + {{< nextlink href="/events/explorer/facets" >}}Facetas{{< /nextlink >}} + {{< nextlink href="/events/explorer/attributes" >}}Atributos{{< /nextlink >}} + {{< nextlink href="/events/explorer/notifications" >}}Enviar notificaciones{{< /nextlink >}} + {{< nextlink href="/events/explorer/analytics" >}}Análisis{{< /nextlink >}} + {{< nextlink href="/events/explorer/saved_views" >}}Vistas guardadas{{< /nextlink >}} {{< /whatsnext >}} ## Lectura adicional diff --git a/content/es/service_management/events/explorer/analytics.md b/content/es/service_management/events/explorer/analytics.md index 38a782555de..add3e57ae98 100644 --- a/content/es/service_management/events/explorer/analytics.md +++ b/content/es/service_management/events/explorer/analytics.md @@ -17,10 +17,10 @@ Puedes exportar visualizaciones de análisis para crear widgets en un dashboard Utiliza la consulta para controlar lo que se muestra en Events Analytics: 1. Elige un atributo o etiqueta para graficarlo, y añádelo como una faceta. Al crear gráficas de una faceta se muestra el conteo único de la variable. - {{< img src="service_management/events/explorer/facet-to-graph.png" alt="Se muestra la lista de facetas que se pueden graficar." style="width:100%;" >}} + {{< img src="events/explorer/facet-to-graph.png" alt="Se muestra la lista de facetas que se pueden graficar." style="width:100%;" >}} 2. Utiliza una faceta para agrupar tu gráfica. Debes añadir un atributo como faceta para poder utilizarlo aquí. - {{< img src="service_management/events/explorer/split-graph.png" alt="Se muestra la lista de facetas por las que puedes agrupar datos." style="width:100%;" >}} + {{< img src="events/explorer/split-graph.png" alt="Se muestra la lista de facetas por las que puedes agrupar datos." style="width:100%;" >}} 3. Elige el intervalo de tiempo de tu gráfica. Cambiar el período de tiempo general modifica la lista de los valores de intervalo de tiempo disponibles. Puedes mostrar los resultados en forma de serie temporal, tabla o lista principal. - {{< img src="service_management/events/explorer/time-interval.png" alt="Se muestra la lista de posibles intervalos de tiempo, incluido el predeterminado, 5 segundos." style="width:100%;" >}} + {{< img src="events/explorer/time-interval.png" alt="Se muestra la lista de posibles intervalos de tiempo, incluido el predeterminado, 5 segundos." style="width:100%;" >}} 4. Elige mostrar los valores superiores o inferiores en función de la medida seleccionada. - {{< img src="service_management/events/explorer/display-values.png" alt="Elige mostrar los valores desde la parte superior o inferior." style="width:100%;" >}} \ No newline at end of file + {{< img src="events/explorer/display-values.png" alt="Elige mostrar los valores desde la parte superior o inferior." style="width:100%;" >}} \ No newline at end of file diff --git a/content/es/service_management/events/explorer/attributes.md b/content/es/service_management/events/explorer/attributes.md index 0e8c52d6017..5bf1972cdcb 100644 --- a/content/es/service_management/events/explorer/attributes.md +++ b/content/es/service_management/events/explorer/attributes.md @@ -1,7 +1,7 @@ --- disable_toc: false further_reading: -- link: /service_management/events/explorer/facets +- link: /events/explorer/facets tag: Documentación text: Más información sobre las facetas de eventos - link: logs/processing/pipelines @@ -38,4 +38,4 @@ Para crear una faceta en una etiqueta que tenga la misma clave que un atributo r {{< partial name="whats-next/whats-next.html" >}} [1]: /es/logs/log_configuration/processors/?tab=ui#remapper -[2]: /es/service_management/events/explorer/facets \ No newline at end of file +[2]: /es/events/explorer/facets \ No newline at end of file diff --git a/content/es/service_management/events/explorer/navigate.md b/content/es/service_management/events/explorer/navigate.md index 42cb53f59b2..15855f147cc 100644 --- a/content/es/service_management/events/explorer/navigate.md +++ b/content/es/service_management/events/explorer/navigate.md @@ -2,7 +2,7 @@ title: Navegar por el Explorer --- -{{< img src="service_management/events/explorer/navigate.png" alt="Cómo navegar por el Events Explorer" style="width:100%;" >}} +{{< img src="events/explorer/navigate.png" alt="Cómo navegar por el Events Explorer" style="width:100%;" >}} ## Información general @@ -14,7 +14,7 @@ Haz clic en cualquier evento en el Events Explorer para abrir el panel lateral d ### Pestaña de atributos -{{< img src="service_management/events/explorer/event-attribute.png" alt="Un ejemplo de la pestaña Atributos del evento" style="width:100%;" >}} +{{< img src="events/explorer/event-attribute.png" alt="Un ejemplo de la pestaña Atributos del evento" style="width:100%;" >}} La pestaña de atributos del panel lateral muestra los atributos del evento como JSON. Haz clic en un atributo para añadirlo o excluirlo de la consulta existente, o a fin de añadir una columna para este atributo. diff --git a/content/es/service_management/events/explorer/saved_views.md b/content/es/service_management/events/explorer/saved_views.md index dbd16989e5f..433323cd89e 100644 --- a/content/es/service_management/events/explorer/saved_views.md +++ b/content/es/service_management/events/explorer/saved_views.md @@ -1,6 +1,6 @@ --- further_reading: -- link: /service_management/events/explorer/ +- link: /events/explorer/ tag: Documentación text: Más información sobre Events Explorer title: Vistas guardadas @@ -46,5 +46,5 @@ En la entrada de la vista predeterminada del panel **Views** (Vistas), puedes: {{< partial name="whats-next/whats-next.html" >}} [1]: https://app.datadoghq.com/event/explorer -[2]: /es/service_management/events/explorer/searching -[3]: /es/service_management/events/explorer/searching \ No newline at end of file +[2]: /es/events/explorer/searching +[3]: /es/events/explorer/searching \ No newline at end of file diff --git a/content/es/service_management/events/guides/_index.md b/content/es/service_management/events/guides/_index.md index af51abb5180..bbb2c30fe1c 100644 --- a/content/es/service_management/events/guides/_index.md +++ b/content/es/service_management/events/guides/_index.md @@ -10,7 +10,7 @@ cascade: subcategory: Guías de eventos disable_toc: true further_reading: -- link: /service_management/events/explorer/ +- link: /events/explorer/ tag: Documentación text: Datadog Events Explorer - link: /monitors/types/event/ @@ -23,22 +23,22 @@ title: Guías de eventos Un evento representa cualquier registro de actividad destacable para los ingenieros (desarrollo, operaciones y seguridad). {{< whatsnext desc="Envía tus eventos personalizados a Datadog:">}} - {{< nextlink href="/service_management/events/guides/agent/" >}}Check del Agent personalizado{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/dogstatsd/" >}}DogStatsD{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/email/" >}}Correo electrónico{{< /nextlink >}} + {{< nextlink href="/events/guides/agent/" >}}Check del Agent personalizado{{< /nextlink >}} + {{< nextlink href="/events/guides/dogstatsd/" >}}DogStatsD{{< /nextlink >}} + {{< nextlink href="/events/guides/email/" >}}Correo electrónico{{< /nextlink >}} {{< nextlink href="/api/v1/events/#post-an-event" >}}API de Datadog{{< /nextlink >}} {{< /whatsnext >}} {{< whatsnext desc="Asegúrate de que tus eventos se encuentren etiquetados:">}} - {{< nextlink href="/service_management/events/guides/recommended_event_tags/" >}}Prácticas recomendadas para el etiquetado de eventos{{< /nextlink >}} + {{< nextlink href="/events/guides/recommended_event_tags/" >}}Prácticas recomendadas para el etiquetado de eventos{{< /nextlink >}} {{< /whatsnext >}} {{< whatsnext desc="Obtén más información sobre los casos de uso de Event Management:">}} - {{< nextlink href="/service_management/events/guides/usage" >}}Casos de uso para eventos{{< /nextlink >}} + {{< nextlink href="/events/guides/usage" >}}Casos de uso para eventos{{< /nextlink >}} {{< /whatsnext >}} {{< whatsnext desc="Otras guías:">}} - {{< nextlink href="/service_management/events/guides/migrating_to_new_events_features/" >}}Migración a las características de eventos nuevas{{< /nextlink >}} + {{< nextlink href="/events/guides/migrating_to_new_events_features/" >}}Migración a las características de eventos nuevas{{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/es/service_management/events/guides/dogstatsd.md b/content/es/service_management/events/guides/dogstatsd.md index 59450760c0b..9a8e56360b8 100644 --- a/content/es/service_management/events/guides/dogstatsd.md +++ b/content/es/service_management/events/guides/dogstatsd.md @@ -212,4 +212,4 @@ $statsd->event('An error occurred.', [1]: /es/developers/dogstatsd/ -[2]: /es/service_management/events/ \ No newline at end of file +[2]: /es/events/ \ No newline at end of file diff --git a/content/es/service_management/events/guides/migrating_to_new_events_features.md b/content/es/service_management/events/guides/migrating_to_new_events_features.md index 1fcedca0bd9..a1edcfb3c1f 100644 --- a/content/es/service_management/events/guides/migrating_to_new_events_features.md +++ b/content/es/service_management/events/guides/migrating_to_new_events_features.md @@ -45,18 +45,18 @@ El Events Explorer muestra los eventos más recientes generados por tu infraestr ### Event Analytics -{{< img src="service_management/events/events-analytics.png" alt="Visualización de Events Analytics filtrada por 'source:cloudtrail'" >}} +{{< img src="events/events-analytics.png" alt="Visualización de Events Analytics filtrada por 'source:cloudtrail'" >}} Además de ver y buscar eventos en el Explorer, ahora puedes realizar gráficas como la serie temporal, lista principal o tabla y agrupar el número de eventos para una consulta determinada. Consulta la sección de [Event Analytics][2] para obtener más información. También puedes [generar métricas][3] con retención de 15 meses a partir de cualquier consulta de búsqueda de eventos para crear monitores y alertas basados en eventos históricos. -{{< img src="service_management/events/generate-metrics.png" alt="Imagen de métricas con la consulta de búsqueda de eventos." >}} +{{< img src="events/generate-metrics.png" alt="Imagen de métricas con la consulta de búsqueda de eventos." >}} ### Graficar eventos en dashboards -{{< img src="service_management/events/graph-events.png" alt="Events Analytics">}} +{{< img src="events/graph-events.png" alt="Events Analytics">}} Ahora puedes graficar eventos para una consulta determinada en tus dashboards como una gráfica de serie temporal, valor de consulta, lista principal, tabla y mucho más. @@ -68,7 +68,7 @@ Los monitores de eventos se han adaptado para utilizar el mismo conjunto estanda Al crear monitores de eventos, el campo de búsqueda de consultas nuevo utiliza la función de autocompletar, en lugar de la consulta heredada para completar espacios en blanco. -{{< img src="service_management/events/guides/events-migration-monitor-new.png" alt="Interfaz de usuario nueva para la sintaxis de consulta de monitores" style="width:100%;" >}} +{{< img src="events/guides/events-migration-monitor-new.png" alt="Interfaz de usuario nueva para la sintaxis de consulta de monitores" style="width:100%;" >}} La búsqueda de consultas nueva te permite utilizar consultas complejas en monitores de eventos con funcionalidades nuevas, como operadores booleanos o comodines. @@ -194,10 +194,10 @@ Los monitores de eventos heredados no admiten el rollup de cardinalidad. {{< partial name="whats-next/whats-next.html" >}} -[1]: /es/service_management/events/explorer -[2]: /es/service_management/events/explorer/analytics -[3]: /es/service_management/events/usage/#custom-metrics +[1]: /es/events/explorer +[2]: /es/events/explorer/analytics +[3]: /es/events/usage/#custom-metrics [4]: https://app.datadoghq.com/dash/integration/30532/monitor-notifications-overview -[5]: /es/service_management/events/guides/new_events_sources/ +[5]: /es/events/guides/new_events_sources/ [6]: /es/help/ [7]: /es/api/latest/monitors/#create-a-monitor \ No newline at end of file diff --git a/content/es/service_management/events/guides/recommended_event_tags.md b/content/es/service_management/events/guides/recommended_event_tags.md index 95166e19c4c..3181f9af8a4 100644 --- a/content/es/service_management/events/guides/recommended_event_tags.md +++ b/content/es/service_management/events/guides/recommended_event_tags.md @@ -43,7 +43,7 @@ Puedes añadir los siguientes atributos básicos a tus eventos: {{< partial name="whats-next/whats-next.html" >}} [1]: /es/getting_started/tagging/unified_service_tagging -[2]: /es/service_management/events/explorer +[2]: /es/events/explorer [3]: /es/api/latest/events/#post-an-event [4]: /es/getting_started/monitors/#notify-your-services-and-your-team-members [5]: /es/getting_started/tagging/assigning_tags diff --git a/content/es/service_management/events/guides/usage.md b/content/es/service_management/events/guides/usage.md index d570a9ec9e6..deb3186d096 100644 --- a/content/es/service_management/events/guides/usage.md +++ b/content/es/service_management/events/guides/usage.md @@ -1,11 +1,11 @@ --- aliases: -- /es/service_management/events/usage +- /es/events/usage further_reading: - link: /logs/log_configuration/processors/ tag: Documentación text: Más información sobre pipelines de procesamiento -- link: /service_management/events/explorer/ +- link: /events/explorer/ tag: Documentación text: Clasificar eventos con Events Explorer title: Uso de eventos @@ -15,7 +15,7 @@ title: Uso de eventos [Genera métricas][5] con una retención de 15 meses a partir de cualquier consulta de búsqueda de eventos para crear y monitorizar eventos históricos y alertas. Para la agregación, se tienen en cuenta los eventos ingeridos con una marca de tiempo dentro de los últimos 20 minutos. Para obtener más información, consulta [Event Analytics][6]. -{{< img src="service_management/events/guides/usage/generate-metrics.png" alt="Imagen de métricas con la consulta de búsqueda de eventos." >}} +{{< img src="events/guides/usage/generate-metrics.png" alt="Imagen de métricas con la consulta de búsqueda de eventos." >}} ## Ejemplos de qué hacer con eventos @@ -31,7 +31,7 @@ Puedes utilizar eventos como fuente de datos en los [widgets de gráficos][8] pa #### Superposiciones -{{< img src="service_management/events/guides/usage/event_overlays.png" alt="Opción para ver superposiciones de eventos en un dashboard de ejemplo" style="width:100%;" >}} +{{< img src="events/guides/usage/event_overlays.png" alt="Opción para ver superposiciones de eventos en un dashboard de ejemplo" style="width:100%;" >}} Las superposiciones permiten visualizar eventos sobre tus gráficos. Utiliza la característica del dashboard [Event Overlays][10] (Superposiciones de eventos) para identificar cuándo un cambio reciente está generando problemas de rendimiento en tu aplicación o servicios y encontrar el origen del problema. @@ -49,8 +49,8 @@ Envía alertas de monitor y notificaciones basadas en consultas de eventos signi [3]: https://app.datadoghq.com/event/pipelines [4]: /es/help/ [5]: https://app.datadoghq.com/event/configuration/generate-metrics -[6]: /es/service_management/events/explorer/analytics -[7]: /es/service_management/events/explorer/ +[6]: /es/events/explorer/analytics +[7]: /es/events/explorer/ [8]: /es/dashboards/widgets/alert_graph/ [9]: https://app.datadoghq.com/dash/integration/30532/monitor-notifications-overview [10]: /es/dashboards/change_overlays/ diff --git a/content/es/service_management/events/ingest.md b/content/es/service_management/events/ingest.md index 8bff8cb010b..e774aef1425 100644 --- a/content/es/service_management/events/ingest.md +++ b/content/es/service_management/events/ingest.md @@ -16,9 +16,9 @@ También puedes enviar tus propio eventos personalizados mediante la API de Data {{< whatsnext desc="Envía tus eventos personalizados a Datadog:">}} {{< nextlink href="/api/latest/events/#post-an-event" >}}API de Datadog{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/agent/" >}}Check del Agent personalizado{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/email/" >}}Correo electrónico{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/dogstatsd/" >}}DogStatsD{{< /nextlink >}} + {{< nextlink href="/events/guides/agent/" >}}Check del Agent personalizado{{< /nextlink >}} + {{< nextlink href="/events/guides/email/" >}}Correo electrónico{{< /nextlink >}} + {{< nextlink href="/events/guides/dogstatsd/" >}}DogStatsD{{< /nextlink >}} {{< nextlink href="/integrations/guide/events-from-sns-emails/" >}}Correos electrónicos de Amazon SNS{{< /nextlink >}} {{< nextlink href="/logs/guide/sending-events-and-logs-to-datadog-with-amazon-eventbridge-api-destinations/#configuration" >}}Destinos de la API de Amazon EventBridge{{< /nextlink >}} {{< /whatsnext >}} \ No newline at end of file diff --git a/content/es/service_management/events/pipelines_and_processors/_index.md b/content/es/service_management/events/pipelines_and_processors/_index.md index 8a8faee4971..4965d4a5385 100644 --- a/content/es/service_management/events/pipelines_and_processors/_index.md +++ b/content/es/service_management/events/pipelines_and_processors/_index.md @@ -1,9 +1,9 @@ --- further_reading: -- link: /service_management/events/ +- link: /events/ tag: Documentación text: Gestión de eventos -- link: /service_management/events/correlation/ +- link: /events/correlation/ tag: Documentación text: Correlación de eventos title: Pipelines y procesadores @@ -58,13 +58,13 @@ Puedes añadir procesadores después de crear un pipeline. Los procesadores disp [1]: https://app.datadoghq.com/event/pipelines [2]: https://app.datadoghq.com/event/explorer -[3]: /es/service_management/events/pipelines_and_processors/aggregation_key -[4]: /es/service_management/events/pipelines_and_processors/arithmetic_processor -[5]: /es/service_management/events/pipelines_and_processors/date_remapper -[6]: /es/service_management/events/pipelines_and_processors/category_processor -[7]: /es/service_management/events/pipelines_and_processors/grok_parser -[8]: /es/service_management/events/pipelines_and_processors/lookup_processor -[9]: /es/service_management/events/pipelines_and_processors/remapper -[10]: /es/service_management/events/pipelines_and_processors/service_remapper -[11]: /es/service_management/events/pipelines_and_processors/status_remapper -[12]: /es/service_management/events/pipelines_and_processors/string_builder_processor \ No newline at end of file +[3]: /es/events/pipelines_and_processors/aggregation_key +[4]: /es/events/pipelines_and_processors/arithmetic_processor +[5]: /es/events/pipelines_and_processors/date_remapper +[6]: /es/events/pipelines_and_processors/category_processor +[7]: /es/events/pipelines_and_processors/grok_parser +[8]: /es/events/pipelines_and_processors/lookup_processor +[9]: /es/events/pipelines_and_processors/remapper +[10]: /es/events/pipelines_and_processors/service_remapper +[11]: /es/events/pipelines_and_processors/status_remapper +[12]: /es/events/pipelines_and_processors/string_builder_processor \ No newline at end of file diff --git a/content/es/service_management/events/pipelines_and_processors/aggregation_key.md b/content/es/service_management/events/pipelines_and_processors/aggregation_key.md index ffcab382d5c..0bb728acb59 100644 --- a/content/es/service_management/events/pipelines_and_processors/aggregation_key.md +++ b/content/es/service_management/events/pipelines_and_processors/aggregation_key.md @@ -21,5 +21,5 @@ El procesador de claves de agregación realiza las siguientes acciones: * Si hay varios valores en la clave de la etiqueta, todos los valores se ordenan alfabéticamente y se concatenan para generar la clave de agregación. * Basándose en estos valores, genera un hash y añade la clave de agregación generada al evento. -[1]: /es/service_management/events/correlation/ +[1]: /es/events/correlation/ [2]: /es/getting_started/tagging/ \ No newline at end of file diff --git a/content/es/service_management/events/pipelines_and_processors/grok_parser.md b/content/es/service_management/events/pipelines_and_processors/grok_parser.md index 1b02497eeb0..ea72bdd3254 100644 --- a/content/es/service_management/events/pipelines_and_processors/grok_parser.md +++ b/content/es/service_management/events/pipelines_and_processors/grok_parser.md @@ -6,7 +6,7 @@ title: Analizador de Grok Crea reglas de Grok personalizadas para analizar el mensaje completo o un atributo específico de tu evento sin formato. Como práctica recomendada, se sugiere utilizar un máximo de 10 reglas de parseo en un procesador de Grok. -{{< img src="service_management/events/grok-parser.png" alt="Ejemplo de parseo 1" style="width:80%;">}} +{{< img src="events/grok-parser.png" alt="Ejemplo de parseo 1" style="width:80%;">}} Haz clic en **Parse My Events** (Analizar mis eventos) a fin de iniciar un conjunto de tres reglas de parseo para los eventos que fluyen a través del pipeline subyacente. Refina la denominación de atributos allí y añade reglas nuevas para otro tipo de eventos si es necesario. Esta característica requiere que los eventos correspondientes se indexen y realmente fluyan. Puedes desactivar o reducir de manera temporal los filtros de exclusión para que funcione. @@ -657,5 +657,5 @@ Si tus eventos contienen caracteres de control ASCII, se serializarán al ingeri [1]: https://github.com/google/re2/wiki/Syntax [2]: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones -[3]: /es/service_management/events/pipelines_and_processors/date_remapper -[4]: /es/service_management/events/pipelines_and_processors/grok_parser/?tab=filters&tabs=filters#matcher-and-filter +[3]: /es/events/pipelines_and_processors/date_remapper +[4]: /es/events/pipelines_and_processors/grok_parser/?tab=filters&tabs=filters#matcher-and-filter diff --git a/content/es/synthetics/explore/_index.md b/content/es/synthetics/explore/_index.md index ee0acefe883..3146d1f2a87 100644 --- a/content/es/synthetics/explore/_index.md +++ b/content/es/synthetics/explore/_index.md @@ -15,7 +15,7 @@ further_reading: - link: /synthetics/explore/results_explorer tag: Documentación text: Más información sobre Synthetic Monitoring y Testing Results Explorer -- link: /service_management/events/explorer +- link: /events/explorer tag: Documentación text: Información sobre el explorador de eventos title: Buscar y gestionar tests Synthetic diff --git a/content/es/synthetics/mobile_app_testing/mobile_app_tests/results.md b/content/es/synthetics/mobile_app_testing/mobile_app_tests/results.md index 4bedecc7956..203c15a10ed 100644 --- a/content/es/synthetics/mobile_app_testing/mobile_app_tests/results.md +++ b/content/es/synthetics/mobile_app_testing/mobile_app_tests/results.md @@ -8,7 +8,7 @@ further_reading: - link: /synthetics/mobile_app_testing/ tag: Documentación text: Más información sobre los tests móviles Synthetic -- link: /service_management/events/explorer +- link: /events/explorer tag: Documentación text: Información sobre el explorador de eventos title: Resultados de tests de aplicaciones móviles diff --git a/content/es/watchdog/faulty_deployment_detection.md b/content/es/watchdog/faulty_deployment_detection.md index 2da610f96fd..a21356abeeb 100644 --- a/content/es/watchdog/faulty_deployment_detection.md +++ b/content/es/watchdog/faulty_deployment_detection.md @@ -42,5 +42,5 @@ Watchdog intenta determinar si la nueva implementación es la causa verosímil d - La tasa de error de la nueva versión no ha sido significativamente superior a la de las versiones anteriores. - Este patrón de error es común durante las implementaciones del servicio, incluso cuando la nueva versión del código no presenta errores. -[2]: /es/service_management/events/explorer +[2]: /es/events/explorer [3]: https://app.datadoghq.com/monitors/create \ No newline at end of file diff --git a/content/fr/administrators_guide/plan.md b/content/fr/administrators_guide/plan.md index 78016c6f71f..1814c62282a 100644 --- a/content/fr/administrators_guide/plan.md +++ b/content/fr/administrators_guide/plan.md @@ -345,7 +345,7 @@ Pendant la phase de [déploiement][41], élaborez une méthodologie détaillée [28]: /fr/integrations/network/ [29]: /fr/network_monitoring/cloud_network_monitoring/ [30]: /fr/software_catalog/ -[31]: /fr/service_management/events/ +[31]: /fr/events/ [32]: /fr/error_tracking/ [33]: /fr/software_catalog/endpoints/ [34]: /fr/agent/fleet_automation/ diff --git a/content/fr/developers/_index.md b/content/fr/developers/_index.md index cddf0595e43..074474ef4d2 100644 --- a/content/fr/developers/_index.md +++ b/content/fr/developers/_index.md @@ -105,7 +105,7 @@ Les [checks custom][11], ou checks custom d'Agent, vous permettent d'envoyer des {{< whatsnext desc="Familiarisez-vous avec les différents types de données que vous pouvez envoyer à Datadog et avec leur méthode d'envoi :" >}} {{< nextlink href="/metrics" >}}Métriques custom : plongez au cœur des métriques custom de Datadog et découvrez les différents types de métriques, ce qu'ils représentent, comment les envoyer et leur rôle au sein de l'écosystème Datadog.{{< /nextlink >}} - {{< nextlink href="service_management/events/guides/" >}}Événements : découvrez comment envoyer des événements à Datadog avec des checks custom d'Agent, DogStatsD ou l'API Datadog.{{< /nextlink >}} + {{< nextlink href="events/guides/" >}}Événements : découvrez comment envoyer des événements à Datadog avec des checks custom d'Agent, DogStatsD ou l'API Datadog.{{< /nextlink >}} {{< nextlink href="/developers/service_checks" >}}Checks de service : apprenez à envoyer le statut de disponibilité d'un service spécifique à Datadog.{{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/fr/developers/dogstatsd/_index.md b/content/fr/developers/dogstatsd/_index.md index 5e0ad6ea283..a02ddbdfaae 100644 --- a/content/fr/developers/dogstatsd/_index.md +++ b/content/fr/developers/dogstatsd/_index.md @@ -578,7 +578,7 @@ DogStatsD et StatsD sont assez semblables. Toutefois, DogStatsD comprend des fon {{< whatsnext desc="">}} {{< nextlink href="/metrics/custom_metrics/dogstatsd_metrics_submission/" >}}Envoyer des métriques à Datadog avec DogStatsD{{< /nextlink >}} -{{< nextlink href="/service_management/events/guides/dogstatsd/" >}}Envoyer des événements à Datadog avec DogStatsD{{< /nextlink >}} +{{< nextlink href="/events/guides/dogstatsd/" >}}Envoyer des événements à Datadog avec DogStatsD{{< /nextlink >}} {{< nextlink href="/developers/service_checks/dogstatsd_service_checks_submission/" >}}Envoyer des checks de service à Datadog avec DogStatsD{{< /nextlink >}} {{< /whatsnext >}} @@ -593,7 +593,7 @@ Si vous souhaitez approfondir vos connaissances sur le format des datagrammes ut [3]: https://hub.docker.com/r/datadog/dogstatsd [4]: https://gcr.io/datadoghq/dogstatsd [5]: /metrics/custom_metrics/ -[6]: /service_management/events/guides/dogstatsd/ +[6]: /events/guides/dogstatsd/ [7]: /developers/service_checks/dogstatsd_service_checks_submission/ [8]: /getting_started/tagging/unified_service_tagging [9]: /developers/dogstatsd/datagram_shell/ diff --git a/content/fr/developers/integrations/agent_integration.md b/content/fr/developers/integrations/agent_integration.md index d6d26b3e4fc..12647cd05ff 100644 --- a/content/fr/developers/integrations/agent_integration.md +++ b/content/fr/developers/integrations/agent_integration.md @@ -483,7 +483,7 @@ Veillez à mettre à jour toutes les références au numéro de version dans la [1]: https://docs.datadoghq.com/fr/agent/ [2]: https://docs.datadoghq.com/fr/metrics/ -[3]: https://docs.datadoghq.com/fr/service_management/events/ +[3]: https://docs.datadoghq.com/fr/events/ [4]: /fr/developers/service_checks/ [5]: https://docs.datadoghq.com/fr/logs/log_collection/agent_checks/ [6]: https://docs.datadoghq.com/fr/agent/guide/integration-management/?tab=linux#install diff --git a/content/fr/events/pipelines_and_processors/grok_parser.md b/content/fr/events/pipelines_and_processors/grok_parser.md index 837dc19ebbc..c546d62042a 100644 --- a/content/fr/events/pipelines_and_processors/grok_parser.md +++ b/content/fr/events/pipelines_and_processors/grok_parser.md @@ -1,6 +1,6 @@ --- aliases: -- /fr/service_management/events/pipelines_and_processors/grok_parser/ +- /fr/events/pipelines_and_processors/grok_parser/ description: Créez des règles grok personnalisées pour analyser le message complet ou des attributs spécifiques des événements bruts en données structurées title: Parser Grok @@ -10,7 +10,7 @@ title: Parser Grok Créez des règles grok personnalisées pour analyser le message complet ou un attribut spécifique de votre événement brut. En tant que meilleure pratique, il est recommandé d'utiliser au maximum 10 règles d'analyse dans un processeur grok. -{{< img src="service_management/events/grok-parser.png" alt="Exemple d'analyse 1" style="width:80%;">}} +{{< img src="events/grok-parser.png" alt="Exemple d'analyse 1" style="width:80%;">}} Cliquez sur **Analyser mes événements** pour démarrer un ensemble de trois règles d'analyse pour les événements circulant dans le pipeline sous-jacent. Affinez la nomination des attributs à partir de là, et ajoutez de nouvelles règles pour d'autres types d'événements si nécessaire. Cette fonctionnalité nécessite que les événements correspondants soient indexés et effectivement en cours de traitement ; vous pouvez temporairement désactiver ou réduire les filtres d'exclusion pour que cela fonctionne pour vous. diff --git a/content/fr/getting_started/application/_index.md b/content/fr/getting_started/application/_index.md index ffd1e9e5a14..ff693bfa8d6 100644 --- a/content/fr/getting_started/application/_index.md +++ b/content/fr/getting_started/application/_index.md @@ -69,7 +69,7 @@ Consultez la section [Hostmap][9] pour en savoir plus. ## Événements -{{< img src="service_management/events/explorer/events-overview.png" alt="Events Explorer" style="width:100%;" >}} +{{< img src="events/explorer/events-overview.png" alt="Events Explorer" style="width:100%;" >}} La vue [Events Explorer][10] affiche les événements les plus récents générés par votre infrastructure et vos services. @@ -158,8 +158,8 @@ L'[application mobile Datadog][23] est disponible dans [l'App Store d'Apple][24 [7]: /fr/infrastructure/ [8]: /fr/getting_started/tagging/ [9]: /fr/infrastructure/hostmap/ -[10]: /fr/service_management/events/ -[11]: /fr/service_management/events/explorer/analytics +[10]: /fr/events/ +[11]: /fr/events/explorer/analytics [12]: /fr/dashboards/ [13]: /fr/dashboards/#screenboards [14]: /fr/dashboards/functions/arithmetic/ diff --git a/content/fr/getting_started/tagging/using_tags.md b/content/fr/getting_started/tagging/using_tags.md index 2b1224417ed..270e79a9d4f 100644 --- a/content/fr/getting_started/tagging/using_tags.md +++ b/content/fr/getting_started/tagging/using_tags.md @@ -404,7 +404,7 @@ Consultez la liste de liens ci-dessous pour accéder aux rubriques correspondant {{< partial name="whats-next/whats-next.html" >}} [1]: /fr/getting_started/tagging/assigning_tags/ -[2]: /fr/service_management/events/explorer +[2]: /fr/events/explorer [3]: /fr/integrations/ [4]: /fr/infrastructure/hostmap/ [5]: /fr/infrastructure/ diff --git a/content/fr/integrations/guide/events-from-sns-emails.md b/content/fr/integrations/guide/events-from-sns-emails.md index 0faed56a1f3..72cfa819f87 100644 --- a/content/fr/integrations/guide/events-from-sns-emails.md +++ b/content/fr/integrations/guide/events-from-sns-emails.md @@ -40,7 +40,7 @@ Configurez des alertes basées sur les e-mails de votre topic SNS avec un [monit {{< partial name="whats-next/whats-next.html" >}} -[1]: /fr/service_management/events/guides/email/ +[1]: /fr/events/guides/email/ [2]: https://app.datadoghq.com/event/explorer [3]: /fr/monitors/types/event/ [4]: /fr/events/explorer/ diff --git a/content/fr/monitors/guide/integrate-monitors-with-statuspage.md b/content/fr/monitors/guide/integrate-monitors-with-statuspage.md index 139722d1186..0338edefbd1 100644 --- a/content/fr/monitors/guide/integrate-monitors-with-statuspage.md +++ b/content/fr/monitors/guide/integrate-monitors-with-statuspage.md @@ -60,7 +60,7 @@ Pour créer un [monitor de métrique][8] qui se déclenche sur les alertes de St [1]: https://www.atlassian.com/software/statuspage [2]: /fr/integrations/statuspage -[3]: /fr/service_management/events/explorer/ +[3]: /fr/events/explorer/ [4]: https://app.datadoghq.com/integrations [5]: https://app.datadoghq.com/event/explorer [6]: /fr/dashboards/guide/custom_time_frames/ diff --git a/content/fr/service_management/events/correlation/analytics.md b/content/fr/service_management/events/correlation/analytics.md index af147ca9b8e..0e75f973039 100644 --- a/content/fr/service_management/events/correlation/analytics.md +++ b/content/fr/service_management/events/correlation/analytics.md @@ -1,6 +1,6 @@ --- further_reading: -- link: service_management/events/correlation/ +- link: events/correlation/ tag: Documentation text: En savoir plus sur la corrélation d'événements title: Analyses à partir de cas et d'événements @@ -13,7 +13,7 @@ Suivez la charge de travail de vos équipes en établissant des graphiques et en ## Métriques de scénarios -{{< img src="service_management/events/correlation/case_analytics.png" alt="Configurer des analyses de scénarios" style="width:100%;" >}} +{{< img src="events/correlation/case_analytics.png" alt="Configurer des analyses de scénarios" style="width:100%;" >}} Vous pouvez interroger les analyses de scénarios dans une variété de widgets présentant des graphiques pour analyser la productivité de vos équipes et identifier des modèles de problèmes. Affichez des graphiques d'analyses dans des dashboards et des notebooks. Pour commencer, dans la configuration du widget, sélectionnez **Cases** dans le menu déroulant de la source de données sous la section *Graph your data*. @@ -34,7 +34,7 @@ Les widgets suivants prennent en charge les analyses de scénarios : Décomposez des métriques d'événements par source, host, service, et plus encore. Découvrez d'où proviennent vos alertes problématiques et apprenez si votre charge opérationnelle augmente ou diminue au fil du temps. -{{< img src="service_management/events/correlation/event_analytics.png" alt="Configurer l'analyse d'événements" style="width:100%;" >}} +{{< img src="events/correlation/event_analytics.png" alt="Configurer l'analyse d'événements" style="width:100%;" >}} Pour commencer, dans la configuration du widget, sélectionnez **Events** dans la liste déroulante de la source de données sous la section *Graph your data*. diff --git a/content/fr/service_management/events/explorer/analytics.md b/content/fr/service_management/events/explorer/analytics.md index b05c3a5a7e2..49c3f4cad37 100644 --- a/content/fr/service_management/events/explorer/analytics.md +++ b/content/fr/service_management/events/explorer/analytics.md @@ -17,10 +17,10 @@ Vous pouvez exporter des visualisations d'analyse pour créer des widgets dans u Créez une requête pour contrôler les données affichées dans votre analyse d'événements : 1. Choisissez l'attribut ou le tag que vous souhaitez représenter, puis ajoutez-le en tant que facette. La facette affiche le total de valeurs uniques de la variable. - {{< img src="service_management/events/explorer/facet-to-graph.png" alt="Liste des facettes pouvant être représentées" style="width:100%;" >}} + {{< img src="events/explorer/facet-to-graph.png" alt="Liste des facettes pouvant être représentées" style="width:100%;" >}} 2. Regroupez les données de votre graphique en fonction d'une facette. Vous devez ajouter un attribut en tant que facette pour pouvoir l'utiliser. - {{< img src="service_management/events/explorer/split-graph.png" alt="Liste des facettes à partir desquelles les données peuvent être regroupées" style="width:100%;" >}} + {{< img src="events/explorer/split-graph.png" alt="Liste des facettes à partir desquelles les données peuvent être regroupées" style="width:100%;" >}} 3. Choisissez l'intervalle de votre graphique. Si vous changez l'intervalle global, cela modifie la liste des laps de temps disponibles. Vous pouvez afficher les résultats sous la forme d'une série temporelle, d'un tableau ou d'une top list. - {{< img src="service_management/events/explorer/time-interval.png" alt="Liste des intervalles disponibles, avec la valeur par défaut de 5 secondes" style="width:100%;" >}} + {{< img src="events/explorer/time-interval.png" alt="Liste des intervalles disponibles, avec la valeur par défaut de 5 secondes" style="width:100%;" >}} 4. Choisissez d'afficher les valeurs les plus élevées ou les plus faibles en fonction de la mesure sélectionnée. - {{< img src="service_management/events/explorer/display-values.png" alt="Choisir d'afficher les valeurs les plus faibles ou les plus élevées" style="width:100%;" >}} \ No newline at end of file + {{< img src="events/explorer/display-values.png" alt="Choisir d'afficher les valeurs les plus faibles ou les plus élevées" style="width:100%;" >}} \ No newline at end of file diff --git a/content/fr/service_management/events/explorer/attributes.md b/content/fr/service_management/events/explorer/attributes.md index 71d64e96783..5495b9c4531 100644 --- a/content/fr/service_management/events/explorer/attributes.md +++ b/content/fr/service_management/events/explorer/attributes.md @@ -1,7 +1,7 @@ --- disable_toc: false further_reading: -- link: /service_management/events/explorer/facets +- link: /events/explorer/facets tag: Documentation text: En savoir plus sur les facettes d'événement - link: logs/processing/pipelines @@ -37,4 +37,4 @@ Pour créer une facette sur un tag qui possède la même clé qu'un attribut ré {{< partial name="whats-next/whats-next.html" >}} [1]: /fr/logs/log_configuration/processors/?tab=ui#remapper -[2]: /fr/service_management/events/explorer/facets \ No newline at end of file +[2]: /fr/events/explorer/facets \ No newline at end of file diff --git a/content/fr/service_management/events/explorer/facets.md b/content/fr/service_management/events/explorer/facets.md index d9408840c37..6ce88bf157c 100644 --- a/content/fr/service_management/events/explorer/facets.md +++ b/content/fr/service_management/events/explorer/facets.md @@ -1,6 +1,6 @@ --- further_reading: -- link: service_management/events/explorer/attributes +- link: events/explorer/attributes tag: Documentation text: En savoir plus sur les attributs réservés title: Facettes @@ -12,7 +12,7 @@ Par défaut, Datadog indexe les attributs d'événement sous la forme de facette Une facette présente les membres distincts d'un attribut ou d'un tag, en plus de proposer des analyses de base, comme le nombre d'événements représentés. Les facettes vous permettent d'effectuer des pivotements ou de filtrer vos ensembles de données en fonction d'un attribut donné. Pour filtrer vos données, sélectionnez les valeurs que vous souhaitez afficher. -{{< img src="service_management/events/explorer/facets-location.png" alt="Volet latéral des facettes" style="width:100%;" >}} +{{< img src="events/explorer/facets-location.png" alt="Volet latéral des facettes" style="width:100%;" >}} ### Créer une facette diff --git a/content/fr/service_management/events/explorer/navigate.md b/content/fr/service_management/events/explorer/navigate.md index 9ec85e9b495..5f2f98300db 100644 --- a/content/fr/service_management/events/explorer/navigate.md +++ b/content/fr/service_management/events/explorer/navigate.md @@ -2,7 +2,7 @@ title: Parcourir l'Events Explorer --- -{{< img src="service_management/events/explorer/navigate.png" alt="Comment parcourir l'Events Explorer" style="width:100%;" >}} +{{< img src="events/explorer/navigate.png" alt="Comment parcourir l'Events Explorer" style="width:100%;" >}} ## Présentation @@ -14,7 +14,7 @@ Cliquez sur un événement de l'Events Explorer pour ouvrir le volet latéral d ### Onglet Event Attributes -{{< img src="service_management/events/explorer/event-attribute.png" alt="Un exemple d'onglet Event Attributes" style="width:100%;" >}} +{{< img src="events/explorer/event-attribute.png" alt="Un exemple d'onglet Event Attributes" style="width:100%;" >}} L'onglet Event Attributes du volet latéral répertorie les attributs de l'événement au format JSON. Cliquez sur un attribut pour l'ajouter à la requête existante, l'exclure ou ajouter une colonne pour cet attribut. diff --git a/content/fr/service_management/events/guides/_index.md b/content/fr/service_management/events/guides/_index.md index a62953f18ef..282fd421485 100644 --- a/content/fr/service_management/events/guides/_index.md +++ b/content/fr/service_management/events/guides/_index.md @@ -10,7 +10,7 @@ cascade: subcategory: Guides sur les événements disable_toc: true further_reading: -- link: /service_management/events/explorer/ +- link: /events/explorer/ tag: Documentation text: Events Explorer Datadog - link: /monitors/types/event/ @@ -23,22 +23,22 @@ title: Guides sur les événements Un événement représente n'importe quelle activité pouvant s'avérer pertinente pour les équipes d'ingénierie (dev, ops et sécurité). {{< whatsnext desc="Il existe plusieurs façons d'envoyer des événements à Datadog :">}} - {{< nextlink href="/service_management/events/guides/agent/" >}}Check d'Agent personnalisé{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/dogstatsd/" >}}DogStatsD{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/email/" >}}E-mail{{< /nextlink >}} + {{< nextlink href="/events/guides/agent/" >}}Check d'Agent personnalisé{{< /nextlink >}} + {{< nextlink href="/events/guides/dogstatsd/" >}}DogStatsD{{< /nextlink >}} + {{< nextlink href="/events/guides/email/" >}}E-mail{{< /nextlink >}} {{< nextlink href="/api/v1/events/#post-an-event" >}}API Datadog{{< /nextlink >}} {{< /whatsnext >}} {{< whatsnext desc="Assurez-vous que vos événements portent un tag :">}} - {{< nextlink href="/service_management/events/guides/recommended_event_tags/" >}}Recommandations pour l'ajout de tags à des événements{{< /nextlink >}} + {{< nextlink href="/events/guides/recommended_event_tags/" >}}Recommandations pour l'ajout de tags à des événements{{< /nextlink >}} {{< /whatsnext >}} {{< whatsnext desc="En savoir plus sur les scénarios d'utilisation d'Event Management :">}} - {{< nextlink href="/service_management/events/guides/usage" >}}Scénarios d'utilisation pour les événements{{< /nextlink >}} + {{< nextlink href="/events/guides/usage" >}}Scénarios d'utilisation pour les événements{{< /nextlink >}} {{< /whatsnext >}} {{< whatsnext desc="Autres guides :">}} - {{< nextlink href="/service_management/events/guides/migrating_to_new_events_features/" >}}Profiter des nouveaux événements{{< /nextlink >}} + {{< nextlink href="/events/guides/migrating_to_new_events_features/" >}}Profiter des nouveaux événements{{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/fr/service_management/events/guides/migrating_to_new_events_features.md b/content/fr/service_management/events/guides/migrating_to_new_events_features.md index d8a8cf37e46..3aed5192353 100644 --- a/content/fr/service_management/events/guides/migrating_to_new_events_features.md +++ b/content/fr/service_management/events/guides/migrating_to_new_events_features.md @@ -46,18 +46,18 @@ L'Events Explorer affiche les événements les plus récents générés par vot ### Analyse d'événements -{{< img src="service_management/events/events-analytics.png" alt="Écran d'analyse d'événements avec le filtre « source:cloudtrail »" >}} +{{< img src="events/events-analytics.png" alt="Écran d'analyse d'événements avec le filtre « source:cloudtrail »" >}} En plus de visualiser et rechercher des événements dans l'Events Explorer, vous pouvez désormais créer des graphiques sous forme de séries temporelles, de top list ou de tableau et regrouper les événements associés à une requête donnée. Consultez la section sur l'[analyse d'événements][2] pour en savoir plus. Vous pouvez également [générer des métriques][3] avec une période de rétention de 15 mois à partir de n'importe quelle requête de recherche d'événements pour créer des monitors et des alertes en fonction des événements historiques. -{{< img src="service_management/events/generate-metrics.png" alt="Image de métriques avec la requête de recherche d'événements." >}} +{{< img src="events/generate-metrics.png" alt="Image de métriques avec la requête de recherche d'événements." >}} ### Créer des graphiques d'événements dans les dashboards -{{< img src="service_management/events/graph-events.png" alt="Analyse d'événements">}} +{{< img src="events/graph-events.png" alt="Analyse d'événements">}} Vous pouvez désormais créer des graphiques d'événements pour une requête donnée au sein de vos dashboards sous forme de série temporelle, de valeur de requête, de top list, de tableau, et plus encore. @@ -69,7 +69,7 @@ Les nouveaux monitors d'événement ont été conçus pour offrir les mêmes fon Lorsque vous créez des monitors d'événement, le nouveau champ de requête de recherche prend désormais en charge l'autocomplétion : vous n'avez plus besoin de tout saisir manuellement. -{{< img src="service_management/events/guides/events-migration-monitor-new.png" alt="Nouvelle interface pour la syntaxe de requête de monitor" style="width:100%;" >}} +{{< img src="events/guides/events-migration-monitor-new.png" alt="Nouvelle interface pour la syntaxe de requête de monitor" style="width:100%;" >}} La nouvelle syntaxe de recherche vous permet d'utiliser des requêtes complexes dans des monitors d'événement, notamment grâce à la prise en charge des opérateurs booléens ou des wildcards. @@ -195,10 +195,10 @@ Les anciens monitors d'événement ne prennent pas en charge la méthode de roll {{< partial name="whats-next/whats-next.html" >}} -[1]: /fr/service_management/events/explorer -[2]: /fr/service_management/events/explorer/analytics -[3]: /fr/service_management/events/#generate-custom-metrics-from-events +[1]: /fr/events/explorer +[2]: /fr/events/explorer/analytics +[3]: /fr/events/#generate-custom-metrics-from-events [4]: https://app.datadoghq.com/dash/integration/30532/monitor-notifications-overview -[5]: /fr/service_management/events/guides/new_events_sources/ +[5]: /fr/events/guides/new_events_sources/ [6]: /fr/help/ [7]: /fr/api/latest/monitors/#create-a-monitor \ No newline at end of file diff --git a/content/fr/service_management/events/guides/recommended_event_tags.md b/content/fr/service_management/events/guides/recommended_event_tags.md index ae8c5bc6804..6345dcc5bc7 100644 --- a/content/fr/service_management/events/guides/recommended_event_tags.md +++ b/content/fr/service_management/events/guides/recommended_event_tags.md @@ -43,7 +43,7 @@ Vous pouvez ajouter les attributs de base suivants à vos événements : {{< partial name="whats-next/whats-next.html" >}} [1]: /fr/getting_started/tagging/unified_service_tagging -[2]: /fr/service_management/events/explorer +[2]: /fr/events/explorer [3]: /fr/api/latest/events/#post-an-event [4]: /fr/getting_started/monitors/#notify-your-team [5]: /fr/getting_started/tagging/assigning_tags diff --git a/content/fr/service_management/events/pipelines_and_processors/_index.md b/content/fr/service_management/events/pipelines_and_processors/_index.md index d7d8080ed7a..d37ab876300 100644 --- a/content/fr/service_management/events/pipelines_and_processors/_index.md +++ b/content/fr/service_management/events/pipelines_and_processors/_index.md @@ -30,12 +30,12 @@ Pour commencer, vous devez d'abord créer un pipeline, qui vous permet de filtre -[1]: /fr/service_management/events/pipelines_and_processors/arithmetic_processor -[2]: /fr/service_management/events/pipelines_and_processors/date_remapper -[3]: /fr/service_management/events/pipelines_and_processors/category_processor -[4]: /fr/service_management/events/pipelines_and_processors/grok_parser -[5]: /fr/service_management/events/pipelines_and_processors/lookup_processor -[6]: /fr/service_management/events/pipelines_and_processors/remapper -[7]: /fr/service_management/events/pipelines_and_processors/service_remapper -[8]: /fr/service_management/events/pipelines_and_processors/status_remapper -[9]: /fr/service_management/events/pipelines_and_processors/string_builder_processor \ No newline at end of file +[1]: /fr/events/pipelines_and_processors/arithmetic_processor +[2]: /fr/events/pipelines_and_processors/date_remapper +[3]: /fr/events/pipelines_and_processors/category_processor +[4]: /fr/events/pipelines_and_processors/grok_parser +[5]: /fr/events/pipelines_and_processors/lookup_processor +[6]: /fr/events/pipelines_and_processors/remapper +[7]: /fr/events/pipelines_and_processors/service_remapper +[8]: /fr/events/pipelines_and_processors/status_remapper +[9]: /fr/events/pipelines_and_processors/string_builder_processor \ No newline at end of file diff --git a/content/ja/account_management/org_settings.md b/content/ja/account_management/org_settings.md index db285992fdd..0b1981dad91 100644 --- a/content/ja/account_management/org_settings.md +++ b/content/ja/account_management/org_settings.md @@ -151,7 +151,7 @@ Datadog のデフォルトおよびカスタムロールについては、[ロ [9]: /ja/account_management/rbac/ [10]: /ja/agent/remote_config/?tab=configurationyamlfile#how-it-works [11]: /ja/account_management/api-app-keys/#client-tokens -[12]: /ja/service_management/events/guides/email/ +[12]: /ja/events/guides/email/ [13]: /ja/synthetics/settings/?tab=specifyvalue#overview [14]: /ja/account_management/safety_center [15]: /ja/account_management/org_settings/oauth_apps \ No newline at end of file diff --git a/content/ja/coterm/usage.md b/content/ja/coterm/usage.md index 140087c34bd..f0dfb82c978 100644 --- a/content/ja/coterm/usage.md +++ b/content/ja/coterm/usage.md @@ -129,7 +129,7 @@ COTERM_BREAK_GLASS=true kubectl delete foo {{< partial name="whats-next/whats-next.html" >}} [1]: /ja/sensitive_data_scanner/ -[2]: /ja/service_management/events/ +[2]: /ja/events/ [3]: /ja/service_management/case_management/ [4]: /ja/coterm/rules [5]: /ja/service_management/incident_management/ diff --git a/content/ja/developers/_index.md b/content/ja/developers/_index.md index cc6930e0094..088b7e9a9fd 100644 --- a/content/ja/developers/_index.md +++ b/content/ja/developers/_index.md @@ -105,7 +105,7 @@ Datadog パートナーになるための詳細は、[Datadog パートナーネ {{< whatsnext desc="Datadog に送信できるデータのタイプとその送信方法について説明します。" >}} {{< nextlink href="/metrics" >}}カスタムメトリクス: Datadog のカスタムメトリクスについて掘り下げて説明します。メトリクスのタイプや、それぞれのタイプが表すもの、送信方法、および Datadog 全体でどのように使用されるかを、このセクションで説明します。{{< /nextlink >}} - {{< nextlink href="service_management/events/guides/" >}}イベント: カスタム Agent チェック、DogStatsD、または Datadog API を使用して、Datadog にイベントを送信する方法について説明します。{{< /nextlink >}} + {{< nextlink href="events/guides/" >}}イベント: カスタム Agent チェック、DogStatsD、または Datadog API を使用して、Datadog にイベントを送信する方法について説明します。{{< /nextlink >}} {{< nextlink href="/developers/service_checks" >}}サービスチェック: 特定のサービスのアップまたはダウンステータスを Datadog に送信する方法について説明します。{{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/ja/developers/dogstatsd/_index.md b/content/ja/developers/dogstatsd/_index.md index 6d534efdae5..51f51abab4f 100644 --- a/content/ja/developers/dogstatsd/_index.md +++ b/content/ja/developers/dogstatsd/_index.md @@ -582,7 +582,7 @@ DogStatsD と StatsD はほぼ同じですが、DogStatsD には、使用可能 {{< whatsnext desc="">}} {{< nextlink href="/metrics/custom_metrics/dogstatsd_metrics_submission/" >}}DogStatsD でメトリクスを Datadog に送信します。{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/dogstatsd/" >}}DogStatsD でイベントを Datadog に送信します。{{< /nextlink >}} + {{< nextlink href="/events/guides/dogstatsd/" >}}DogStatsD でイベントを Datadog に送信します。{{< /nextlink >}} {{< nextlink href="/developers/service_checks/dogstatsd_service_checks_submission/" >}}DogStatsD でサービスチェックを Datadog に送信します。{{< /nextlink >}} {{< /whatsnext >}} @@ -597,7 +597,7 @@ DogStatsD が使用するデータグラム形式についてさらに理解を [3]: https://hub.docker.com/r/datadog/dogstatsd [4]: https://gcr.io/datadoghq/dogstatsd [5]: /ja/metrics/custom_metrics/ -[6]: /ja/service_management/events/guides/dogstatsd/ +[6]: /ja/events/guides/dogstatsd/ [7]: /ja/developers/service_checks/dogstatsd_service_checks_submission/ [8]: /ja/getting_started/tagging/unified_service_tagging [9]: /ja/developers/dogstatsd/datagram_shell/ \ No newline at end of file diff --git a/content/ja/developers/integrations/agent_integration.md b/content/ja/developers/integrations/agent_integration.md index dced09a04bd..01de602c150 100644 --- a/content/ja/developers/integrations/agent_integration.md +++ b/content/ja/developers/integrations/agent_integration.md @@ -486,7 +486,7 @@ Developer Platform に記載された手順に従って、Agent チェックの [15]: /ja/developers/integrations/check_references/#service-check-file [16]: https://packaging.python.org/en/latest/tutorials/packaging-projects/ [17]: https://docs.datadoghq.com/ja/agent/ -[18]: https://docs.datadoghq.com/ja/service_management/events/ +[18]: https://docs.datadoghq.com/ja/events/ [19]: https://desktop.github.com/ [20]: https://docs.datadoghq.com/ja/developers/integrations/ [21]: https://github.com/Datadog/integrations-extras diff --git a/content/ja/dora_metrics/setup/_index.md b/content/ja/dora_metrics/setup/_index.md index 0f1e9125c04..87f517602ee 100644 --- a/content/ja/dora_metrics/setup/_index.md +++ b/content/ja/dora_metrics/setup/_index.md @@ -43,7 +43,7 @@ DORA Metrics は、選択されたサイト ({{< region-param key="dd_site_name" {{< partial name="whats-next/whats-next.html" >}} [3]: /ja/dora_metrics/ -[4]: /ja/service_management/events/explorer/ +[4]: /ja/events/explorer/ [5]: /ja/api/latest/metrics/#query-timeseries-points [6]: /ja/api/latest/metrics/#query-timeseries-data-across-multiple-products [7]: /ja/dora_metrics/data_collected/ diff --git a/content/ja/error_tracking/dynamic_sampling.md b/content/ja/error_tracking/dynamic_sampling.md index f6beccc192b..d7fde0bddc6 100644 --- a/content/ja/error_tracking/dynamic_sampling.md +++ b/content/ja/error_tracking/dynamic_sampling.md @@ -48,7 +48,7 @@ Dynamic Sampling が適用された場合、次の手順を推奨します: {{< partial name="whats-next/whats-next.html" >}} -[1]: /ja/service_management/events/ +[1]: /ja/events/ [2]: https://app.datadoghq.com/error-tracking/settings/rate-limits [3]: /ja/logs/error_tracking/manage_data_collection#add-a-rule [4]: https://app.datadoghq.com/error-tracking/settings \ No newline at end of file diff --git a/content/ja/events/guides/recommended_event_tags.md b/content/ja/events/guides/recommended_event_tags.md index 025fc9090e0..e1482339ba5 100644 --- a/content/ja/events/guides/recommended_event_tags.md +++ b/content/ja/events/guides/recommended_event_tags.md @@ -1,6 +1,6 @@ --- aliases: -- /ja/service_management/events/guides/recommended_event_tags/ +- /ja/events/guides/recommended_event_tags/ description: おすすめのイベントタグとその付け方についてご紹介します。 further_reading: - link: /getting_started/tagging/assigning_tags diff --git a/content/ja/getting_started/application/_index.md b/content/ja/getting_started/application/_index.md index b22ff5c70aa..14e6b5d108b 100644 --- a/content/ja/getting_started/application/_index.md +++ b/content/ja/getting_started/application/_index.md @@ -146,8 +146,8 @@ Datadog [Cloud SIEM][21] (Security Information and Event Management) は、ア [7]: /ja/infrastructure/ [8]: /ja/getting_started/tagging/ [9]: /ja/infrastructure/hostmap/ -[10]: /ja/service_management/events/ -[11]: /ja/service_management/events/explorer/analytics +[10]: /ja/events/ +[11]: /ja/events/explorer/analytics [12]: /ja/dashboards/ [13]: /ja/dashboards/#screenboards [14]: /ja/dashboards/functions/arithmetic/ diff --git a/content/ja/glossary/terms/processing_pipeline_(Events).md b/content/ja/glossary/terms/processing_pipeline_(Events).md index a69057ab0a9..894a97a45ad 100644 --- a/content/ja/glossary/terms/processing_pipeline_(Events).md +++ b/content/ja/glossary/terms/processing_pipeline_(Events).md @@ -5,4 +5,4 @@ related_terms: - pipeline title: 処理パイプライン --- -Datadog Events の場合、処理パイプラインは、取り込み時のイベント属性に対するデータ構造化アクションの一連の手順です。ユーザーは、処理パイプラインを構成して、イベントを正規化し、強化することができます。詳細は、ドキュメントを参照してください。 \ No newline at end of file +Datadog Events の場合、処理パイプラインは、取り込み時のイベント属性に対するデータ構造化アクションの一連の手順です。ユーザーは、処理パイプラインを構成して、イベントを正規化し、強化することができます。詳細は、ドキュメントを参照してください。 \ No newline at end of file diff --git a/content/ja/integrations/catchpoint.md b/content/ja/integrations/catchpoint.md index 20c5c0d29d6..4b2422e425e 100644 --- a/content/ja/integrations/catchpoint.md +++ b/content/ja/integrations/catchpoint.md @@ -843,7 +843,7 @@ Catchpoint インテグレーションには、サービスのチェック機能 ご不明な点は、[Datadog のサポートチーム][5]までお問い合わせください。 [1]: https://app.datadoghq.com/integrations/catchpoint -[2]: https://docs.datadoghq.com/ja/service_management/events/ +[2]: https://docs.datadoghq.com/ja/events/ [3]: https://github.com/DataDog/dogweb/blob/prod/integration/catchpoint/catchpoint_metadata.csv [4]: https://app.datadoghq.com/dash/integration/32054/catchpoint-dashboard [5]: https://docs.datadoghq.com/ja/help/ diff --git a/content/ja/integrations/crowdstrike.md b/content/ja/integrations/crowdstrike.md index 6a8e1cf33a0..791fdd3eefa 100644 --- a/content/ja/integrations/crowdstrike.md +++ b/content/ja/integrations/crowdstrike.md @@ -102,7 +102,7 @@ CrowdStrike インテグレーションには、サービスのチェック機 ご不明な点は、[Datadog のサポートチーム][8]までお問合せください。 [1]: https://www.crowdstrike.com/ -[2]: https://docs.datadoghq.com/ja/service_management/events/explorer/ +[2]: https://docs.datadoghq.com/ja/events/explorer/ [3]: https://supportportal.crowdstrike.com/ [4]: https://falcon.crowdstrike.com/support/api-clients-and-keys [5]: https://app.datadoghq.com/integrations/crowdstrike diff --git a/content/ja/integrations/guide/events-from-sns-emails.md b/content/ja/integrations/guide/events-from-sns-emails.md index 4c6c4c50618..25b2cb204e9 100644 --- a/content/ja/integrations/guide/events-from-sns-emails.md +++ b/content/ja/integrations/guide/events-from-sns-emails.md @@ -37,7 +37,7 @@ AWS コンソールで SNS トピックに戻り、サブスクリプション {{< partial name="whats-next/whats-next.html" >}} -[1]: /ja/service_management/events/guides/email/ +[1]: /ja/events/guides/email/ [2]: https://app.datadoghq.com/event/explorer [3]: /ja/monitors/types/event/ [4]: /ja/events/explorer/ diff --git a/content/ja/integrations/harness_harness_notifications.md b/content/ja/integrations/harness_harness_notifications.md index 709f510b784..35ea2697baa 100644 --- a/content/ja/integrations/harness_harness_notifications.md +++ b/content/ja/integrations/harness_harness_notifications.md @@ -107,7 +107,7 @@ Notifications ページから、通知チャネルを有効化・無効化した サポートが必要な場合は [Harness サポート][5]にお問い合わせください。 -[1]: https://docs.datadoghq.com/ja/service_management/events/explorer/ +[1]: https://docs.datadoghq.com/ja/events/explorer/ [2]: mailto:support@harness.io [3]: https://developer.harness.io/docs/continuous-delivery/x-platform-cd-features/cd-steps/notify-users-of-pipeline-events/#datadog-notifications [4]: https://docs.datadoghq.com/ja/account_management/api-app-keys/ diff --git a/content/ja/integrations/redmine.md b/content/ja/integrations/redmine.md index d42edfa7020..87a054f7c48 100644 --- a/content/ja/integrations/redmine.md +++ b/content/ja/integrations/redmine.md @@ -57,5 +57,5 @@ Redmine インテグレーションには、サービスのチェック機能は ご不明な点は、[Datadog のサポートチーム][3]までお問合せください。 [1]: https://app.datadoghq.com/integrations/redmine -[2]: https://docs.datadoghq.com/ja/service_management/events/explorer/ +[2]: https://docs.datadoghq.com/ja/events/explorer/ [3]: https://docs.datadoghq.com/ja/help/ \ No newline at end of file diff --git a/content/ja/integrations/slack.md b/content/ja/integrations/slack.md index 15ab9ce01f8..7f13bdc7a82 100644 --- a/content/ja/integrations/slack.md +++ b/content/ja/integrations/slack.md @@ -118,7 +118,7 @@ Datadog サイトの [Slack インテグレーションタイル][1]を使用し [1]: https://app.datadoghq.com/integrations/slack [2]: https://slack.com/apps/A0F7XDT7F-datadog-legacy [3]: https://docs.datadoghq.com/ja/monitors/notifications/ -[4]: https://docs.datadoghq.com/ja/service_management/events/explorer/notifications/ +[4]: https://docs.datadoghq.com/ja/events/explorer/notifications/ {{% /tab %}} {{< /tabs >}} diff --git a/content/ja/integrations/snowflake_web.md b/content/ja/integrations/snowflake_web.md index 1ec116de229..103aa93c028 100644 --- a/content/ja/integrations/snowflake_web.md +++ b/content/ja/integrations/snowflake_web.md @@ -702,7 +702,7 @@ _ステータス: ok, critical_ [10]: images/custom_query.png [11]: images/snowflake_metrics.png [12]: https://docs.datadoghq.com/ja/reference_tables/?tab=manualupload -[13]: https://docs.datadoghq.com/ja/service_management/events/explorer/ +[13]: https://docs.datadoghq.com/ja/events/explorer/ [14]: https://docs.snowflake.com/en/user-guide/views-introduction [15]: https://www.datadoghq.com/product/cloud-cost-management/ [16]: https://docs.snowflake.com/en/user-guide/views-materialized diff --git a/content/ja/integrations/win32_event_log.md b/content/ja/integrations/win32_event_log.md index 6fb5e756af8..4e3079e54a0 100644 --- a/content/ja/integrations/win32_event_log.md +++ b/content/ja/integrations/win32_event_log.md @@ -632,7 +632,7 @@ Windows Event Log チェックには、サービスのチェック機能は含 [1]: https://docs.microsoft.com/en-us/windows/win32/eventlog/event-logging [2]: https://app.datadoghq.com/account/settings/agent/latest?platform=windows -[3]: https://docs.datadoghq.com/ja/service_management/events/ +[3]: https://docs.datadoghq.com/ja/events/ [4]: https://docs.datadoghq.com/ja/logs/ [5]: https://docs.datadoghq.com/ja/agent/guide/agent-configuration-files/#agent-configuration-directory [6]: https://github.com/DataDog/integrations-core/blob/master/win32_event_log/datadog_checks/win32_event_log/data/conf.yaml.example diff --git a/content/ja/logs/guide/best-practices-for-log-management.md b/content/ja/logs/guide/best-practices-for-log-management.md index 7abbf7f7792..70b9875a118 100644 --- a/content/ja/logs/guide/best-practices-for-log-management.md +++ b/content/ja/logs/guide/best-practices-for-log-management.md @@ -217,7 +217,7 @@ If you want to prevent data leaks and limit non-compliance risks, use Sensitive [14]: https://app.datadoghq.com/logs [15]: /ja/logs/explorer/search/ [16]: /ja/logs/indexes/#set-daily-quota -[17]: /ja/service_management/events/explorer/facets +[17]: /ja/events/explorer/facets [18]: https://app.datadoghq.com/dash/integration/logs_estimated_usage [19]: https://app.datadoghq.com/dashboard/lists?q=Log+Management+-+Estimated+Usage [20]: /ja/logs/log_configuration/indexes/#exclusion-filters diff --git a/content/ja/logs/log_configuration/archives.md b/content/ja/logs/log_configuration/archives.md index 30e1f2ab223..a3df3178576 100644 --- a/content/ja/logs/log_configuration/archives.md +++ b/content/ja/logs/log_configuration/archives.md @@ -424,4 +424,4 @@ Datadog がストレージバケットに転送するログアーカイブは、 [12]: /ja/account_management/rbac/permissions#logs_read_index_data [13]: /ja/account_management/rbac/permissions#logs_read_data [14]: /ja/logs/explorer/live_tail/ -[15]: /ja/service_management/events/explorer/ +[15]: /ja/events/explorer/ diff --git a/content/ja/metrics/overview.md b/content/ja/metrics/overview.md index 36aa39a99ed..a2079045d86 100644 --- a/content/ja/metrics/overview.md +++ b/content/ja/metrics/overview.md @@ -139,7 +139,7 @@ Datadog には全部で {{< translate key="integration_count" >}} を超える [15]: /ja/tracing/trace_pipeline/generate_metrics/ [16]: /ja/real_user_monitoring/platform/generate_metrics/ [17]: /ja/infrastructure/process/increase_process_retention/#generate-a-process-based-metric -[18]: /ja/service_management/events/guides/usage/#custom-metrics +[18]: /ja/events/guides/usage/#custom-metrics [19]: /ja/metrics/metrics-without-limits/ [20]: /ja/metrics/distributions/ [21]: /ja/metrics/custom_metrics/historical_metrics/ diff --git a/content/ja/monitors/downtimes/_index.md b/content/ja/monitors/downtimes/_index.md index 4735180bda0..77c8aefcb4e 100644 --- a/content/ja/monitors/downtimes/_index.md +++ b/content/ja/monitors/downtimes/_index.md @@ -195,7 +195,7 @@ Datadog は、特定のクラウドワークロードの手動シャットダウ [7]: /ja/monitors/notify/#overview [8]: /ja/integrations/#cat-notification [9]: /ja/monitors/status/ -[10]: /ja/service_management/events/explorer +[10]: /ja/events/explorer [11]: /ja/api/latest/downtimes/#cancel-a-downtime [12]: /ja/account_management/#preferences [13]: /ja/integrations/amazon_ec2/#ec2-automuting diff --git a/content/ja/monitors/guide/integrate-monitors-with-statuspage.md b/content/ja/monitors/guide/integrate-monitors-with-statuspage.md index 2d3941ff389..0f34b3d21d8 100644 --- a/content/ja/monitors/guide/integrate-monitors-with-statuspage.md +++ b/content/ja/monitors/guide/integrate-monitors-with-statuspage.md @@ -59,7 +59,7 @@ Statuspage アラートでトリガーする[メトリクスモニター][8]を [1]: https://www.atlassian.com/software/statuspage [2]: /ja/integrations/statuspage -[3]: /ja/service_management/events/explorer/ +[3]: /ja/events/explorer/ [4]: https://app.datadoghq.com/integrations [5]: https://app.datadoghq.com/event/explorer [6]: /ja/dashboards/guide/custom_time_frames/ diff --git a/content/ja/monitors/status/events.md b/content/ja/monitors/status/events.md index 5c29c29d8f0..6047fc63301 100644 --- a/content/ja/monitors/status/events.md +++ b/content/ja/monitors/status/events.md @@ -1,6 +1,6 @@ --- further_reading: -- link: service_management/events/ +- link: events/ tag: ドキュメント text: イベント管理 title: Status Events diff --git a/content/ja/monitors/types/event.md b/content/ja/monitors/types/event.md index f56e0c8a601..2b922b1b907 100644 --- a/content/ja/monitors/types/event.md +++ b/content/ja/monitors/types/event.md @@ -4,7 +4,7 @@ aliases: - /ja/monitors/create/types/event/ description: Datadog によって収集されたイベントを監視する further_reading: -- link: /service_management/events/ +- link: /events/ tag: ドキュメント text: Event Management Overview - link: /monitors/notify/ @@ -94,7 +94,7 @@ For detailed instructions on the **Configure notifications and automations** sec {{< partial name="whats-next/whats-next.html" >}} [1]: https://app.datadoghq.com/monitors#create/event -[2]: /ja/service_management/events/explorer/searching +[2]: /ja/events/explorer/searching [3]: /ja/help/ [4]: /ja/monitors/configuration/#advanced-alert-conditions [5]: /ja/monitors/notify/ \ No newline at end of file diff --git a/content/ja/partners/getting_started/data-intake.md b/content/ja/partners/getting_started/data-intake.md index d0de52ac31b..47c092ba1bb 100644 --- a/content/ja/partners/getting_started/data-intake.md +++ b/content/ja/partners/getting_started/data-intake.md @@ -180,7 +180,7 @@ Datadog にデータが流れ込んだら、次はクライアントに[価値 [11]: /ja/api/latest/events [12]: /ja/api/latest/tracing/ [13]: /ja/developers/custom_checks/ -[14]: /ja/service_management/events/guides/dogstatsd/ +[14]: /ja/events/guides/dogstatsd/ [15]: /ja/metrics/custom_metrics/ [16]: /ja/developers/community/libraries/#api-and-dogstatsd-client-libraries [17]: /ja/api/latest/ diff --git a/content/ja/service_management/events/_index.md b/content/ja/service_management/events/_index.md index a890c86e32a..f59459bbd70 100644 --- a/content/ja/service_management/events/_index.md +++ b/content/ja/service_management/events/_index.md @@ -7,7 +7,7 @@ further_reading: - link: '#post-an-event' tag: Documentation text: Datadog イベント API -- link: /service_management/events/guides/recommended_event_tags/ +- link: /events/guides/recommended_event_tags/ tag: Documentation text: イベントへのタグ付けのベストプラクティス - link: https://www.datadoghq.com/blog/identify-sensitive-data-leakage-in-apm-rum-with-sensitive-data-scanner/ @@ -23,7 +23,7 @@ is_beta: true title: イベント管理 --- -{{< img src="service_management/events/correlation/event_management.png" alt="what is event management" style="width:100%;" >}} +{{< img src="events/correlation/event_management.png" alt="what is event management" style="width:100%;" >}} ## 概要 @@ -34,11 +34,11 @@ title: イベント管理 ## コンポーネント {{< whatsnext desc="Event Management features:">}} - {{< nextlink href="/service_management/events/ingest/" >}}Ingest events - Learn how to send events to Datadog{{< /nextlink >}} - {{< nextlink href="/service_management/events/pipelines_and_processors/">}}Pipelines and Processors - Enrich and Normalize your events{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/" >}}Events Explorer - View, search and send notifications from events coming into Datadog{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/usage/" >}}Using events - Analyze, investigate, and monitor events {{< /nextlink >}} - {{< nextlink href="/service_management/events/correlation/" >}}Correlation - reduce alert fatigure and the number of tickets/notifictions you recieve {{< /nextlink >}} + {{< nextlink href="/events/ingest/" >}}Ingest events - Learn how to send events to Datadog{{< /nextlink >}} + {{< nextlink href="/events/pipelines_and_processors/">}}Pipelines and Processors - Enrich and Normalize your events{{< /nextlink >}} + {{< nextlink href="/events/explorer/" >}}Events Explorer - View, search and send notifications from events coming into Datadog{{< /nextlink >}} + {{< nextlink href="/events/guides/usage/" >}}Using events - Analyze, investigate, and monitor events {{< /nextlink >}} + {{< nextlink href="/events/correlation/" >}}Correlation - reduce alert fatigure and the number of tickets/notifictions you recieve {{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/ja/service_management/events/correlation/_index.md b/content/ja/service_management/events/correlation/_index.md index f1b217bec73..5795496144a 100644 --- a/content/ja/service_management/events/correlation/_index.md +++ b/content/ja/service_management/events/correlation/_index.md @@ -6,7 +6,7 @@ algolia: - 相関パターン disable_toc: false further_reading: -- link: service_management/events/ +- link: events/ tag: ドキュメント text: Event Management - link: service_management/case_management/ @@ -27,9 +27,9 @@ Event Correlation では、イベント間の関連性やユーザーが定義 * すべての該当チームがサイロ化せず、一つの問題を把握できるようにする {{< whatsnext desc="はじめに:" >}} -    {{< nextlink href="/service_management/events/correlation/configuration" >}}相関（Correlation） - 2 種類の相関機能の利用を開始する{{< /nextlink >}} -    {{< nextlink href="/service_management/events/correlation/triage_and_notify/" >}}トリアージと通知 - 作成された相関について、ビューの確認、トリアージ、通知、チケットの受信を行う{{< /nextlink >}} -    {{< nextlink href="/service_management/events/correlation/analytics/" >}}分析 - 割り当てられたケース数、サービスごとの件数など、相関で得られるメトリクスを分析・調査する{{< /nextlink >}} +    {{< nextlink href="/events/correlation/configuration" >}}相関（Correlation） - 2 種類の相関機能の利用を開始する{{< /nextlink >}} +    {{< nextlink href="/events/correlation/triage_and_notify/" >}}トリアージと通知 - 作成された相関について、ビューの確認、トリアージ、通知、チケットの受信を行う{{< /nextlink >}} +    {{< nextlink href="/events/correlation/analytics/" >}}分析 - 割り当てられたケース数、サービスごとの件数など、相関で得られるメトリクスを分析・調査する{{< /nextlink >}} {{< /whatsnext >}} ## その他の参考資料 diff --git a/content/ja/service_management/events/correlation/configuration.md b/content/ja/service_management/events/correlation/configuration.md index 7f02c55e125..bbda22672e7 100644 --- a/content/ja/service_management/events/correlation/configuration.md +++ b/content/ja/service_management/events/correlation/configuration.md @@ -1,9 +1,9 @@ --- further_reading: -- link: service_management/events/correlation/triage_and_notify +- link: events/correlation/triage_and_notify tag: ドキュメント text: ケースのトリアージと通知について -- link: service_management/events/correlation/analytics +- link: events/correlation/analytics tag: ドキュメント text: ケースの分析 title: 構成 @@ -20,8 +20,8 @@ title: 構成 ### 相関の構成 {{< whatsnext desc=" " >}} - {{< nextlink href="service_management/events/correlation/patterns" >}}パターンベース相関{{< /nextlink >}} - {{< nextlink href="service_management/events/correlation/intelligent" >}}インテリジェント相関{{< /nextlink >}} + {{< nextlink href="events/correlation/patterns" >}}パターンベース相関{{< /nextlink >}} + {{< nextlink href="events/correlation/intelligent" >}}インテリジェント相関{{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/ja/service_management/events/correlation/intelligent.md b/content/ja/service_management/events/correlation/intelligent.md index de2c44c4638..2810d084203 100644 --- a/content/ja/service_management/events/correlation/intelligent.md +++ b/content/ja/service_management/events/correlation/intelligent.md @@ -1,6 +1,6 @@ --- further_reading: -- link: service_management/events/correlation/triage_and_notify +- link: events/correlation/triage_and_notify tag: ドキュメント text: ケースのトリアージと通知について title: インテリジェントな相関付け @@ -16,17 +16,17 @@ title: インテリジェントな相関付け 1. そこから、自分の組織から作成されたインテリジェントな相関付けをプレビューすることができます。 -{{< img src="service_management/events/correlation/intelligent/intelligent_config_updated.png" alt="インテリジェントな相関付けの構成" style="width:100%;" >}} +{{< img src="events/correlation/intelligent/intelligent_config_updated.png" alt="インテリジェントな相関付けの構成" style="width:100%;" >}} ## 最初のケースの受信 -{{< img src="service_management/events/correlation/intelligent/intelligent_project.png" alt="Event Management - Intelligent Correlation" style="width:100%;" >}} +{{< img src="events/correlation/intelligent/intelligent_project.png" alt="Event Management - Intelligent Correlation" style="width:100%;" >}} [Event Correlations][3] に移動すると、**Intelligent Correlation** というプロジェクトが見つかります。このプロジェクトから、インテリジェントな相関付けにより作成されたケースを見ることができます。 インテリジェントな相関付けは、関連するアラートを見つけた後、自動的にケースを生成します。 -{{< img src="service_management/events/correlation/intelligent/intelligent_correlation.png" alt="インテリジェントな相関付けから作成されたケースのケース詳細ページの Investigation タブに表示された関連アラート" style="width:100%;" >}} +{{< img src="events/correlation/intelligent/intelligent_correlation.png" alt="インテリジェントな相関付けから作成されたケースのケース詳細ページの Investigation タブに表示された関連アラート" style="width:100%;" >}} diff --git a/content/ja/service_management/events/correlation/patterns.md b/content/ja/service_management/events/correlation/patterns.md index bb7b52973b6..e8385a42e6c 100644 --- a/content/ja/service_management/events/correlation/patterns.md +++ b/content/ja/service_management/events/correlation/patterns.md @@ -1,6 +1,6 @@ --- further_reading: -- link: service_management/events/correlation/triage_and_notify +- link: events/correlation/triage_and_notify tag: ドキュメント text: ケースのトリアージと通知について title: パターンに基づく相関 @@ -12,7 +12,7 @@ title: パターンに基づく相関 まずは、Datadog はお客様の環境に応じて[パターンに基づく相関][1]を自動的に提案します。推奨パターンの構成を開くには、推奨パターンのいずれかをクリックします。構成フィールドは事前に入力されています。 -{{< img src="service_management/events/correlation/pattern/recommended_patterns_preview.png" alt="相関の推奨パターンと、パターンが作成する可能性のあるケースを示すプレビューパネル" style="width:100%;" >}} +{{< img src="events/correlation/pattern/recommended_patterns_preview.png" alt="相関の推奨パターンと、パターンが作成する可能性のあるケースを示すプレビューパネル" style="width:100%;" >}} ## パターンの作成 @@ -23,7 +23,7 @@ title: パターンに基づく相関 1. 推奨パターンを調整するには、**+ Continue With Pattern** をクリックします。これにより、調整を追加するための事前に入力された構成ページに移動します。または、**+ Personalize From Scratch** をクリックして独自のパターンを作成することもできます。 まず、イベントはイベント集計キーに基づいて重複排除されてアラートにまとめられます。次に、アラートは構成に基づいてケースに相関付けられます。 -{{< img src="service_management/events/correlation/correlation_helper.mp4" alt="イベントが定義されたソース、フィルターに一致すると、重複排除されてアラートにまとめられます。アラートはグループ化属性に基づいて相関され、そのイベントは、新しいケースでプロセスが繰り返される前に、定義されたタイムウィンドウ内で重複排除されます。これらの構成は設定で変更できます" video=true >}} +{{< img src="events/correlation/correlation_helper.mp4" alt="イベントが定義されたソース、フィルターに一致すると、重複排除されてアラートにまとめられます。アラートはグループ化属性に基づいて相関され、そのイベントは、新しいケースでプロセスが繰り返される前に、定義されたタイムウィンドウ内で重複排除されます。これらの構成は設定で変更できます" video=true >}} 集計キーでイベントを送信する方法については、[Datadog にイベントを送信する][5]を参照してください。集計キーのないイベントは、重複排除されて時間枠内で 1 つのアラートにまとめられます。 ### 提案パターン @@ -67,7 +67,7 @@ title: パターンに基づく相関 このデータを使用して、相関の影響をプレビューし、パターンの期待される出力を理解します。 -{{< img src="service_management/events/correlation/pattern/preview_pattern_output.png" alt="プレビューパネルをハイライトするパターンに基づく相関の構成。パネルには、構成に一致する取り込みイベントの数、それらのイベントのうちどれだけのアラートが発生するか、どれだけの重複排除が発生するか、その結果発生するケースの数が表示されます。" style="width:100%;" >}} +{{< img src="events/correlation/pattern/preview_pattern_output.png" alt="プレビューパネルをハイライトするパターンに基づく相関の構成。パネルには、構成に一致する取り込みイベントの数、それらのイベントのうちどれだけのアラートが発生するか、どれだけの重複排除が発生するか、その結果発生するケースの数が表示されます。" style="width:100%;" >}} **注**: プレビューケースのデフォルトタイトルは、相関の最初のアラートです。パターンを保存すると、イベント管理ケースのタイトルがインテリジェントに生成されます。 @@ -86,6 +86,6 @@ title: パターンに基づく相関 [1]: https://app.datadoghq.com/event/correlation [2]: https://app.datadoghq.com/event/correlation/rule/new -[3]: /ja/service_management/events/explorer/facets/#create-a-facet -[4]: /ja/service_management/events/explorer/facets -[5]: /ja/service_management/events/ingest/ \ No newline at end of file +[3]: /ja/events/explorer/facets/#create-a-facet +[4]: /ja/events/explorer/facets +[5]: /ja/events/ingest/ \ No newline at end of file diff --git a/content/ja/service_management/events/explorer/_index.md b/content/ja/service_management/events/explorer/_index.md index 831b122f2e8..177eb6fdb41 100644 --- a/content/ja/service_management/events/explorer/_index.md +++ b/content/ja/service_management/events/explorer/_index.md @@ -12,19 +12,19 @@ further_reading: title: イベントエクスプローラー --- -{{< img src="service_management/events/events-explorer.mp4" alt="イベントを属性でソートし、分析結果を調べる" video=true >}} +{{< img src="events/events-explorer.mp4" alt="イベントを属性でソートし、分析結果を調べる" video=true >}} イベントエクスプローラーを使用して、Datadog に流入するイベントを集計・表示します。イベントを属性でグループ化またはフィルタリングし、イベント分析でグラフィカルに表現します。クエリ構文を使用して、ブール演算子やワイルドカード演算子を使用してイベントをフィルタリングします。 {{< whatsnext desc="Features of the Events Explorer:" >}} - {{< nextlink href="/service_management/events/explorer/searching" >}}検索{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/navigate" >}}エクスプローラーの操作{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/customization" >}}カスタマイズ{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/facets" >}}ファセット{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/attributes" >}}属性{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/notifications" >}}通知の送信{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/analytics" >}}分析{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/saved_views" >}}保存ビュー{{< /nextlink >}} + {{< nextlink href="/events/explorer/searching" >}}検索{{< /nextlink >}} + {{< nextlink href="/events/explorer/navigate" >}}エクスプローラーの操作{{< /nextlink >}} + {{< nextlink href="/events/explorer/customization" >}}カスタマイズ{{< /nextlink >}} + {{< nextlink href="/events/explorer/facets" >}}ファセット{{< /nextlink >}} + {{< nextlink href="/events/explorer/attributes" >}}属性{{< /nextlink >}} + {{< nextlink href="/events/explorer/notifications" >}}通知の送信{{< /nextlink >}} + {{< nextlink href="/events/explorer/analytics" >}}分析{{< /nextlink >}} + {{< nextlink href="/events/explorer/saved_views" >}}保存ビュー{{< /nextlink >}} {{< /whatsnext >}} ## その他の参考資料 diff --git a/content/ja/service_management/events/explorer/analytics.md b/content/ja/service_management/events/explorer/analytics.md index 8b87596adc8..27d9c274655 100644 --- a/content/ja/service_management/events/explorer/analytics.md +++ b/content/ja/service_management/events/explorer/analytics.md @@ -17,10 +17,10 @@ title: 分析 クエリを使用して、イベント分析に何を表示するかを制御できます。 1. グラフ化する属性またはタグを選択し、ファセットとして追加します。ファセットをグラフ化すると、変数の一意のカウントが表示されます。 - {{< img src="service_management/events/explorer/facet-to-graph.png" alt="グラフ化できるファセットのリストを表示します。" style="width:100%;" >}} + {{< img src="events/explorer/facet-to-graph.png" alt="グラフ化できるファセットのリストを表示します。" style="width:100%;" >}} 2. ファセットを使用してグラフをグループ化します。ここで使用できるようにするには、ファセットとして属性を追加する必要があります。 - {{< img src="service_management/events/explorer/split-graph.png" alt="データをグループ化できるファセットのリストを表示します。" style="width:100%;" >}} + {{< img src="events/explorer/split-graph.png" alt="データをグループ化できるファセットのリストを表示します。" style="width:100%;" >}} 3. グラフの時間間隔を選択します。グローバルタイムフレームを変更すると、使用可能なタイムステップ値のリストが変更されます。結果は、時系列、表、またはトップリストとして表示できます。 - {{< img src="service_management/events/explorer/time-interval.png" alt="デフォルトの 5 秒を含む、可能な時間間隔のリストを表示します。" style="width:100%;" >}} + {{< img src="events/explorer/time-interval.png" alt="デフォルトの 5 秒を含む、可能な時間間隔のリストを表示します。" style="width:100%;" >}} 4. 選択したメジャーに応じて、上位と下位のどちらの値を表示するかを選択します。 - {{< img src="service_management/events/explorer/display-values.png" alt="値を上から表示するか下から表示するかを選択します。" style="width:100%;" >}} + {{< img src="events/explorer/display-values.png" alt="値を上から表示するか下から表示するかを選択します。" style="width:100%;" >}} diff --git a/content/ja/service_management/events/guides/_index.md b/content/ja/service_management/events/guides/_index.md index b6804c7d6ba..de9a8a54947 100644 --- a/content/ja/service_management/events/guides/_index.md +++ b/content/ja/service_management/events/guides/_index.md @@ -10,7 +10,7 @@ cascade: subcategory: イベントガイド disable_toc: true further_reading: -- link: /service_management/events/explorer/ +- link: /events/explorer/ tag: Documentation text: Datadog イベントエクスプローラー - link: /monitors/types/event/ @@ -23,22 +23,22 @@ title: イベントガイド イベントは、エンジニア (開発、運用、セキュリティ) が注目すべきアクティビティの記録です。 {{< whatsnext desc="カスタムイベントを Datadog に送信します。">}} - {{< nextlink href="/service_management/events/guides/agent/" >}}カスタム Agent チェック{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/dogstatsd/" >}}DogStatsD{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/email/" >}}メール{{< /nextlink >}} + {{< nextlink href="/events/guides/agent/" >}}カスタム Agent チェック{{< /nextlink >}} + {{< nextlink href="/events/guides/dogstatsd/" >}}DogStatsD{{< /nextlink >}} + {{< nextlink href="/events/guides/email/" >}}メール{{< /nextlink >}} {{< nextlink href="/api/v1/events/#post-an-event" >}}Datadog API{{< /nextlink >}} {{< /whatsnext >}} {{< whatsnext desc="イベントには必ずタグを付けてください。">}} - {{< nextlink href="/service_management/events/guides/recommended_event_tags/" >}}イベントへのタグ付けのベストプラクティス{{< /nextlink >}} + {{< nextlink href="/events/guides/recommended_event_tags/" >}}イベントへのタグ付けのベストプラクティス{{< /nextlink >}} {{< /whatsnext >}} {{< whatsnext desc="Learn more about Event Management use cases:">}} - {{< nextlink href="/service_management/events/guides/usage" >}}イベントの使用例{{< /nextlink >}} + {{< nextlink href="/events/guides/usage" >}}イベントの使用例{{< /nextlink >}} {{< /whatsnext >}} {{< whatsnext desc="その他のガイド:">}} - {{< nextlink href="/service_management/events/guides/migrating_to_new_events_features/" >}}新しいイベント機能への移行{{< /nextlink >}} + {{< nextlink href="/events/guides/migrating_to_new_events_features/" >}}新しいイベント機能への移行{{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/ja/service_management/events/guides/dogstatsd.md b/content/ja/service_management/events/guides/dogstatsd.md index 09632edb3db..c1af0cbc061 100644 --- a/content/ja/service_management/events/guides/dogstatsd.md +++ b/content/ja/service_management/events/guides/dogstatsd.md @@ -209,4 +209,4 @@ $statsd->event('An error occurred.', [1]: /ja/developers/dogstatsd/ -[2]: /ja/service_management/events/ \ No newline at end of file +[2]: /ja/events/ \ No newline at end of file diff --git a/content/ja/service_management/events/guides/migrating_to_new_events_features.md b/content/ja/service_management/events/guides/migrating_to_new_events_features.md index e886632ec3a..7793b73f024 100644 --- a/content/ja/service_management/events/guides/migrating_to_new_events_features.md +++ b/content/ja/service_management/events/guides/migrating_to_new_events_features.md @@ -45,18 +45,18 @@ Datadog のレガシーイベントストリームとイベントモニターは ### イベント分析 -{{< img src="service_management/events/events-analytics.png" alt="'source:cloudtrail' でフィルタリングされたイベントアナリティクスの表示" >}} +{{< img src="events/events-analytics.png" alt="'source:cloudtrail' でフィルタリングされたイベントアナリティクスの表示" >}} エクスプローラーでのイベントの表示や検索に加え、時系列、トップリスト、テーブルとしてグラフ化し、指定したクエリのイベント数をグループ化することができるようになりました。詳しくは、[イベントアナリティクス][2]をご覧ください。 また、イベント検索クエリから 15 ヶ月間保持される[メトリクスを生成][3]し、過去のイベントに基づきモニターやアラートを作成できます。 -{{< img src="service_management/events/generate-metrics.png" alt="イベント検索クエリによるメトリクスのイメージ。" >}} +{{< img src="events/generate-metrics.png" alt="イベント検索クエリによるメトリクスのイメージ。" >}} ### ダッシュボードでイベントをグラフ化する -{{< img src="service_management/events/graph-events.png" alt="イベントアナリティクス" >}} +{{< img src="events/graph-events.png" alt="イベントアナリティクス" >}} ダッシュボード内で、指定したクエリのイベントを、時系列グラフ、クエリ値、トップリスト、テーブルなどでグラフ化できるようになりました。 @@ -68,7 +68,7 @@ Datadog のレガシーイベントストリームとイベントモニターは イベントモニターを作成する際、従来の空白で埋めるタイプのクエリから、新しいクエリ検索フィールドにオートコンプリートが追加されました。 -{{< img src="service_management/events/guides/events-migration-monitor-new.png" alt="モニタークエリ構文の新しい UI" style="width:100%;" >}} +{{< img src="events/guides/events-migration-monitor-new.png" alt="モニタークエリ構文の新しい UI" style="width:100%;" >}} 新しいクエリ検索では、ブール演算子やワイルドカードなどの新しい機能により、イベントモニターで複雑なクエリを使用することができます。 @@ -194,10 +194,10 @@ GitHub または Chef からのイベントを表示する {{< partial name="whats-next/whats-next.html" >}} -[1]: /ja/service_management/events/explorer -[2]: /ja/service_management/events/explorer/analytics -[3]: /ja/service_management/events/usage/#custom-metrics +[1]: /ja/events/explorer +[2]: /ja/events/explorer/analytics +[3]: /ja/events/usage/#custom-metrics [4]: https://app.datadoghq.com/dash/integration/30532/monitor-notifications-overview -[5]: /ja/service_management/events/guides/new_events_sources/ +[5]: /ja/events/guides/new_events_sources/ [6]: /ja/help/ [7]: /ja/api/latest/monitors/#create-a-monitor \ No newline at end of file diff --git a/content/ja/service_management/events/guides/recommended_event_tags.md b/content/ja/service_management/events/guides/recommended_event_tags.md index f4df0852f36..7626ecb1d56 100644 --- a/content/ja/service_management/events/guides/recommended_event_tags.md +++ b/content/ja/service_management/events/guides/recommended_event_tags.md @@ -42,7 +42,7 @@ Datadog では、以下のような利点から、すべてのイベントに[ {{< partial name="whats-next/whats-next.html" >}} [1]: /ja/getting_started/tagging/unified_service_tagging -[2]: /ja/service_management/events/explorer +[2]: /ja/events/explorer [3]: /ja/api/latest/events/#post-an-event [4]: /ja/getting_started/monitors/#notify-your-services-and-your-team-members [5]: /ja/getting_started/tagging/assigning_tags diff --git a/content/ja/service_management/events/guides/usage.md b/content/ja/service_management/events/guides/usage.md index 6418b46fe6c..ae3294a0752 100644 --- a/content/ja/service_management/events/guides/usage.md +++ b/content/ja/service_management/events/guides/usage.md @@ -1,11 +1,11 @@ --- aliases: -- /ja/service_management/events/usage +- /ja/events/usage further_reading: - link: /logs/log_configuration/processors/ tag: ドキュメント text: 処理パイプラインについて -- link: /service_management/events/explorer/ +- link: /events/explorer/ tag: ドキュメント text: イベントエクスプローラーでイベントをトリアージする title: イベントの利用 @@ -15,7 +15,7 @@ title: イベントの利用 [Generate metrics][5] を使うと、任意のイベント検索クエリから保持期間 15 か月のメトリクスを生成し、過去のイベントやアラートを作成して監視できます。過去 20 分以内のタイム スタンプで取り込まれたイベントが、集計の対象になります。詳しくは [Event Analytics][6] を参照してください。 -{{< img src="service_management/events/guides/usage/generate-metrics.png" alt="イベント検索クエリによるメトリクスのイメージ。" >}} +{{< img src="events/guides/usage/generate-metrics.png" alt="イベント検索クエリによるメトリクスのイメージ。" >}} ## イベントの活用例 @@ -25,13 +25,13 @@ title: イベントの利用 ### ダッシュボード -{{< img src="service_management/events/guides/usage/events-dashboard.mp4" alt="イベントをソースとするグラフウィジェット" video=true >}} +{{< img src="events/guides/usage/events-dashboard.mp4" alt="イベントをソースとするグラフウィジェット" video=true >}} イベントは [graph widgets][8] のデータ ソースとして利用でき、イベント検索クエリをもとに timeseries, table, top list ウィジェットを作成できます。たとえば、[Monitor Notifications Overview][9] ダッシュボードでは、モニター アラート イベントのトレンドを分析し、設定の見直しやアラート疲れの軽減に役立てられます。 #### オーバーレイ -{{< img src="service_management/events/guides/usage/event_overlays.png" alt="ダッシュボードの例でイベントオーバーレイを表示するオプション" style="width:100%;" >}} +{{< img src="events/guides/usage/event_overlays.png" alt="ダッシュボードの例でイベントオーバーレイを表示するオプション" style="width:100%;" >}} オーバーレイは、対応するイベントをグラフ上に重ねて表示します。Dashboard の [Event Overlays][10] 機能を使うと、最近の変更がアプリケーションやサービスでパフォーマンス問題を引き起こしているタイミングを特定し、原因を突き止められます。 @@ -49,8 +49,8 @@ title: イベントの利用 [3]: https://app.datadoghq.com/event/pipelines [4]: /ja/help/ [5]: https://app.datadoghq.com/event/configuration/generate-metrics -[6]: /ja/service_management/events/explorer/analytics -[7]: /ja/service_management/events/explorer/ +[6]: /ja/events/explorer/analytics +[7]: /ja/events/explorer/ [8]: /ja/dashboards/widgets/alert_graph/ [9]: https://app.datadoghq.com/dash/integration/30532/monitor-notifications-overview [10]: /ja/dashboards/change_overlays/ diff --git a/content/ja/service_management/events/pipelines_and_processors/_index.md b/content/ja/service_management/events/pipelines_and_processors/_index.md index a10d0f865ca..4bb95befcb8 100644 --- a/content/ja/service_management/events/pipelines_and_processors/_index.md +++ b/content/ja/service_management/events/pipelines_and_processors/_index.md @@ -54,12 +54,12 @@ Datadog Event Management Pipelines を活用すれば、組織はモニタリン [1]: https://app.datadoghq.com/event/pipelines [2]: https://app.datadoghq.com/event/explorer -[3]: /ja/service_management/events/pipelines_and_processors/arithmetic_processor -[4]: /ja/service_management/events/pipelines_and_processors/date_remapper -[5]: /ja/service_management/events/pipelines_and_processors/category_processor -[6]: /ja/service_management/events/pipelines_and_processors/grok_parser -[7]: /ja/service_management/events/pipelines_and_processors/lookup_processor -[8]: /ja/service_management/events/pipelines_and_processors/remapper -[9]: /ja/service_management/events/pipelines_and_processors/service_remapper -[10]: /ja/service_management/events/pipelines_and_processors/status_remapper -[11]: /ja/service_management/events/pipelines_and_processors/string_builder_processor \ No newline at end of file +[3]: /ja/events/pipelines_and_processors/arithmetic_processor +[4]: /ja/events/pipelines_and_processors/date_remapper +[5]: /ja/events/pipelines_and_processors/category_processor +[6]: /ja/events/pipelines_and_processors/grok_parser +[7]: /ja/events/pipelines_and_processors/lookup_processor +[8]: /ja/events/pipelines_and_processors/remapper +[9]: /ja/events/pipelines_and_processors/service_remapper +[10]: /ja/events/pipelines_and_processors/status_remapper +[11]: /ja/events/pipelines_and_processors/string_builder_processor \ No newline at end of file diff --git a/content/ja/service_management/events/pipelines_and_processors/grok_parser.md b/content/ja/service_management/events/pipelines_and_processors/grok_parser.md index 72722c8caec..1fd5c021364 100644 --- a/content/ja/service_management/events/pipelines_and_processors/grok_parser.md +++ b/content/ja/service_management/events/pipelines_and_processors/grok_parser.md @@ -6,7 +6,7 @@ title: Grok パーサー メッセージ全体や未加工のイベントの特定の属性をパースするためのカスタム Grok ルールを作成できます。ベストプラクティスとして、Grok プロセッサー毎のパース規則は最大 10 で使用することが推奨されます。 -{{< img src="service_management/events/grok-parser.png" alt="パース例 1" style="width:80%;">}} +{{< img src="events/grok-parser.png" alt="パース例 1" style="width:80%;">}} **Parse My Events** をクリックして、基底のパイプラインを流れるイベントの 3 つのパースルールのセットを始動させます。そこから属性の名前を絞り込み、必要に応じて他のタイプのイベントに新しいルールを追加します。この機能を使用するには、対応するイベントがインデックス化され、実際に流入している必要があります。除外フィルターを一時的に無効にするか、サンプリングして、これを機能させることができます。 @@ -657,5 +657,5 @@ MyParsingRule Usage\:\s+%{number:usage}%{data:ignore} [1]: https://github.com/google/re2/wiki/Syntax [2]: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones -[3]: /ja/service_management/events/pipelines_and_processors/date_remapper -[4]: /ja/service_management/events/pipelines_and_processors/grok_parser/?tab=filters&tabs=filters#matcher-and-filter \ No newline at end of file +[3]: /ja/events/pipelines_and_processors/date_remapper +[4]: /ja/events/pipelines_and_processors/grok_parser/?tab=filters&tabs=filters#matcher-and-filter \ No newline at end of file diff --git a/content/ja/synthetics/explore/_index.md b/content/ja/synthetics/explore/_index.md index 8118ab8cb75..d308ae3cdbd 100644 --- a/content/ja/synthetics/explore/_index.md +++ b/content/ja/synthetics/explore/_index.md @@ -15,7 +15,7 @@ further_reading: - link: /synthetics/explore/results_explorer tag: ドキュメント text: Learn about the Synthetic Monitoring & Testing Results Explorer -- link: /service_management/events/explorer +- link: /events/explorer tag: ドキュメント text: イベントエクスプローラーについて title: Synthetic テストの検索と管理 diff --git a/content/ja/watchdog/faulty_deployment_detection.md b/content/ja/watchdog/faulty_deployment_detection.md index 023c6a8d635..2826b7641f9 100644 --- a/content/ja/watchdog/faulty_deployment_detection.md +++ b/content/ja/watchdog/faulty_deployment_detection.md @@ -39,5 +39,5 @@ Watchdog は、新しいデプロイメントがエラーのもっともな原 - 新しいバージョンのエラー率は、以前のバージョンに比べて有意に高いわけではありませんでした。 - このエラーパターンは、たとえ新しいコードバージョンに欠陥がなくても、サービスをデプロイする際に一般的です。 -[2]: /ja/service_management/events/explorer +[2]: /ja/events/explorer [3]: https://app.datadoghq.com/monitors/create diff --git a/content/ko/account_management/org_settings.md b/content/ko/account_management/org_settings.md index b3465e0d349..cb8fb822fd0 100644 --- a/content/ko/account_management/org_settings.md +++ b/content/ko/account_management/org_settings.md @@ -151,7 +151,7 @@ Datadog의 기본 및 커스텀 역할에 대해 알아보려면 [역할 기반 [9]: /ko/account_management/rbac/ [10]: /ko/agent/remote_config/?tab=configurationyamlfile#how-it-works [11]: /ko/account_management/api-app-keys/#client-tokens -[12]: /ko/service_management/events/guides/email/ +[12]: /ko/events/guides/email/ [13]: /ko/synthetics/settings/?tab=specifyvalue#overview [14]: /ko/account_management/safety_center [15]: /ko/account_management/org_settings/oauth_apps \ No newline at end of file diff --git a/content/ko/administrators_guide/plan.md b/content/ko/administrators_guide/plan.md index b1a3bbd83e0..212bff6a021 100644 --- a/content/ko/administrators_guide/plan.md +++ b/content/ko/administrators_guide/plan.md @@ -344,7 +344,7 @@ Datadog을 설치할 때 과정을 현실적으로 개발 및 계획하는 것 [28]: /ko/integrations/network/ [29]: /ko/network_monitoring/cloud_network_monitoring/ [30]: /ko/software_catalog/ -[31]: /ko/service_management/events/ +[31]: /ko/events/ [32]: /ko/error_tracking/ [33]: /ko/software_catalog/endpoints/ [34]: /ko/agent/fleet_automation/ diff --git a/content/ko/developers/_index.md b/content/ko/developers/_index.md index 246c9713bf6..a5ffc42a371 100644 --- a/content/ko/developers/_index.md +++ b/content/ko/developers/_index.md @@ -105,7 +105,7 @@ Datadog에 지원되지 않는 데이터를 전송하는 방법을 결정하려 {{< whatsnext desc="Datadog에 제출할 수 있는 데이터 유형과 제출 방법을 알아보세요." >}} {{< nextlink href="/metrics" >}}커스텀 메트릭: Datadog의 커스텀 메트릭을 자세히 살펴보세요. 이 섹션은 메트릭 유형, 의미, 제출 방법, Datadog에서 활용되는 방법을 설명합니다.{{< /nextlink >}} - {{< nextlink href="service_management/events/guides/" >}}이벤트: 커스템 에이전트 검사, DogStatsD 또는 Datadog API를 통해 Datadog에 이벤트를 제출하는 방법을 살펴봅니다.{{< /nextlink >}} + {{< nextlink href="events/guides/" >}}이벤트: 커스템 에이전트 검사, DogStatsD 또는 Datadog API를 통해 Datadog에 이벤트를 제출하는 방법을 살펴봅니다.{{< /nextlink >}} {{< nextlink href="/developers/service_checks" >}}서비스 검사 : 특정 서비스의 업/다운 상태를 Datadog에 제출하는 방법을 살펴봅니다.{{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/ko/developers/dogstatsd/_index.md b/content/ko/developers/dogstatsd/_index.md index 797ebc701cc..c5a03123a40 100644 --- a/content/ko/developers/dogstatsd/_index.md +++ b/content/ko/developers/dogstatsd/_index.md @@ -566,7 +566,7 @@ DogStatsD와 StatsD는 대체로 유사하지만, DogStatsD에는 사용 가능 {{< whatsnext desc="">}} {{< nextlink href="/metrics/custom_metrics/dogstatsd_metrics_submission/" >}}DogStatsD를 사용하여 Datadog에 메트릭 전송.{{< /nextlink >}} -{{< nextlink href="/service_management/events/guides/dogstatsd/" >}}DogStatsD를 사용하여 Datadog에 이벤트 전송.{{< /nextlink >}} +{{< nextlink href="/events/guides/dogstatsd/" >}}DogStatsD를 사용하여 Datadog에 이벤트 전송.{{< /nextlink >}} {{< nextlink href="/developers/service_checks/dogstatsd_service_checks_submission/" >}}DogStatsD를 사용하여 Datadog에 서비스 검사 전송.{{< /nextlink >}} {{< /whatsnext >}} @@ -581,7 +581,7 @@ DogStatsD에서 사용하는 데이터그램 형식에 대해 자세히 알고 [3]: https://hub.docker.com/r/datadog/dogstatsd [4]: https://gcr.io/datadoghq/dogstatsd [5]: /ko/metrics/custom_metrics/ -[6]: /ko/service_management/events/guides/dogstatsd/ +[6]: /ko/events/guides/dogstatsd/ [7]: /ko/developers/service_checks/dogstatsd_service_checks_submission/ [8]: /ko/getting_started/tagging/unified_service_tagging [9]: /ko/developers/dogstatsd/datagram_shell/ \ No newline at end of file diff --git a/content/ko/developers/integrations/agent_integration.md b/content/ko/developers/integrations/agent_integration.md index a6389252e42..8fdb2858c15 100644 --- a/content/ko/developers/integrations/agent_integration.md +++ b/content/ko/developers/integrations/agent_integration.md @@ -486,7 +486,7 @@ Developer Platform에 안내된 단계를 따라 GitHub에서 리뷰할 수 있 [15]: /ko/developers/integrations/check_references/#service-check-file [16]: https://packaging.python.org/en/latest/tutorials/packaging-projects/ [17]: https://docs.datadoghq.com/ko/agent/ -[18]: https://docs.datadoghq.com/ko/service_management/events/ +[18]: https://docs.datadoghq.com/ko/events/ [19]: https://desktop.github.com/ [20]: https://docs.datadoghq.com/ko/developers/integrations/ [21]: https://github.com/Datadog/integrations-extras diff --git a/content/ko/dora_metrics/data_collected/_index.md b/content/ko/dora_metrics/data_collected/_index.md index 6d78ef0a65e..e41ca56b8e6 100644 --- a/content/ko/dora_metrics/data_collected/_index.md +++ b/content/ko/dora_metrics/data_collected/_index.md @@ -73,7 +73,7 @@ Datadog는 커밋 생성부터 배포까지 다양한 단계를 나타내는 메 {{< partial name="whats-next/whats-next.html" >}} -[1]: /ko/service_management/events/explorer/ +[1]: /ko/events/explorer/ [2]: /ko/api/latest/metrics/#query-timeseries-points [3]: /ko/api/latest/metrics/#query-timeseries-data-across-multiple-products [5]: https://app.datadoghq.com/event/explorer?query=source%3Asoftware_delivery_insights diff --git a/content/ko/events/guides/recommended_event_tags.md b/content/ko/events/guides/recommended_event_tags.md index 86988ddc9f2..f7a6c42e3d9 100644 --- a/content/ko/events/guides/recommended_event_tags.md +++ b/content/ko/events/guides/recommended_event_tags.md @@ -1,6 +1,6 @@ --- aliases: -- /ko/service_management/events/guides/recommended_event_tags/ +- /ko/events/guides/recommended_event_tags/ description: 권장 이벤트 태그 및 그 추가 방법에 대해 알아보세요. further_reading: - link: /getting_started/tagging/assigning_tags diff --git a/content/ko/getting_started/application/_index.md b/content/ko/getting_started/application/_index.md index 7b2671372e3..1947b9f2140 100644 --- a/content/ko/getting_started/application/_index.md +++ b/content/ko/getting_started/application/_index.md @@ -146,8 +146,8 @@ Datadog [Cloud SIEM][21](보안 정보 및 이벤트 관리)는 자동으로 애 [7]: /ko/infrastructure/ [8]: /ko/getting_started/tagging/ [9]: /ko/infrastructure/hostmap/ -[10]: /ko/service_management/events/ -[11]: /ko/service_management/events/explorer/analytics +[10]: /ko/events/ +[11]: /ko/events/explorer/analytics [12]: /ko/dashboards/ [13]: /ko/dashboards/#screenboards [14]: /ko/dashboards/functions/arithmetic/ diff --git a/content/ko/getting_started/tagging/using_tags.md b/content/ko/getting_started/tagging/using_tags.md index a07b49f82dd..6ebe88a42bd 100644 --- a/content/ko/getting_started/tagging/using_tags.md +++ b/content/ko/getting_started/tagging/using_tags.md @@ -378,7 +378,7 @@ SLO 태그는 SLO의 기초 메트릭이나 모니터링에 사용된 메트릭 {{< partial name="whats-next/whats-next.html" >}} [1]: /ko/getting_started/tagging/assigning_tags/ -[2]: /ko/service_management/events/explorer +[2]: /ko/events/explorer [3]: /ko/integrations/ [4]: /ko/infrastructure/hostmap/ [5]: /ko/infrastructure/ diff --git a/content/ko/integrations/catchpoint.md b/content/ko/integrations/catchpoint.md index 023794d3e48..56929841c99 100644 --- a/content/ko/integrations/catchpoint.md +++ b/content/ko/integrations/catchpoint.md @@ -66,7 +66,7 @@ Catchpoint 통합을 통해 다음 작업을 실행할 수 있습니다. } ``` -Catchpoint는 알림을 직접 Datadog의 [Events Explorer](https://docs.datadoghq.com/service_management/events/)로 전송합니다. +Catchpoint는 알림을 직접 Datadog의 [Events Explorer](https://docs.datadoghq.com/events/)로 전송합니다. ![Catchpoint 이벤트](images/screenshot.png) diff --git a/content/ko/integrations/crowdstrike.md b/content/ko/integrations/crowdstrike.md index 634f6734d72..7eab119e71c 100644 --- a/content/ko/integrations/crowdstrike.md +++ b/content/ko/integrations/crowdstrike.md @@ -102,7 +102,7 @@ CrowdStrike 통합에는 서비스 점검이 포함되어 있지 않습니다. 도움이 필요하신가요? [Datadog 지원팀][8]에 문의하세요. [1]: https://www.crowdstrike.com/ -[2]: https://docs.datadoghq.com/ko/service_management/events/explorer/ +[2]: https://docs.datadoghq.com/ko/events/explorer/ [3]: https://supportportal.crowdstrike.com/ [4]: https://falcon.crowdstrike.com/support/api-clients-and-keys [5]: https://app.datadoghq.com/integrations/crowdstrike diff --git a/content/ko/integrations/guide/events-from-sns-emails.md b/content/ko/integrations/guide/events-from-sns-emails.md index 1768b7c55d2..4a1e445560d 100644 --- a/content/ko/integrations/guide/events-from-sns-emails.md +++ b/content/ko/integrations/guide/events-from-sns-emails.md @@ -37,7 +37,7 @@ AWS 콘솔의 SNS 주제로 돌아가서 구독 상태가 `Confirmed`인지 확 {{< partial name="whats-next/whats-next.html" >}} -[1]: /ko/service_management/events/guides/email/ +[1]: /ko/events/guides/email/ [2]: https://app.datadoghq.com/event/explorer [3]: /ko/monitors/types/event/ [4]: /ko/events/explorer/ diff --git a/content/ko/integrations/redmine.md b/content/ko/integrations/redmine.md index aa1941f6e2e..c37f5aa776b 100644 --- a/content/ko/integrations/redmine.md +++ b/content/ko/integrations/redmine.md @@ -57,5 +57,5 @@ Redmine 통합은 서비스 점검을 포함하지 않습니다. 도움이 필요하신가요? [Datadog 지원팀][3]에 문의하세요. [1]: https://app.datadoghq.com/integrations/redmine -[2]: https://docs.datadoghq.com/ko/service_management/events/explorer/ +[2]: https://docs.datadoghq.com/ko/events/explorer/ [3]: https://docs.datadoghq.com/ko/help/ \ No newline at end of file diff --git a/content/ko/logs/error_tracking/manage_data_collection.md b/content/ko/logs/error_tracking/manage_data_collection.md index 53c0f5e16e3..d65ec91139a 100644 --- a/content/ko/logs/error_tracking/manage_data_collection.md +++ b/content/ko/logs/error_tracking/manage_data_collection.md @@ -97,4 +97,4 @@ title: 데이터 수집 관리 [1]: https://app.datadoghq.com/error-tracking/settings/rules [2]: /ko/logs/error_tracking/#setup [3]: /ko/logs/explorer/search_syntax/ -[4]: /ko/service_management/events/ \ No newline at end of file +[4]: /ko/events/ \ No newline at end of file diff --git a/content/ko/logs/log_configuration/archives.md b/content/ko/logs/log_configuration/archives.md index 1c70cad90e0..d97423e9ebe 100644 --- a/content/ko/logs/log_configuration/archives.md +++ b/content/ko/logs/log_configuration/archives.md @@ -424,4 +424,4 @@ Datadog이 스토리지 버킷에 전달하는 로그 아카이브는 압축된 [12]: /ko/account_management/rbac/permissions#logs_read_index_data [13]: /ko/account_management/rbac/permissions#logs_read_data [14]: /ko/logs/explorer/live_tail/ -[15]: /ko/service_management/events/explorer/ +[15]: /ko/events/explorer/ diff --git a/content/ko/metrics/guide/rate-limit.md b/content/ko/metrics/guide/rate-limit.md index 057e02f24b3..fc84555a2e5 100644 --- a/content/ko/metrics/guide/rate-limit.md +++ b/content/ko/metrics/guide/rate-limit.md @@ -64,7 +64,7 @@ Datadog이 카디널리티 증가를 감지하면 속도 제한이 적용되기 {{< partial name="whats-next/whats-next.html" >}} [1]: /ko/account_management/billing/custom_metrics/?tab=countrate#effect-of-adding-tags -[2]: https://docs.datadoghq.com/ko/service_management/events/ +[2]: https://docs.datadoghq.com/ko/events/ [3]: https://docs.datadoghq.com/ko/monitors/types/event/ [4]: https://docs.datadoghq.com/ko/metrics/guide/custom_metrics_governance/ [5]: https://docs.datadoghq.com/ko/help/ \ No newline at end of file diff --git a/content/ko/monitors/downtimes/_index.md b/content/ko/monitors/downtimes/_index.md index 5c7e6593db0..2d6497980b6 100644 --- a/content/ko/monitors/downtimes/_index.md +++ b/content/ko/monitors/downtimes/_index.md @@ -193,7 +193,7 @@ Datadog은 특정 클라우드 워크로드의 수동 종료와 관련된 모니 [10]: /ko/integrations/#cat-notification [11]: https://app.datadoghq.com/monitors/downtimes [12]: /ko/monitors/manage/status/ -[13]: /ko/service_management/events/explorer +[13]: /ko/events/explorer [14]: /ko/api/latest/downtimes/#cancel-a-downtime [15]: /ko/account_management/#preferences [16]: /ko/integrations/amazon_ec2/#ec2-automuting diff --git a/content/ko/monitors/guide/integrate-monitors-with-statuspage.md b/content/ko/monitors/guide/integrate-monitors-with-statuspage.md index df60bbec19f..8d0d24b77d2 100644 --- a/content/ko/monitors/guide/integrate-monitors-with-statuspage.md +++ b/content/ko/monitors/guide/integrate-monitors-with-statuspage.md @@ -59,7 +59,7 @@ Statuspage 알림을 트리거하는 [메트릭 모니터][8]을 생성하는 [1]: https://www.atlassian.com/software/statuspage [2]: /ko/integrations/statuspage -[3]: /ko/service_management/events/explorer/ +[3]: /ko/events/explorer/ [4]: https://app.datadoghq.com/integrations [5]: https://app.datadoghq.com/event/explorer [6]: /ko/dashboards/guide/custom_time_frames/ diff --git a/content/ko/service_management/events/_index.md b/content/ko/service_management/events/_index.md index 651b869c2a7..5146d17454e 100644 --- a/content/ko/service_management/events/_index.md +++ b/content/ko/service_management/events/_index.md @@ -7,7 +7,7 @@ further_reading: - link: /api/latest/events/ tag: 설명서 text: Datadog Events API -- link: /service_management/events/guides/recommended_event_tags/ +- link: /events/guides/recommended_event_tags/ tag: 설명서 text: Tagging Events에 대한 모범 사례 - link: https://www.datadoghq.com/blog/identify-sensitive-data-leakage-in-apm-rum-with-sensitive-data-scanner/ @@ -23,7 +23,7 @@ is_beta: true title: Event Management --- -{{< img src="service_management/events/correlation/event_management.png" alt="이벤트 관리란?" style="width:100%;" >}} +{{< img src="events/correlation/event_management.png" alt="이벤트 관리란?" style="width:100%;" >}} ## 개요 @@ -34,11 +34,11 @@ title: Event Management ## 구성 요소 {{< whatsnext desc="Event Management 기능:">}} - {{< nextlink href="/service_management/events/ingest/" >}}이벤트 수집 - Datadog에 이벤트를 보내는 방법 알아보기{{< /nextlink >}} - {{< nextlink href="/service_management/events/pipelines_and_processors/">}}파이프라인 및 프로세서 - 이벤트 강화 및 정규화{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/" >}}Events Explorer - Datadog으로 들어오는 이벤트의 알림 확인, 검색 및 전송{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/usage/" >}}이벤트 사용 - 이벤트 분석, 조사 및 모니터링{{< /nextlink >}} - {{< nextlink href="/service_management/events/correlation/" >}}상호 연관 - 알림 피로도 및 수신 티켓/알림 수 조정{{< /nextlink >}} + {{< nextlink href="/events/ingest/" >}}이벤트 수집 - Datadog에 이벤트를 보내는 방법 알아보기{{< /nextlink >}} + {{< nextlink href="/events/pipelines_and_processors/">}}파이프라인 및 프로세서 - 이벤트 강화 및 정규화{{< /nextlink >}} + {{< nextlink href="/events/explorer/" >}}Events Explorer - Datadog으로 들어오는 이벤트의 알림 확인, 검색 및 전송{{< /nextlink >}} + {{< nextlink href="/events/guides/usage/" >}}이벤트 사용 - 이벤트 분석, 조사 및 모니터링{{< /nextlink >}} + {{< nextlink href="/events/correlation/" >}}상호 연관 - 알림 피로도 및 수신 티켓/알림 수 조정{{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/ko/service_management/events/correlation/_index.md b/content/ko/service_management/events/correlation/_index.md index fa2aabcacff..8092ffabf16 100644 --- a/content/ko/service_management/events/correlation/_index.md +++ b/content/ko/service_management/events/correlation/_index.md @@ -6,7 +6,7 @@ algolia: - 상관관계 패턴 disable_toc: false further_reading: -- link: service_management/events/ +- link: events/ tag: 설명서 text: 이벤트 관리 - link: service_management/case_management/ @@ -22,9 +22,9 @@ title: 상관관계 * 단일 문제에 대해 해당 팀 전부의 협업 가능 {{< whatsnext desc="Get Started:">}} - {{< nextlink href="/service_management/events/correlation/configuration" >}}상관관계 - 두 가지 서로 다른 상관관계 유형으로 시작해 보세요.{{< /nextlink >}} - {{< nextlink href="/service_management/events/correlation/triage_and_notify/" >}}우선순위 및 알림 - 생성된 상관관계에 대한 티켓을 확인하고, 우선순위를 지정하고, 일림을 받거나 이를 수신하세요.{{< /nextlink >}} - {{< nextlink href="/service_management/events/correlation/analytics/" >}}분석 - 서비스별 개수, 할당된 사례 수 등 상관관계에 대한 메트릭을 분석하고 조사하세요.{{< /nextlink >}} + {{< nextlink href="/events/correlation/configuration" >}}상관관계 - 두 가지 서로 다른 상관관계 유형으로 시작해 보세요.{{< /nextlink >}} + {{< nextlink href="/events/correlation/triage_and_notify/" >}}우선순위 및 알림 - 생성된 상관관계에 대한 티켓을 확인하고, 우선순위를 지정하고, 일림을 받거나 이를 수신하세요.{{< /nextlink >}} + {{< nextlink href="/events/correlation/analytics/" >}}분석 - 서비스별 개수, 할당된 사례 수 등 상관관계에 대한 메트릭을 분석하고 조사하세요.{{< /nextlink >}} {{< /whatsnext >}} ## 참고 자료 diff --git a/content/ko/service_management/events/correlation/analytics.md b/content/ko/service_management/events/correlation/analytics.md index affb22b8028..99be39c13ae 100644 --- a/content/ko/service_management/events/correlation/analytics.md +++ b/content/ko/service_management/events/correlation/analytics.md @@ -1,6 +1,6 @@ --- further_reading: -- link: service_management/events/correlation/ +- link: events/correlation/ tag: 설명서 text: 이벤트 상관관계 title: 케이스 및 이벤트 분석 @@ -13,7 +13,7 @@ title: 케이스 및 이벤트 분석 ## 케이스 메트릭 -{{< img src="service_management/events/correlation/case_analytics.png" alt="케이스 분석 설정" style="width:100%;" >}} +{{< img src="events/correlation/case_analytics.png" alt="케이스 분석 설정" style="width:100%;" >}} 다양한 그래프 위젯에서 케이스 분석을 쿼리하여 팀 생산성을 분석하고 문제의 패턴을 식별할 수 있습니다. Dashboards와 Notebooks 모두에 분석 그래프를 표시합니다. 시작하려면 위젯 설정의 *Graph your data* 섹션 아래 데이터 소스 드롭다운에서 **Cases**를 선택합니다. @@ -34,7 +34,7 @@ title: 케이스 및 이벤트 분석 소스, 호스트, 서비스 등을 기준으로 이벤트 메트릭을 분류합니다. 알림이 어디서 발생하는지 알아보고 시간이 지남에 따라 운영 부하가 증가하거나 감소하는지 알아보세요. -{{< img src="service_management/events/correlation/event_analytics.png" alt="이벤트 분석 설정" style="width:100%;" >}} +{{< img src="events/correlation/event_analytics.png" alt="이벤트 분석 설정" style="width:100%;" >}} 시작하려면 위젯 설정의 *Graph your data* 섹션 아래 데이터 소스 드롭다운에서 **Events**를 선택합니다. diff --git a/content/ko/service_management/events/correlation/configuration.md b/content/ko/service_management/events/correlation/configuration.md index 613a18a119d..7e72fd51f07 100644 --- a/content/ko/service_management/events/correlation/configuration.md +++ b/content/ko/service_management/events/correlation/configuration.md @@ -1,9 +1,9 @@ --- further_reading: -- link: service_management/events/correlation/triage_and_notify +- link: events/correlation/triage_and_notify tag: 설명서 text: 사례 심사 및 알림에 대해 더 알아보기 -- link: service_management/events/correlation/analytics +- link: events/correlation/analytics tag: 설명서 text: 사례 분석 title: 구성 diff --git a/content/ko/service_management/events/correlation/intelligent.md b/content/ko/service_management/events/correlation/intelligent.md index b8ebe09c95c..91b0c84770c 100644 --- a/content/ko/service_management/events/correlation/intelligent.md +++ b/content/ko/service_management/events/correlation/intelligent.md @@ -1,6 +1,6 @@ --- further_reading: -- link: service_management/events/correlation/triage_and_notify +- link: events/correlation/triage_and_notify tag: 설명서 text: 사례 심사 및 알림에 대해 더 알아보기 title: 지능형 상관 관계 @@ -20,17 +20,17 @@ title: 지능형 상관 관계 1. 특정 팀이 심사하는 방법에 맞게 보기를 생성하고 사용자 지정하세요. 예를 들어 데이터베이스 팀에 맞는 보기를 하나 생성하고 모바일 팀에 맞는 보기를 별도로 생성할 수 있습니다. -{{< img src="service_management/events/correlation/intelligent/intelligent_config.png" alt="지능형 상관 관계 구성" style="width:100%;" >}} +{{< img src="events/correlation/intelligent/intelligent_config.png" alt="지능형 상관 관계 구성" style="width:100%;" >}} ## 첫 사례 수신 -{{< img src="service_management/events/correlation/intelligent/intelligent_project.png" alt="Event Management - Intelligent Correlation" style="width:100%;" >}} +{{< img src="events/correlation/intelligent/intelligent_project.png" alt="Event Management - Intelligent Correlation" style="width:100%;" >}} [Case Management][2]로 이동해 이름이 **Event Management - Intelligent Correlation**인 프로젝트를 찾으세요. 이 프로젝트에서 내가 이전에 생성한 보기와 지능형 상관 관계 기능으로 생성된 사례를 보기를 확인할 수 있습니다. 지능형 상관 관계에서는 관련 알림을 찾으면 자동으로 사례를 생성합니다. -{{< img src="service_management/events/correlation/intelligent/intelligent_correlation.png" alt="지능형 상관 관계 기능으로 생성된 케이스 상세 페이지, Investigation 탭에 관련 알림을 표시" style="width:100%;" >}} +{{< img src="events/correlation/intelligent/intelligent_correlation.png" alt="지능형 상관 관계 기능으로 생성된 케이스 상세 페이지, Investigation 탭에 관련 알림을 표시" style="width:100%;" >}} diff --git a/content/ko/service_management/events/correlation/patterns.md b/content/ko/service_management/events/correlation/patterns.md index 50273ec2f38..7ec6cd6f608 100644 --- a/content/ko/service_management/events/correlation/patterns.md +++ b/content/ko/service_management/events/correlation/patterns.md @@ -1,6 +1,6 @@ --- further_reading: -- link: service_management/events/correlation/triage_and_notify +- link: events/correlation/triage_and_notify tag: 설명서 text: 사례 심사 및 알림에 대해 알아보기 title: 패턴 기반 상관 관계 @@ -12,7 +12,7 @@ title: 패턴 기반 상관 관계 Datadog에서는 시작할 때 내 환경에 따라 자동으로 [패턴 기반 상관 관계][1]를 제안합니다. 추천 항목 중 하나를 클릭하면 추천 패턴의 구성을 열 수 있습니다. 구성 필드가 자동으로 채워져 있습니다. -{{< img src="service_management/events/correlation/pattern/recommended_patterns_preview.png" alt="미리 보기 패널에 패턴 기반 잠재 사례가 표시된 상관 관계 추천 패턴" style="width:100%;" >}} +{{< img src="events/correlation/pattern/recommended_patterns_preview.png" alt="미리 보기 패널에 패턴 기반 잠재 사례가 표시된 상관 관계 추천 패턴" style="width:100%;" >}} ## 패턴 생성 @@ -23,7 +23,7 @@ Datadog에서는 시작할 때 내 환경에 따라 자동으로 [패턴 기반 1. **+ Continue With Pattern**을 클릭해 추천 패턴을 수정할 수 있습니다. 그러면 필드가 미리 채워진 구성 페이지로 이동하고, 여기에서 추가 구성을 할 수 있습니다. 또는 **+ Personalize From Scratch**를 클릭해 나만의 패턴을 생성할 수 있습니다. 먼저 알림을 보내기 위해 이벤트 집계 키에 따라 이벤트가 복제됩니다. 그리고 구성에 따라 알림과 사례의 상관 관계가 수립됩니다. -{{< img src="service_management/events/correlation/correlation_helper.mp4" alt="이벤트가 정의된 소스 및 필터와 일치하면 알림으로 복제됩니다. 알림은 그룹화 속성에 따라 상관 관계가 수립되고, 새 사례에서 프로세스가 반복되기 전에 지정한 기간 안에 이벤트 복제가 취소됩니다. 설정에서 이 구성을 수정할 수 있습니다" video=true >}} +{{< img src="events/correlation/correlation_helper.mp4" alt="이벤트가 정의된 소스 및 필터와 일치하면 알림으로 복제됩니다. 알림은 그룹화 속성에 따라 상관 관계가 수립되고, 새 사례에서 프로세스가 반복되기 전에 지정한 기간 안에 이벤트 복제가 취소됩니다. 설정에서 이 구성을 수정할 수 있습니다" video=true >}} 집계 키로 이벤트를 전송하는 방법에 관한 자세한 정보는 [Datadog로 이벤트 전송][5]을 참고하세요. 집계 키가 없는 이벤트는 시간대 내에 중복 제거되어 단일 알림이 됩니다. ### 제안 패턴 @@ -67,7 +67,7 @@ Datadog에서는 시작할 때 내 환경에 따라 자동으로 [패턴 기반 이 데이터를 이용해 내 상관 관계에 있을 영향을 미리 보고 패턴의 예측 결과를 이해할 수 있습니다. -{{< img src="service_management/events/correlation/pattern/preview_pattern_output.png" alt="미리 보기 패널을 보여주는 패턴 기반 상관 관계. 패널에서 내 구성과 일치하는 수집 이벤트 수, 발생하게 될 중복 해제 수, 발생할 총 사례 수를 볼 수 있음." style="width:100%;" >}} +{{< img src="events/correlation/pattern/preview_pattern_output.png" alt="미리 보기 패널을 보여주는 패턴 기반 상관 관계. 패널에서 내 구성과 일치하는 수집 이벤트 수, 발생하게 될 중복 해제 수, 발생할 총 사례 수를 볼 수 있음." style="width:100%;" >}} **참고**: 미리 보기 사례의 기본값 제목은 상관 관계의 첫 알림입니다. 패턴을 저장하면 이벤트 관리 사례 제목이 알아보기 쉽게 생성됩니다. @@ -86,6 +86,6 @@ Datadog에서는 시작할 때 내 환경에 따라 자동으로 [패턴 기반 [1]: https://app.datadoghq.com/event/correlation [2]: https://app.datadoghq.com/event/correlation/rule/new -[3]: /ko/service_management/events/explorer/facets/#create-a-facet -[4]: /ko/service_management/events/explorer/facets -[5]: /ko/service_management/events/ingest/ \ No newline at end of file +[3]: /ko/events/explorer/facets/#create-a-facet +[4]: /ko/events/explorer/facets +[5]: /ko/events/ingest/ \ No newline at end of file diff --git a/content/ko/service_management/events/explorer/_index.md b/content/ko/service_management/events/explorer/_index.md index 48e76e75b58..da742a9a662 100644 --- a/content/ko/service_management/events/explorer/_index.md +++ b/content/ko/service_management/events/explorer/_index.md @@ -12,19 +12,19 @@ further_reading: title: 이벤트 익스플로러 --- -{{< img src="service_management/events/events-explorer.mp4" alt="속성별 이벤트 정렬 및 분석 탐색" video=true >}} +{{< img src="events/events-explorer.mp4" alt="속성별 이벤트 정렬 및 분석 탐색" video=true >}} 이벤트 탐색기를 사용하여 Datadog에 전송되는 이벤트를 집계하고 확인합니다. 속성별로 이벤트를 그룹화하거나 필터링하고 이벤트 분석을 사용하여 이벤트를 그래픽으로 표시합니다. 쿼리 구문을 사용하여 불리언 및 와일드카드 연산자로 이벤트를 필터링합니다. {{< whatsnext desc="이벤트 탐색기 기능" >}} - {{< nextlink href="/service_management/events/explorer/searching" >}}검색{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/navigate" >}}탐색기 살펴보기{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/customization" >}}커스터마이징{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/facets" >}}패싯{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/attributes" >}}속성{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/notifications" >}}알림 전송{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/analytics" >}}분석{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/saved_views" >}}저장된 보기{{< /nextlink >}} + {{< nextlink href="/events/explorer/searching" >}}검색{{< /nextlink >}} + {{< nextlink href="/events/explorer/navigate" >}}탐색기 살펴보기{{< /nextlink >}} + {{< nextlink href="/events/explorer/customization" >}}커스터마이징{{< /nextlink >}} + {{< nextlink href="/events/explorer/facets" >}}패싯{{< /nextlink >}} + {{< nextlink href="/events/explorer/attributes" >}}속성{{< /nextlink >}} + {{< nextlink href="/events/explorer/notifications" >}}알림 전송{{< /nextlink >}} + {{< nextlink href="/events/explorer/analytics" >}}분석{{< /nextlink >}} + {{< nextlink href="/events/explorer/saved_views" >}}저장된 보기{{< /nextlink >}} {{< /whatsnext >}} ## 참고 자료 diff --git a/content/ko/service_management/events/explorer/analytics.md b/content/ko/service_management/events/explorer/analytics.md index 9d01d948b84..4116a2c4eac 100644 --- a/content/ko/service_management/events/explorer/analytics.md +++ b/content/ko/service_management/events/explorer/analytics.md @@ -17,10 +17,10 @@ title: 분석 쿼리를 사용하여 Events Analytics에 표시되는 내용을 관리합니다. 1. 그래프화할 속성 또는 태그를 선택한 뒤 이를 패싯으로 추가합니다. 패싯을 그래프화하면 변수의 고유 카운트 값이 표시됩니다. - {{< img src="service_management/events/explorer/facet-to-graph.png" alt="그래프화할 수 있는 패싯 목록을 표시" style="width:100%;" >}} + {{< img src="events/explorer/facet-to-graph.png" alt="그래프화할 수 있는 패싯 목록을 표시" style="width:100%;" >}} 2. 패싯을 사용하여 그래프를 그룹화합니다. 여기에서 속성을 사용하려면 속성을 패싯으로 추가해야 합니다. - {{< img src="service_management/events/explorer/split-graph.png" alt="데이터를 그룹화할 수 있는 패싯 목록을 표시" style="width:100%;" >}} + {{< img src="events/explorer/split-graph.png" alt="데이터를 그룹화할 수 있는 패싯 목록을 표시" style="width:100%;" >}} 3. 그래프의 시간 간격을 선택합니다. 글로벌 시간 프레임을 변경하면 사용 가능한 타임스텝 값 목록이 변경됩니다. 그 결과를 시계열, 테이블 또는 상위 목록으로 표시할 수 있습니다. - {{< img src="service_management/events/explorer/time-interval.png" alt="기본값인 5초를 포함해 가능한 시간 간격 목록을 표시" style="width:100%;" >}} + {{< img src="events/explorer/time-interval.png" alt="기본값인 5초를 포함해 가능한 시간 간격 목록을 표시" style="width:100%;" >}} 4. 선택된 측정값에 따라 상위 또는 하위 값을 표시하도록 선택합니다. - {{< img src="service_management/events/explorer/display-values.png" alt="값을 상단 혹은 하단에 표시할지 선택" style="width:100%;" >}} \ No newline at end of file + {{< img src="events/explorer/display-values.png" alt="값을 상단 혹은 하단에 표시할지 선택" style="width:100%;" >}} \ No newline at end of file diff --git a/content/ko/service_management/events/explorer/attributes.md b/content/ko/service_management/events/explorer/attributes.md index 2f9a1a11a56..b7d97467002 100644 --- a/content/ko/service_management/events/explorer/attributes.md +++ b/content/ko/service_management/events/explorer/attributes.md @@ -1,7 +1,7 @@ --- disable_toc: false further_reading: -- link: /service_management/events/explorer/facets +- link: /events/explorer/facets tag: 설명서 text: 이벤트 패싯에 대해 알아보기 - link: logs/processing/pipelines @@ -38,4 +38,4 @@ title: 예약된 속성 {{< partial name="whats-next/whats-next.html" >}} [1]: /ko/logs/log_configuration/processors/?tab=ui#remapper -[2]: /ko/service_management/events/explorer/facets \ No newline at end of file +[2]: /ko/events/explorer/facets \ No newline at end of file diff --git a/content/ko/service_management/events/explorer/facets.md b/content/ko/service_management/events/explorer/facets.md index 5153083cbb5..276cab9aec9 100644 --- a/content/ko/service_management/events/explorer/facets.md +++ b/content/ko/service_management/events/explorer/facets.md @@ -1,6 +1,6 @@ --- further_reading: -- link: service_management/events/explorer/attributes +- link: events/explorer/attributes tag: 설명서 text: 예약된 속성에 대해 알아보기 title: 패싯 @@ -12,7 +12,7 @@ title: 패싯 패싯에서는 속성 또는 태그의 고유 구성 요소를 표시하고, 표시되는 이벤트의 수와 같이 기본 분석 결과를 제공합니다. 패싯을 사용하면 주어진 속성을 기반으로 데이터세트를 피벗하거나 필터링할 수 있습니다. 필터링하려면 보고 싶은 값을 하나 선택하세요. -{{< img src="service_management/events/explorer/facets-location.png" alt="패싯 측면 패널" style="width:100%;" >}} +{{< img src="events/explorer/facets-location.png" alt="패싯 측면 패널" style="width:100%;" >}} ### 패싯 생성 diff --git a/content/ko/service_management/events/explorer/navigate.md b/content/ko/service_management/events/explorer/navigate.md index 26d134da6ac..ac29d071142 100644 --- a/content/ko/service_management/events/explorer/navigate.md +++ b/content/ko/service_management/events/explorer/navigate.md @@ -2,7 +2,7 @@ title: 탐색기 사용 방법 --- -{{< img src="service_management/events/explorer/navigate.png" alt="Event Explorer 탐색하는 방법" style="width:100%;" >}} +{{< img src="events/explorer/navigate.png" alt="Event Explorer 탐색하는 방법" style="width:100%;" >}} ## 개요 @@ -14,7 +14,7 @@ Events Explorer에 있는 이벤트 하나를 클릭하면 이벤트 측면 패 ### 속성 탭 -{{< img src="service_management/events/explorer/event-attribute.png" alt="Event Attribute 탭 예시" style="width:100%;" >}} +{{< img src="events/explorer/event-attribute.png" alt="Event Attribute 탭 예시" style="width:100%;" >}} 측면 패널의 속성 탭에는 이벤트 속성이 JSON 목록으로 표시됩니다. 속성을 클릭해 기존 쿼리에 추가 또는 제외하거나, 속성의 열을 추가할 수 있습니다. diff --git a/content/ko/service_management/events/explorer/saved_views.md b/content/ko/service_management/events/explorer/saved_views.md index 8b23c0b596c..6ab13418bed 100644 --- a/content/ko/service_management/events/explorer/saved_views.md +++ b/content/ko/service_management/events/explorer/saved_views.md @@ -1,6 +1,6 @@ --- further_reading: -- link: /service_management/events/explorer/ +- link: /events/explorer/ tag: 설명서 text: 이벤트 탐색기에 대해 자세히 알아보기 title: 저장된 보기 @@ -46,5 +46,5 @@ title: 저장된 보기 {{< partial name="whats-next/whats-next.html" >}} [1]: https://app.datadoghq.com/event/explorer -[2]: /ko/service_management/events/explorer/searching -[3]: /ko/service_management/events/explorer/searching \ No newline at end of file +[2]: /ko/events/explorer/searching +[3]: /ko/events/explorer/searching \ No newline at end of file diff --git a/content/ko/service_management/events/guides/_index.md b/content/ko/service_management/events/guides/_index.md index 36d761ac9a3..e2eebf59963 100644 --- a/content/ko/service_management/events/guides/_index.md +++ b/content/ko/service_management/events/guides/_index.md @@ -10,7 +10,7 @@ cascade: subcategory: 이벤트 가이드 disable_toc: true further_reading: -- link: /service_management/events/explorer/ +- link: /events/explorer/ tag: 설명서 text: Datadog Events Explorer - link: /monitors/types/event/ diff --git a/content/ko/service_management/events/guides/migrating_to_new_events_features.md b/content/ko/service_management/events/guides/migrating_to_new_events_features.md index c995aa1c1f3..54b1aea9b06 100644 --- a/content/ko/service_management/events/guides/migrating_to_new_events_features.md +++ b/content/ko/service_management/events/guides/migrating_to_new_events_features.md @@ -45,18 +45,18 @@ Events Explorer는 인프라스트럭처와 서비스 또는 모니터링 경고 ### 이벤트 애널리틱스 -{{< img src="service_management/events/events-analytics.png" alt="'source:cloudtrail'로 필터링된 Event Analytics 표시 화면" >}} +{{< img src="events/events-analytics.png" alt="'source:cloudtrail'로 필터링된 Event Analytics 표시 화면" >}} Events Explorer에서 이벤트를 보고 검색하는 것 외에도 이제 시계열, 상위 목록 또는 표로 그래프 표시를 하고 주어진 쿼리에 대한 이벤트 수를 그룹화할 수 있습니다. 자세한 내용은 [Event Analytics][2]를 참조하세요. 또한 모든 이벤트 검색 쿼리에서 15개월 리텐션이 설정된 [메트릭을 생성][3]하여 과거 이벤트를 기반으로 모니터 및 경고를 생성할 수 있습니다. -{{< img src="service_management/events/generate-metrics.png" alt="이벤트 검색 쿼리가 포함된 메트릭 이미지." >}} +{{< img src="events/generate-metrics.png" alt="이벤트 검색 쿼리가 포함된 메트릭 이미지." >}} ### 대시보드의 그래프 이벤트 -{{< img src="service_management/events/graph-events.png" alt="Events Analytics">}} +{{< img src="events/graph-events.png" alt="Events Analytics">}} 이제 대시보드 내에서 주어진 쿼리에 대한 이벤트를 시계열 그래프, 쿼리값, 상위 목록, 표 등으로 그래프 표시를 할 수 있습니다. @@ -68,7 +68,7 @@ Events Explorer에서 이벤트를 보고 검색하는 것 외에도 이제 시 이벤트 모니터를 생성할 때 새 쿼리 검색 필드는 레거시 공백 채우기 쿼리가 아닌 자동 완성을 사용합니다. -{{< img src="service_management/events/guides/events-migration-monitor-new.png" alt="모니터 쿼리 구문을 위한 새로운 UI" style="width:100%;" >}} +{{< img src="events/guides/events-migration-monitor-new.png" alt="모니터 쿼리 구문을 위한 새로운 UI" style="width:100%;" >}} 새 쿼리 검색을 사용하면 Boolean 연산자 또는 와일드카드와 같은 새로운 기능으로 이벤트 모니터에서 복잡한 쿼리를 사용할 수 있습니다. @@ -194,10 +194,10 @@ Zabbix 또는 Prometheus가 오늘 서비스에 대한 경고를 트리거했습 {{< partial name="whats-next/whats-next.html" >}} -[1]: /ko/service_management/events/explorer -[2]: /ko/service_management/events/explorer/analytics -[3]: /ko/service_management/events/usage/#custom-metrics +[1]: /ko/events/explorer +[2]: /ko/events/explorer/analytics +[3]: /ko/events/usage/#custom-metrics [4]: https://app.datadoghq.com/dash/integration/30532/monitor-notifications-overview -[5]: /ko/service_management/events/guides/new_events_sources/ +[5]: /ko/events/guides/new_events_sources/ [6]: /ko/help/ [7]: /ko/api/latest/monitors/#create-a-monitor \ No newline at end of file diff --git a/content/ko/service_management/events/guides/recommended_event_tags.md b/content/ko/service_management/events/guides/recommended_event_tags.md index 91562a74b61..79215af4d07 100644 --- a/content/ko/service_management/events/guides/recommended_event_tags.md +++ b/content/ko/service_management/events/guides/recommended_event_tags.md @@ -42,7 +42,7 @@ Datadog은 다음과 같은 이점을 위해 모든 이벤트에 [통합 서비 {{< partial name="whats-next/whats-next.html" >}} [1]: /ko/getting_started/tagging/unified_service_tagging -[2]: /ko/service_management/events/explorer +[2]: /ko/events/explorer [3]: /ko/api/latest/events/#post-an-event [4]: /ko/getting_started/monitors/#notify-your-team [5]: /ko/getting_started/tagging/assigning_tags diff --git a/content/ko/service_management/events/ingest.md b/content/ko/service_management/events/ingest.md index c6624a98ba6..43eac615a0a 100644 --- a/content/ko/service_management/events/ingest.md +++ b/content/ko/service_management/events/ingest.md @@ -16,9 +16,9 @@ Datadog API, Custom Agent Check, DogStatsD, 또는 Events Email API를 사용하 {{< whatsnext desc="Datadog에 커스텀 이벤트 전송:">}} {{< nextlink href="/api/latest/events/#post-an-event" >}}Datadog API{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/agent/" >}}Custom Agent Check{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/email/" >}}이메일{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/dogstatsd/" >}}DogStatsD{{< /nextlink >}} + {{< nextlink href="/events/guides/agent/" >}}Custom Agent Check{{< /nextlink >}} + {{< nextlink href="/events/guides/email/" >}}이메일{{< /nextlink >}} + {{< nextlink href="/events/guides/dogstatsd/" >}}DogStatsD{{< /nextlink >}} {{< nextlink href="/integrations/guide/events-from-sns-emails/" >}}Amazon SNS 이메일{{< /nextlink >}} {{< nextlink href="/logs/guide/sending-events-and-logs-to-datadog-with-amazon-eventbridge-api-destinations/#configuration" >}}Amazon EventBridge API Destinations{{< /nextlink >}} {{< /whatsnext >}} \ No newline at end of file diff --git a/content/ko/service_management/events/pipelines_and_processors/_index.md b/content/ko/service_management/events/pipelines_and_processors/_index.md index a6c40a9b4d3..269eb9433bd 100644 --- a/content/ko/service_management/events/pipelines_and_processors/_index.md +++ b/content/ko/service_management/events/pipelines_and_processors/_index.md @@ -30,12 +30,12 @@ title: 파이프라인 및 프로세서 -[1]: /ko/service_management/events/pipelines_and_processors/arithmetic_processor -[2]: /ko/service_management/events/pipelines_and_processors/date_remapper -[3]: /ko/service_management/events/pipelines_and_processors/category_processor -[4]: /ko/service_management/events/pipelines_and_processors/grok_parser -[5]: /ko/service_management/events/pipelines_and_processors/lookup_processor -[6]: /ko/service_management/events/pipelines_and_processors/remapper -[7]: /ko/service_management/events/pipelines_and_processors/service_remapper -[8]: /ko/service_management/events/pipelines_and_processors/status_remapper -[9]: /ko/service_management/events/pipelines_and_processors/string_builder_processor \ No newline at end of file +[1]: /ko/events/pipelines_and_processors/arithmetic_processor +[2]: /ko/events/pipelines_and_processors/date_remapper +[3]: /ko/events/pipelines_and_processors/category_processor +[4]: /ko/events/pipelines_and_processors/grok_parser +[5]: /ko/events/pipelines_and_processors/lookup_processor +[6]: /ko/events/pipelines_and_processors/remapper +[7]: /ko/events/pipelines_and_processors/service_remapper +[8]: /ko/events/pipelines_and_processors/status_remapper +[9]: /ko/events/pipelines_and_processors/string_builder_processor \ No newline at end of file diff --git a/content/ko/service_management/events/pipelines_and_processors/grok_parser.md b/content/ko/service_management/events/pipelines_and_processors/grok_parser.md index 5ad297449b7..8ee4789e629 100644 --- a/content/ko/service_management/events/pipelines_and_processors/grok_parser.md +++ b/content/ko/service_management/events/pipelines_and_processors/grok_parser.md @@ -6,7 +6,7 @@ title: Grok 파서 원시 이벤트의 전체 메시지 또는 특정 속성을 파싱하는 커스텀 grok 규칙을 만듭니다. 모범 사례로, grok 프로세서 내에서 최대 10개의 파싱 규칙을 사용하는 것이 좋습니다. -{{< img src="service_management/events/grok-parser.png" alt="파싱 예제 1" style="width:80%;">}} +{{< img src="events/grok-parser.png" alt="파싱 예제 1" style="width:80%;">}} **내 이벤트 파싱**을 클릭하여 기본 파이프라인을 통해 흐르는 이벤트에 대한 세 가지 파싱 규칙 세트를 시작합니다. 속성 이름을 구체화하고, 필요한 경우 다른 유형의 이벤트에 대한 새 규칙을 추가합니다. 이 기능을 사용하려면 해당 이벤트가 인덱싱되어 실제로 수신되는 상태여야 합니다. 작동을 위해 임시로 예외 필터를 비활성화하거나 샘플링할 수 있습니다. @@ -657,5 +657,5 @@ MyParsingRule Usage\:\s+%{number:usage}%{data:ignore} [1]: https://github.com/google/re2/wiki/Syntax [2]: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones -[3]: /ko/service_management/events/pipelines_and_processors/date_remapper -[4]: /ko/service_management/events/pipelines_and_processors/grok_parser/?tab=filters&tabs=filters#matcher-and-filter \ No newline at end of file +[3]: /ko/events/pipelines_and_processors/date_remapper +[4]: /ko/events/pipelines_and_processors/grok_parser/?tab=filters&tabs=filters#matcher-and-filter \ No newline at end of file diff --git a/content/ko/service_management/events/triage_inbox.md b/content/ko/service_management/events/triage_inbox.md index a0d6d13ef9a..1d0110a51be 100644 --- a/content/ko/service_management/events/triage_inbox.md +++ b/content/ko/service_management/events/triage_inbox.md @@ -1,9 +1,9 @@ --- further_reading: -- link: /service_management/events/ingest// +- link: /events/ingest// tag: doc text: Datadog에 이벤트 전송 -- link: /service_management/events/correlation/ +- link: /events/correlation/ tag: doc text: 이벤트 상관관계에 대해 자세히 알아보기 - link: https://www.datadoghq.com/blog/datadog-event-management/ @@ -20,7 +20,7 @@ Datadog Event Management의 [Triage Inbox][4]는 다양한 소스에서 발생 케이스 트리아지 및 조사는 Triage Inbox에서 시작되며, 여기에서 수신된 케이스를 정렬, 필터링, 관리할 수 있습니다. Datadog 내부뿐 아니라 외부의 팀원과도 협업하여 대응을 조율할 수 있습니다. 이후 필요에 따라 케이스의 우선순위를 지정하고, 담당자를 할당하며, 조사 및 에스컬레이션하여 보다 신속한 해결을 이끌 수 있습니다. -{{< img src="/service_management/events/triage_inbox/event_mgmt_inbox.mp4" alt="우선순위별 정렬, 상태 및 우선순위 변경 기능을 갖춘 Event Management Inbox" video=true >}} +{{< img src="/events/triage_inbox/event_mgmt_inbox.mp4" alt="우선순위별 정렬, 상태 및 우선순위 변경 기능을 갖춘 Event Management Inbox" video=true >}} ## 시작하기 @@ -44,7 +44,7 @@ Datadog Event Management의 [Triage Inbox][4]는 다양한 소스에서 발생 - **이슈 에스컬레이션:** [Incident Management][1], [On-Call][2], [Workflow Automation][3] 또는 타사 도구를 사용하여 인시던트를 트리거하거나 온콜 담당자에게 페이지를 보낼 수 있습니다. - **외부 도구와 동기화:** Jira 및 ServiceNow 레코드를 동기화하여 외부 이해관계자가 최신 상태를 유지할 수 있도록 합니다. - {{< img src="/service_management/events/triage_inbox/event_mgmt_inbox_right_hand_panel.png" alt="Event Management 인박스 오른쪽 패널, Escalate 드롭다운 강조 표시" style="width:100%;" >}} + {{< img src="/events/triage_inbox/event_mgmt_inbox_right_hand_panel.png" alt="Event Management 인박스 오른쪽 패널, Escalate 드롭다운 강조 표시" style="width:100%;" >}} ## 조치 diff --git a/content/ko/watchdog/faulty_deployment_detection.md b/content/ko/watchdog/faulty_deployment_detection.md index df4efaa325f..14e7042773a 100644 --- a/content/ko/watchdog/faulty_deployment_detection.md +++ b/content/ko/watchdog/faulty_deployment_detection.md @@ -39,5 +39,5 @@ Watchdog에서는 새 배포에 오류 원인이 있는지 확인합니다. 그 - 새 버전의 오류율이 이전 버전에 비해 그렇게 높은 수준이 아닙니다. - 해당 오류 패턴이 새 코드 버전에 결함이 없더라도 나타날 수 있는, 서비스 배포 중 나타나는 일반적인 현상입니다. -[2]: /ko/service_management/events/explorer +[2]: /ko/events/explorer [3]: https://app.datadoghq.com/monitors/create \ No newline at end of file