diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml index d0ffa89f272..169b21ec859 100644 --- a/config/_default/menus/main.en.yaml +++ b/config/_default/menus/main.en.yaml @@ -6,8 +6,8 @@ menu: - name: In The App identifier: platform_heading weight: 2000000 - - name: Service Management - identifier: service_management_heading + - name: Incident Response + identifier: incident_response_heading weight: 3000000 - name: Actions & Remediations identifier: actions_heading @@ -1436,42 +1436,6 @@ menu: identifier: cloudcraft_api_users_info parent: cloudcraft_api_users weight: 1 - - name: Watchdog - url: watchdog/ - identifier: watchdog_top_level - pre: watchdog - parent: platform_heading - weight: 60000 - - name: Alerts - url: watchdog/alerts - identifier: watchdog_alerts - parent: watchdog_top_level - weight: 1 - - name: Impact Analysis - url: watchdog/impact_analysis/ - identifier: watchdog_impact_analysis - parent: watchdog_top_level - weight: 2 - - name: RCA - url: watchdog/rca/ - identifier: watchdog_rca - parent: watchdog_top_level - weight: 3 - - name: Insights - identifier: watchdog_insights - url: watchdog/insights - parent: watchdog_top_level - weight: 4 - - name: Faulty Deployment Detection - url: watchdog/faulty_deployment_detection/ - identifier: watchdog_faulty_deployment_detection - parent: watchdog_top_level - weight: 5 - - name: Faulty Cloud & SaaS API Detection - url: watchdog/faulty_cloud_saas_api_detection - parent: watchdog_top_level - weight: 6 - identifier: watchdog_faulty_cloud_saas_api_detection - name: Bits AI url: bits_ai/ pre: bits-ai @@ -1964,6 +1928,42 @@ menu: weight: 11 parent: alerting identifier: alerting_guide + - name: Service Level Objectives + url: service_level_objectives/ + pre: slos + weight: 70000 + parent: platform_heading + identifier: slos + - name: Monitor-based SLOs + url: service_level_objectives/monitor/ + parent: slos + identifier: slos_monitor + weight: 1 + - name: Metric-based SLOs + url: service_level_objectives/metric/ + parent: slos + identifier: slos_metric + weight: 2 + - name: Time Slice SLOs + url: service_level_objectives/time_slice/ + parent: slos + identifier: slos_time_slice + weight: 3 + - name: Error Budget Alerts + url: service_level_objectives/error_budget/ + parent: slos + identifier: error_budget + weight: 4 + - name: Burn Rate Alerts + url: service_level_objectives/burn_rate/ + parent: slos + identifier: burn_rate + weight: 5 + - name: Guides + url: service_level_objectives/guide/ + parent: slos + identifier: slos_guides + weight: 6 - name: Metrics url: metrics/ identifier: metrics_top_level @@ -2085,6 +2085,42 @@ menu: parent: metrics_top_level identifier: metrics_guide weight: 14 + - name: Watchdog + url: watchdog/ + identifier: watchdog_top_level + pre: watchdog + parent: platform_heading + weight: 90000 + - name: Alerts + url: watchdog/alerts + identifier: watchdog_alerts + parent: watchdog_top_level + weight: 1 + - name: Impact Analysis + url: watchdog/impact_analysis/ + identifier: watchdog_impact_analysis + parent: watchdog_top_level + weight: 2 + - name: RCA + url: watchdog/rca/ + identifier: watchdog_rca + parent: watchdog_top_level + weight: 3 + - name: Insights + identifier: watchdog_insights + url: watchdog/insights + parent: watchdog_top_level + weight: 4 + - name: Faulty Deployment Detection + url: watchdog/faulty_deployment_detection/ + identifier: watchdog_faulty_deployment_detection + parent: watchdog_top_level + weight: 5 + - name: Faulty Cloud & SaaS API Detection + url: watchdog/faulty_cloud_saas_api_detection + parent: watchdog_top_level + weight: 6 + identifier: watchdog_faulty_cloud_saas_api_detection - name: Internal Developer Portal url: internal_developer_portal/ pre: internal-developer-portal-wui @@ -2438,46 +2474,151 @@ menu: parent: change_tracking identifier: change_tracking_feature_flags weight: 1 - - name: Service Level Objectives - url: service_management/service_level_objectives/ - pre: slos - weight: 10000 - parent: service_management_heading - identifier: slos - - name: Monitor-based SLOs - url: service_management/service_level_objectives/monitor/ - parent: slos - identifier: slos_monitor + - name: Event Management + url: events/ + pre: events + identifier: events + parent: platform_heading + weight: 150000 + - name: Ingest Events + url: events/ingest/ + identifier: event_ingest + parent: events weight: 1 - - name: Metric-based SLOs - url: service_management/service_level_objectives/metric/ - parent: slos - identifier: slos_metric + - name: Pipelines and Processors + url: events/pipelines_and_processors/ + identifier: overview + parent: events weight: 2 - - name: Time Slice SLOs - url: service_management/service_level_objectives/time_slice/ - parent: slos - identifier: slos_time_slice + - name: Aggregation Key Processor + url: events/pipelines_and_processors/aggregation_key + identifier: aggregation_key_processor + parent: overview + weight: 201 + - name: Arithmetic Processor + url: events/pipelines_and_processors/arithmetic_processor + identifier: arithmetic_processor + parent: overview + weight: 202 + - name: Date Remapper + url: events/pipelines_and_processors/date_remapper + identifier: date_remapper + parent: overview + weight: 203 + - name: Category Processor + url: events/pipelines_and_processors/category_processor + identifier: category_processor + parent: overview + weight: 204 + - name: Grok Parser + url: events/pipelines_and_processors/grok_parser + identifier: grok_parser + parent: overview + weight: 205 + - name: Lookup Processor + url: events/pipelines_and_processors/lookup_processor + identifier: lookup_processor + parent: overview + weight: 206 + - name: Remapper + url: events/pipelines_and_processors/remapper + identifier: remapper + parent: overview + weight: 207 + - name: Service Remapper + url: events/pipelines_and_processors/service_remapper + identifier: service_remapper + parent: overview + weight: 208 + - name: Status Remapper + url: events/pipelines_and_processors/status_remapper + identifier: status_remapper + parent: overview + weight: 209 + - name: String Builder Processor + url: events/pipelines_and_processors/string_builder_processor + identifier: string_builder_processor + parent: overview + weight: 210 + - name: Explorer + url: events/explorer/ + identifier: events_explorer + parent: events weight: 3 - - name: Error Budget Alerts - url: service_management/service_level_objectives/error_budget/ - parent: slos - identifier: error_budget + - name: Searching + url: events/explorer/searching + identifier: events_explorer_searching + parent: events_explorer + weight: 301 + - name: Navigate the Explorer + url: events/explorer/navigate + identifier: events_explorer_navigate + parent: events_explorer + weight: 302 + - name: Customization + url: events/explorer/customization + identifier: events_explorer_customization + parent: events_explorer + weight: 303 + - name: Facets + url: events/explorer/facets + identifier: events_explorer_facets + parent: events_explorer + weight: 304 + - name: Attributes + url: events/explorer/attributes + identifier: events_explorer_attributes + parent: events_explorer + weight: 305 + - name: Notifications + url: events/explorer/notifications + identifier: event_explorer_notifications + parent: events_explorer + weight: 306 + - name: Analytics + url: events/explorer/analytics + identifier: event_explorer_analytics + parent: events_explorer + weight: 307 + - name: Saved Views + url: events/explorer/saved_views + identifier: event_explorer_saved_views + parent: events_explorer + weight: 308 + - name: Triage Inbox + identifier: event_triage_inbox + url: events/triage_inbox + parent: events weight: 4 - - name: Burn Rate Alerts - url: service_management/service_level_objectives/burn_rate/ - parent: slos - identifier: burn_rate + - name: Correlation + url: events/correlation/ + identifier: event_correlation + parent: events weight: 5 + - name: Configuration + url: events/correlation/configuration + identifier: event_correlation_configure + parent: event_correlation + weight: 501 + - name: Triaging & Notifying + url: events/correlation/triage_and_notify + identifier: event_correlation_triage_and_notify + parent: event_correlation + weight: 502 + - name: Analytics + url: events/correlation/analytics + identifier: event_correlation_analytics + parent: event_correlation + weight: 503 - name: Guides - url: service_management/service_level_objectives/guide/ - parent: slos - identifier: slos_guides - weight: 6 + url: events/guides/ + identifier: events_guides + parent: events + weight: 10 - name: Incident Management url: service_management/incident_management/ pre: incidents - parent: service_management_heading + parent: incident_response_heading identifier: incidents weight: 20000 - name: Declare an Incident @@ -2598,7 +2739,7 @@ menu: - name: On-Call url: service_management/on-call/ pre: on-call - parent: service_management_heading + parent: incident_response_heading identifier: oncall weight: 30000 - name: Datadog Clipboard @@ -2654,154 +2795,13 @@ menu: - name: Status Pages url: service_management/status_pages/ pre: status-page-wui - parent: service_management_heading + parent: incident_response_heading identifier: status_pages weight: 40000 - - name: Event Management - url: service_management/events/ - pre: events - identifier: events - parent: service_management_heading - weight: 50000 - - name: Ingest Events - url: service_management/events/ingest/ - identifier: event_ingest - parent: events - weight: 1 - - name: Pipelines and Processors - url: service_management/events/pipelines_and_processors/ - identifier: overview - parent: events - weight: 2 - - name: Aggregation Key Processor - url: service_management/events/pipelines_and_processors/aggregation_key - identifier: aggregation_key_processor - parent: overview - weight: 201 - - name: Arithmetic Processor - url: service_management/events/pipelines_and_processors/arithmetic_processor - identifier: arithmetic_processor - parent: overview - weight: 202 - - name: Date Remapper - url: service_management/events/pipelines_and_processors/date_remapper - identifier: date_remapper - parent: overview - weight: 203 - - name: Category Processor - url: service_management/events/pipelines_and_processors/category_processor - identifier: category_processor - parent: overview - weight: 204 - - name: Grok Parser - url: service_management/events/pipelines_and_processors/grok_parser - identifier: grok_parser - parent: overview - weight: 205 - - name: Lookup Processor - url: service_management/events/pipelines_and_processors/lookup_processor - identifier: lookup_processor - parent: overview - weight: 206 - - name: Remapper - url: service_management/events/pipelines_and_processors/remapper - identifier: remapper - parent: overview - weight: 207 - - name: Service Remapper - url: service_management/events/pipelines_and_processors/service_remapper - identifier: service_remapper - parent: overview - weight: 208 - - name: Status Remapper - url: service_management/events/pipelines_and_processors/status_remapper - identifier: status_remapper - parent: overview - weight: 209 - - name: String Builder Processor - url: service_management/events/pipelines_and_processors/string_builder_processor - identifier: string_builder_processor - parent: overview - weight: 210 - - name: Explorer - url: service_management/events/explorer/ - identifier: events_explorer - parent: events - weight: 3 - - name: Searching - url: service_management/events/explorer/searching - identifier: events_explorer_searching - parent: events_explorer - weight: 301 - - name: Navigate the Explorer - url: service_management/events/explorer/navigate - identifier: events_explorer_navigate - parent: events_explorer - weight: 302 - - name: Customization - url: service_management/events/explorer/customization - identifier: events_explorer_customization - parent: events_explorer - weight: 303 - - name: Facets - url: service_management/events/explorer/facets - identifier: events_explorer_facets - parent: events_explorer - weight: 304 - - name: Attributes - url: service_management/events/explorer/attributes - identifier: events_explorer_attributes - parent: events_explorer - weight: 305 - - name: Notifications - url: service_management/events/explorer/notifications - identifier: event_explorer_notifications - parent: events_explorer - weight: 306 - - name: Analytics - url: service_management/events/explorer/analytics - identifier: event_explorer_analytics - parent: events_explorer - weight: 307 - - name: Saved Views - url: service_management/events/explorer/saved_views - identifier: event_explorer_saved_views - parent: events_explorer - weight: 308 - - name: Triage Inbox - identifier: event_triage_inbox - url: service_management/events/triage_inbox - parent: events - weight: 4 - - name: Correlation - url: service_management/events/correlation/ - identifier: event_correlation - parent: events - weight: 5 - - name: Configuration - url: service_management/events/correlation/configuration - identifier: event_correlation_configure - parent: event_correlation - weight: 501 - - name: Triaging & Notifying - url: service_management/events/correlation/triage_and_notify - identifier: event_correlation_triage_and_notify - parent: event_correlation - weight: 502 - - name: Analytics - url: service_management/events/correlation/analytics - identifier: event_correlation_analytics - parent: event_correlation - weight: 503 - - name: Guides - url: service_management/events/guides/ - identifier: events_guides - parent: events - weight: 10 - name: Case Management url: service_management/case_management/ pre: case-management - parent: service_management_heading + parent: incident_response_heading identifier: case_management weight: 60000 - name: Projects diff --git a/content/en/account_management/billing/incident_response.md b/content/en/account_management/billing/incident_response.md index 5031f212ef3..ce4e9154ec0 100644 --- a/content/en/account_management/billing/incident_response.md +++ b/content/en/account_management/billing/incident_response.md @@ -1,13 +1,13 @@ --- title: Incident Response Billing further_reading: -- link: "/service_management/incident_management/" +- link: "/incident_response/incident_management/" tag: "Documentation" text: "Incident Management" -- link: "/service_management/on-call/" +- link: "/incident_response/on-call/" tag: "Documentation" text: "On-Call" -- link: "/service_management/status_pages/" +- link: "/incident_response/status_pages/" tag: "Documentation" text: "Status Pages" --- @@ -132,12 +132,12 @@ Your monthly bill contains the following: {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/incident_management/ -[2]: /service_management/on-call/ +[1]: /incident_response/incident_management/ +[2]: /incident_response/on-call/ [3]: https://www.datadoghq.com/pricing/?product=incident-response#products [4]: https://app.datadoghq.com/billing/seats -[5]: /service_management/on-call/schedules/ -[6]: /service_management/on-call/escalation_policies/ -[7]: /service_management/on-call/profile_settings/#notification-preferences -[8]: /service_management/incident_management/investigate/timeline +[5]: /incident_response/on-call/schedules/ +[6]: /incident_response/on-call/escalation_policies/ +[7]: /incident_response/on-call/profile_settings/#notification-preferences +[8]: /incident_response/incident_management/investigate/timeline [9]: https://app.datadoghq.com/on-call/settings/notifications-preferences-admin diff --git a/content/en/account_management/billing/workflow_automation.md b/content/en/account_management/billing/workflow_automation.md index 0bf2d5c3af5..745264ac9fb 100644 --- a/content/en/account_management/billing/workflow_automation.md +++ b/content/en/account_management/billing/workflow_automation.md @@ -73,8 +73,8 @@ This means that if your automation originates from one of these services, those [6]: https://www.datadoghq.com/pricing/?product=infrastructure-monitoring#products [7]: /api/latest/workflow-automation/ [8]: /actions/workflows/ -[9]: /service_management/incident_management/ -[10]: /service_management/on-call/ +[9]: /incident_response/incident_management/ +[10]: /incident_response/on-call/ [11]: /actions/app_builder/ [12]: /api/latest/workflow-automation/#list-workflow-instances [13]: https://www.datadoghq.com/pricing/?product=workflow-automation#products \ No newline at end of file diff --git a/content/en/account_management/org_settings.md b/content/en/account_management/org_settings.md index 7233cfafe53..b56f9a9c57c 100644 --- a/content/en/account_management/org_settings.md +++ b/content/en/account_management/org_settings.md @@ -168,7 +168,7 @@ Users with the `Org Management` permission can enable or disable the idle time s [9]: /account_management/rbac/ [10]: /remote_configuration#how-it-works [11]: /account_management/api-app-keys/#client-tokens -[12]: /service_management/events/guides/email/ +[12]: /events/guides/email/ [13]: /synthetics/settings/?tab=specifyvalue#overview [14]: /account_management/safety_center [15]: /account_management/org_settings/oauth_apps diff --git a/content/en/account_management/rbac/granular_access.md b/content/en/account_management/rbac/granular_access.md index 41af75a7411..74c29217e24 100644 --- a/content/en/account_management/rbac/granular_access.md +++ b/content/en/account_management/rbac/granular_access.md @@ -52,9 +52,9 @@ A user with the `user_access_manage` permission can elevate their access to any [5]: /dashboards/widgets/powerpack/#powerpack-permissions [6]: /security/detection_rules/#restrict-edit-permissions [7]: /security/suppressions/#restrict-edit-permissions -[8]: /service_management/service_level_objectives/#permissions +[8]: /service_level_objectives/#permissions [9]: /synthetics/browser_tests/#permissions -[10]: /service_management/case_management/settings#granular-access-control +[10]: /incident_response/case_management/settings#granular-access-control [11]: /getting_started/integrations/#granular-access-control [12]: /reference_tables/#permissions [13]: /actions/app_builder/access_and_auth/#restrict-access-to-a-specific-app @@ -66,6 +66,6 @@ A user with the `user_access_manage` permission can elevate their access to any [19]: /real_user_monitoring [20]: /account_management/org_settings/cross_org_visibility/#permissions [21]: /sheets/#permissions -[22]: /service_management/on-call/#granular-access-control +[22]: /incident_response/on-call/#granular-access-control [23]: /observability_pipelines/configuration/access_control/ [24]: /logs/log_configuration/pipelines/#pipeline-permissions diff --git a/content/en/account_management/teams/_index.md b/content/en/account_management/teams/_index.md index d756eba6ec7..a9138509f4f 100644 --- a/content/en/account_management/teams/_index.md +++ b/content/en/account_management/teams/_index.md @@ -20,7 +20,7 @@ Team membership is flexible. Users can join teams, be added by other members, or ### Navigation -Access the team directory page from [Organization Settings][1] or by navigating to [**Service Management > Teams**][2]. The [team directory page][1] lists all teams within your organization. +Access the team directory page from [Organization Settings][1] or by navigating to [**Teams**][2]. The [team directory page][1] lists all teams within your organization. ### Create team @@ -161,11 +161,11 @@ To customize your team, see [Team Management][3]. [3]: /account_management/teams/manage/ [4]: /account_management/saml/mapping/#map-saml-attributes-to-teams [5]: /dashboards/#dashboard-details -[6]: /service_management/incident_management/ +[6]: /incident_response/incident_management/ [7]: /monitors/configuration/?tab=thresholdalert#add-metadata [8]: /infrastructure/resource_catalog/ [9]: /tracing/software_catalog/adding_metadata/#add-metadata-from-the-datadog-ui -[10]: /service_management/service_level_objectives/#slo-tags +[10]: /service_level_objectives/#slo-tags [11]: https://app.datadoghq.com/dashboard/lists [12]: https://app.datadoghq.com/services [13]: https://app.datadoghq.com/incidents diff --git a/content/en/account_management/teams/manage.md b/content/en/account_management/teams/manage.md index 14f417154d1..73ed3692cbe 100644 --- a/content/en/account_management/teams/manage.md +++ b/content/en/account_management/teams/manage.md @@ -84,9 +84,9 @@ In some cases, a team's membership cannot be directly modified within Datadog by With subteams, you can nest teams within each other to mimic your company's hierarchy in Datadog, allowing for a more complete and accurate ownership model. Subteams also provide an enhanced filtering experience; select a larger team (like a director-level group) to find all the data connected to any of its subteams. {{< img src="account_management/teams/teams_filter_hierarchies.png" alt="Filter Hierarchical Teams" >}} - -On the **Subteams** tab, you can add and remove existing teams. For a clear view of a team's place in its hierarchy, go to [**Service Management** > **Teams** > **Map View**][4], then search for the team by name. -To automate subteam management based on your organization’s hierarchical structure, use the [Teams APIs][5]. + +On the **Subteams** tab, you can add and remove existing teams. For a clear view of a team's place in its hierarchy, go to [**Teams** > **Map View**][4], then search for the team by name. +To automate subteam management based on your organization's hierarchical structure, use the [Teams APIs][5]. ## Manage teams through an identity provider diff --git a/content/en/administrators_guide/plan.md b/content/en/administrators_guide/plan.md index df1a6a85553..1f5c7452d1d 100644 --- a/content/en/administrators_guide/plan.md +++ b/content/en/administrators_guide/plan.md @@ -344,7 +344,7 @@ Create a detailed roll-out methodology in the [build][41] phase by focusing on t [28]: /integrations/network/ [29]: /network_monitoring/cloud_network_monitoring/ [30]: /software_catalog/ -[31]: /service_management/events/ +[31]: /events/ [32]: /error_tracking/ [33]: /software_catalog/endpoints/ [34]: /agent/fleet_automation/ diff --git a/content/en/all_guides.md b/content/en/all_guides.md index 2cf1328960a..59687a07ed2 100644 --- a/content/en/all_guides.md +++ b/content/en/all_guides.md @@ -18,11 +18,13 @@ Guides in the Datadog documentation are pages that provide background knowledge, {{< nextlink href="/metrics/guide" >}}    Metrics{{< /nextlink >}} {{< nextlink href="/notebooks/guide" >}}    Notebooks{{< /nextlink >}} {{< nextlink href="/monitors/guide" >}}    Alerting{{< /nextlink >}} +{{< nextlink href="/service_level_objectives/guide" >}}    SLOs{{< /nextlink >}} +{{< nextlink href="/events/guides" >}}    Events{{< /nextlink >}} {{< /whatsnext >}} -{{< whatsnext desc="Service Management:">}} -{{< nextlink href="/service_management/service_level_objectives/guide" >}}    SLOs{{< /nextlink >}} -{{< nextlink href="/service_management/events/guides" >}}    Events{{< /nextlink >}} +{{< whatsnext desc="Incident Response:">}} +{{< nextlink href="/incident_response/incident_management/guides/" >}}    Incident Management{{< /nextlink >}} +{{< nextlink href="/incident_response/on-call/guides/" >}}    On-Call{{< /nextlink >}} {{< /whatsnext >}} {{< whatsnext desc="Infrastructure:">}} diff --git a/content/en/bits_ai/bits_ai_sre/configure.md b/content/en/bits_ai/bits_ai_sre/configure.md index c2e80e3925e..538f32ba0c3 100644 --- a/content/en/bits_ai/bits_ai_sre/configure.md +++ b/content/en/bits_ai/bits_ai_sre/configure.md @@ -107,7 +107,7 @@ You can monitor user-initiated actions with [Audit Trail][11]. Events are sent w [2]: /monitors/notify [3]: https://docs.datadoghq.com/integrations/slack/?tab=datadogforslack [4]: https://app.datadoghq.com/bits-ai/settings/integrations -[5]: /service_management/case_management/projects +[5]: /incident_response/case_management/projects [6]: https://app.datadoghq.com/cases/settings [7]: https://app.datadoghq.com/integrations/confluence [8]: /account_management/rbac diff --git a/content/en/bits_ai/bits_ai_sre/investigate_issues.md b/content/en/bits_ai/bits_ai_sre/investigate_issues.md index b8d2e486665..be767cff320 100644 --- a/content/en/bits_ai/bits_ai_sre/investigate_issues.md +++ b/content/en/bits_ai/bits_ai_sre/investigate_issues.md @@ -136,6 +136,6 @@ The Reports tab enables you to track the number of investigations run over time [6]: https://app.datadoghq.com/monitors/manage [8]: /bits_ai/bits_ai_sre/configure#slack [9]: /bits_ai/bits_ai_sre/help_bits_learn/ -[10]: /service_management/on-call/pages/#page-from-notifications -[14]: /service_management/case_management/notifications_integrations/#third-party-tickets +[10]: /incident_response/on-call/pages/#page-from-notifications +[14]: /incident_response/case_management/notifications_integrations/#third-party-tickets [15]: /account_management/rbac/permissions/#bits-ai diff --git a/content/en/bits_ai/chat_with_bits_ai.md b/content/en/bits_ai/chat_with_bits_ai.md index 1bfb4e37b08..abdf3b9bf96 100644 --- a/content/en/bits_ai/chat_with_bits_ai.md +++ b/content/en/bits_ai/chat_with_bits_ai.md @@ -5,7 +5,7 @@ further_reading: - link: "bits_ai/" tag: "Documentation" text: "Bits AI Overview" -- link: "/service_management/incident_management/incident_ai" +- link: "/incident_response/incident_management/incident_ai" tag: "Documentation" text: "Coordinate incidents with Incident AI" aliases: diff --git a/content/en/containers/datadog_operator/crd_slo.md b/content/en/containers/datadog_operator/crd_slo.md index bc8b25774a3..08a2b9e677a 100644 --- a/content/en/containers/datadog_operator/crd_slo.md +++ b/content/en/containers/datadog_operator/crd_slo.md @@ -68,11 +68,11 @@ To create a [Service Level Objective][1] (SLO), you can use the Datadog Operator ### Additional examples [Metric-based SLO with Universal Service Monitoring][8] -[1]: /service_management/service_level_objectives/ +[1]: /service_level_objectives/ [2]: https://helm.sh/ [3]: https://kubernetes.io/docs/tasks/tools/install-kubectl/ [4]: /api/latest/service-level-objectives/#create-an-slo-object -[5]: /service_management/service_level_objectives/monitor/ -[6]: /service_management/service_level_objectives/metric/ +[5]: /service_level_objectives/monitor/ +[6]: /service_level_objectives/metric/ [7]: /api/latest/service-level-objectives/#create-an-slo-object [8]: https://github.com/DataDog/datadog-operator/blob/main/examples/datadogslo/metric-usm-example.yaml diff --git a/content/en/coscreen/_index.md b/content/en/coscreen/_index.md index 2864bb8991f..138de4e8849 100644 --- a/content/en/coscreen/_index.md +++ b/content/en/coscreen/_index.md @@ -146,5 +146,5 @@ For all the details on how CoScreen enables secure collaboration, read the [CoSc [6]: https://www.datadoghq.com/legal/privacy/ [7]: https://www.coscreen.co/security [8]: /security/sensitive_data_scanner/ -[9]: /service_management/incident_management/ +[9]: /incident_response/incident_management/ [10]: https://app.datadoghq.com/incidents/settings#Integrations \ No newline at end of file diff --git a/content/en/coterm/_index.md b/content/en/coterm/_index.md index 718eb8c799b..4d256480a54 100644 --- a/content/en/coterm/_index.md +++ b/content/en/coterm/_index.md @@ -50,7 +50,7 @@ You can review your recorded terminal sessions and process data in Datadog: [1]: https://app.datadoghq.com/organization-settings/api-keys [2]: /security/sensitive_data_scanner/ -[3]: /service_management/case_management/ +[3]: /incident_response/case_management/ [4]: http://app.datadoghq.com/event/explorer?query=source%3Acoterm_process_info [5]: https://app.datadoghq.com/logs?query=service%3Addcoterm [6]: https://app.datadoghq.com/terminal-streams \ No newline at end of file diff --git a/content/en/coterm/rules.md b/content/en/coterm/rules.md index a8b974e7785..ae2bec1fe6c 100644 --- a/content/en/coterm/rules.md +++ b/content/en/coterm/rules.md @@ -126,4 +126,4 @@ All Lua snippets are executed inside a sandboxed [Luau][3] runtime. CoTerm injec [3]: https://luau.org/ [4]: https://www.lua.org/pil/2.5.html [5]: https://www.lua.org/pil/2.1.html -[6]: /service_management/incident_management/ \ No newline at end of file +[6]: /incident_response/incident_management/ \ No newline at end of file diff --git a/content/en/coterm/usage.md b/content/en/coterm/usage.md index a8f6ed6eaaf..995b4664716 100644 --- a/content/en/coterm/usage.md +++ b/content/en/coterm/usage.md @@ -130,10 +130,10 @@ COTERM_BREAK_GLASS=true kubectl delete foo {{< partial name="whats-next/whats-next.html" >}} [1]: /sensitive_data_scanner/ -[2]: /service_management/events/ -[3]: /service_management/case_management/ +[2]: /events/ +[3]: /incident_response/case_management/ [4]: /coterm/rules -[5]: /service_management/incident_management/ +[5]: /incident_response/incident_management/ [6]: /coterm/install [7]: https://app.datadoghq.com/terminal-streams -[8]: /service_management/case_management/automation_rules/ \ No newline at end of file +[8]: /incident_response/case_management/automation_rules/ \ No newline at end of file diff --git a/content/en/dashboards/_index.md b/content/en/dashboards/_index.md index ef5a6ddf650..a5ecad90ed2 100644 --- a/content/en/dashboards/_index.md +++ b/content/en/dashboards/_index.md @@ -45,7 +45,7 @@ Dashboards provide real-time insights into the performance and health of systems {{< nextlink href="/dashboards/configure" >}}Configure: Overview of the configuration options for dashboards{{< /nextlink >}} {{< nextlink href="/dashboards/list" >}}Dashboard List: Search, view, or create dashboards and lists{{< /nextlink >}} {{< nextlink href="/dashboards/template_variables" >}}Template Variable: Dynamically filter widgets in a dashboard{{< /nextlink >}} - {{< nextlink href="/service_management/incident_management/datadog_clipboard/" >}}Datadog Clipboard{{< /nextlink >}} + {{< nextlink href="/incident_response/incident_management/datadog_clipboard/" >}}Datadog Clipboard{{< /nextlink >}} {{< nextlink href="/api/latest/dashboards" >}}API: Manage dashboards programmatically{{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/en/dashboards/guide/slo_data_source.md b/content/en/dashboards/guide/slo_data_source.md index 125a85bac71..78f3f15f995 100644 --- a/content/en/dashboards/guide/slo_data_source.md +++ b/content/en/dashboards/guide/slo_data_source.md @@ -2,7 +2,7 @@ title: Graph historical SLO data on Dashboards description: Display historical SLO data on dashboards using SLO widgets and timeseries visualizations for performance tracking. further_reading: -- link: "/service_management/service_level_objectives/" +- link: "/service_level_objectives/" tag: "Documentation" text: "Learn more about Service Level Objectives" - link: "/dashboards/widgets/slo" @@ -51,5 +51,5 @@ For SLOs that have [status corrections][2], you can enable or disable correction {{< partial name="whats-next/whats-next.html" >}} [1]: /dashboards/sharing/scheduled_reports/ -[2]: /service_management/service_level_objectives/#slo-status-corrections -[3]: /service_management/service_level_objectives/#configuration +[2]: /service_level_objectives/#slo-status-corrections +[3]: /service_level_objectives/#configuration diff --git a/content/en/dashboards/guide/slo_graph_query.md b/content/en/dashboards/guide/slo_graph_query.md index 4db9402581f..c9c1b7b9f7d 100644 --- a/content/en/dashboards/guide/slo_graph_query.md +++ b/content/en/dashboards/guide/slo_graph_query.md @@ -50,5 +50,5 @@ The SLO widget filters the SLO metric queries by those additional tags for your {{< partial name="whats-next/whats-next.html" >}} [1]: /dashboards/widgets/slo/ -[2]: /service_management/service_level_objectives/metric/ +[2]: /service_level_objectives/metric/ [3]: /dashboards/template_variables/ diff --git a/content/en/dashboards/widgets/configuration/_index.md b/content/en/dashboards/widgets/configuration/_index.md index ac7d2735d0c..06eb4c57db2 100644 --- a/content/en/dashboards/widgets/configuration/_index.md +++ b/content/en/dashboards/widgets/configuration/_index.md @@ -187,5 +187,5 @@ Click on the context menu (three vertical dots) of any dashboard graph to open a [6]: /tracing/services/service_page/ [7]: /tracing/services/resource_page/ [8]: /dashboards/guide/custom_time_frames/ -[9]: /service_management/incident_management/datadog_clipboard/ +[9]: /incident_response/incident_management/datadog_clipboard/ [10]: /dashboards/widgets/split_graph/ \ No newline at end of file diff --git a/content/en/dashboards/widgets/geomap.md b/content/en/dashboards/widgets/geomap.md index bb96b4fcc3f..5f4728969f6 100644 --- a/content/en/dashboards/widgets/geomap.md +++ b/content/en/dashboards/widgets/geomap.md @@ -48,7 +48,7 @@ The geomap widget visualizes geographic data with shaded regions or points. It c [4]: /logs/logs_to_metrics/ [5]: /dashboards/querying/ [6]: /real_user_monitoring/explorer/search_syntax/ - [7]: /service_management/service_level_objectives/#searching-slos + [7]: /service_level_objectives/#searching-slos {{% /tab %}} {{% tab "Points" %}} diff --git a/content/en/dashboards/widgets/slo.md b/content/en/dashboards/widgets/slo.md index abdfff22176..206695b47f3 100644 --- a/content/en/dashboards/widgets/slo.md +++ b/content/en/dashboards/widgets/slo.md @@ -80,7 +80,7 @@ This widget can be used with the **[Dashboards API][3]**. See the following tabl {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/service_level_objectives/ +[1]: /service_level_objectives/ [2]: /dashboards/template_variables/ [3]: /api/latest/dashboards/ [4]: /dashboards/graphing_json/widget_json/ diff --git a/content/en/dashboards/widgets/slo_list.md b/content/en/dashboards/widgets/slo_list.md index fc6c1c9c985..bb09adec142 100644 --- a/content/en/dashboards/widgets/slo_list.md +++ b/content/en/dashboards/widgets/slo_list.md @@ -41,6 +41,6 @@ This widget can be used with the **[Dashboards API][2]**. See the following tabl {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/service_level_objectives/ +[1]: /service_level_objectives/ [2]: /api/latest/dashboards/ [3]: /dashboards/graphing_json/widget_json/ diff --git a/content/en/developers/dogstatsd/_index.md b/content/en/developers/dogstatsd/_index.md index e030d8bd341..6ce50f8b240 100644 --- a/content/en/developers/dogstatsd/_index.md +++ b/content/en/developers/dogstatsd/_index.md @@ -602,7 +602,7 @@ DogStatsD and StatsD are broadly similar, however, DogStatsD contains advanced f {{< whatsnext desc="">}} {{< nextlink href="/metrics/custom_metrics/dogstatsd_metrics_submission/" >}}Send metrics to Datadog with DogStatsD.{{< /nextlink >}} -{{< nextlink href="/service_management/events/guides/dogstatsd/" >}}Send events to Datadog with DogStatsD.{{< /nextlink >}} +{{< nextlink href="/events/guides/dogstatsd/" >}}Send events to Datadog with DogStatsD.{{< /nextlink >}} {{< nextlink href="/developers/service_checks/dogstatsd_service_checks_submission/" >}}Send service checks to Datadog with DogStatsD.{{< /nextlink >}} {{< /whatsnext >}} @@ -617,7 +617,7 @@ If you're interested in learning more about the datagram format used by DogStats [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/en/dora_metrics/_index.md b/content/en/dora_metrics/_index.md index 2335c4c6fa3..e8b3e2a4edb 100644 --- a/content/en/dora_metrics/_index.md +++ b/content/en/dora_metrics/_index.md @@ -17,7 +17,7 @@ further_reading: - link: "/continuous_delivery/deployments" tag: "Documentation" text: "Learn about Deployment Visibility" -- link: "/service_management/events" +- link: "/events" tag: "Documentation" text: "Learn about Event Management" - link: "/monitors/types/metric" diff --git a/content/en/dora_metrics/data_collected/_index.md b/content/en/dora_metrics/data_collected/_index.md index 6397159daba..94533ac7075 100644 --- a/content/en/dora_metrics/data_collected/_index.md +++ b/content/en/dora_metrics/data_collected/_index.md @@ -129,7 +129,7 @@ Using commit-level granularity provides a more accurate view of engineering perf {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/events/explorer/ +[1]: /events/explorer/ [2]: /api/latest/metrics/#query-timeseries-points [3]: /api/latest/metrics/#query-timeseries-data-across-multiple-products [5]: https://app.datadoghq.com/event/explorer?query=source%3Asoftware_delivery_insights @@ -142,5 +142,5 @@ Using commit-level granularity provides a more accurate view of engineering perf [12]: /dora_metrics/deployments/#limitations [13]: https://www.datadoghq.com/blog/service-catalog-setup/ [14]: https://app.datadoghq.com/incidents -[15]: /service_management/incident_management/describe#attributes +[15]: /incident_response/incident_management/describe#attributes [16]: /dora_metrics/ diff --git a/content/en/dora_metrics/setup/failures.md b/content/en/dora_metrics/setup/failures.md index d382f113f44..fc2d39293dc 100644 --- a/content/en/dora_metrics/setup/failures.md +++ b/content/en/dora_metrics/setup/failures.md @@ -56,7 +56,7 @@ If provided with incidents, the `Severity` tag is added to failure events. You can retroactively include incidents from the past two years by selecting **Backfill Data** in the [DORA settings][202], which creates failures from those incidents. Backfilling data can take up to an hour to complete. -[201]: /service_management/incident_management/ +[201]: /incident_response/incident_management/ [202]: https://app.datadoghq.com/ci/settings/dora [203]: https://app.datadoghq.com/incidents/settings?section=property-fields diff --git a/content/en/error_tracking/dynamic_sampling.md b/content/en/error_tracking/dynamic_sampling.md index 428f18fe009..83a1050c6ee 100644 --- a/content/en/error_tracking/dynamic_sampling.md +++ b/content/en/error_tracking/dynamic_sampling.md @@ -48,7 +48,7 @@ When Dynamic Sampling is applied, the following steps are recommended: {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/events/ +[1]: /events/ [2]: https://app.datadoghq.com/error-tracking/settings/rate-limits [3]: /logs/error_tracking/manage_data_collection#add-a-rule [4]: https://app.datadoghq.com/error-tracking/settings diff --git a/content/en/error_tracking/manage_data_collection.md b/content/en/error_tracking/manage_data_collection.md index b7e64e24d96..6e1adedd6ab 100644 --- a/content/en/error_tracking/manage_data_collection.md +++ b/content/en/error_tracking/manage_data_collection.md @@ -148,5 +148,5 @@ When Dynamic Sampling is applied, the following steps are recommended: [1]: https://app.datadoghq.com/error-tracking/settings/rules [2]: /error_tracking/troubleshooting/?tab=java#errors-are-not-found-in-error-tracking -[4]: /service_management/events/ +[4]: /events/ [5]: https://app.datadoghq.com/error-tracking/settings/rate-limits diff --git a/content/en/service_management/events/_index.md b/content/en/events/_index.md similarity index 72% rename from content/en/service_management/events/_index.md rename to content/en/events/_index.md index 610380608cf..6277e621938 100644 --- a/content/en/service_management/events/_index.md +++ b/content/en/events/_index.md @@ -3,12 +3,12 @@ title: Event Management aliases: - /guides/eventcorrelation/ - /guides/markdown/ -- /events +- /service_management/events/ further_reading: - link: "/api/latest/events/" tag: "Documentation" text: "Datadog Events API" -- link: "/service_management/events/guides/recommended_event_tags/" +- link: "/events/guides/recommended_event_tags/" tag: "Documentation" text: "Best Practices for Tagging Events" - link: "https://www.datadoghq.com/blog/identify-sensitive-data-leakage-in-apm-rum-with-sensitive-data-scanner/" @@ -40,12 +40,12 @@ More than 100 Datadog integrations support events collection, including [Kuberne ## Components {{< 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/triage_inbox" >}}Triage Inbox - Triage, investigate, collaborate, and resolve incidents{{< /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 fatigue and the number of tickets/notifications you receive {{< /nextlink >}} + {{< nextlink href="/events/ingest/" >}}Ingest events - Learn how to send events to Datadog{{< /nextlink >}} + {{< nextlink href="/events/triage_inbox" >}}Triage Inbox - Triage, investigate, collaborate, and resolve incidents{{< /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 fatigue and the number of tickets/notifications you receive {{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/en/service_management/events/correlation/_index.md b/content/en/events/correlation/_index.md similarity index 54% rename from content/en/service_management/events/correlation/_index.md rename to content/en/events/correlation/_index.md index 3be5d33ad76..434f689adb9 100644 --- a/content/en/service_management/events/correlation/_index.md +++ b/content/en/events/correlation/_index.md @@ -1,11 +1,13 @@ --- title: Correlation +aliases: +- /service_management/events/correlation/ disable_toc: false further_reading: - link: "service_management/events/" tag: "Documentation" text: "Event Management" -- link: "service_management/case_management/" +- link: "/incident_response/case_management/" tag: "Documentation" text: "Case Management" algolia: @@ -20,9 +22,9 @@ Event Correlation groups events based on their relationships or on user-defined * Have all affected teams to be aware of a single issue instead of working in silos {{< whatsnext desc="Get Started:">}} - {{< nextlink href="/service_management/events/correlation/configuration" >}}Correlation - Get started with our two different kinds of correlation{{< /nextlink >}} - {{< nextlink href="/service_management/events/correlation/triage_and_notify/" >}}Triage and Notify - View, triage, get notified or receive tickets about the correlations which have been created for you{{< /nextlink >}} - {{< nextlink href="/service_management/events/correlation/analytics/" >}}Analytics - Analyze, investigate, the metrics from correlations e.g the number of cases assigned, the number by service, etc {{< /nextlink >}} + {{< nextlink href="/events/correlation/configuration" >}}Correlation - Get started with our two different kinds of correlation{{< /nextlink >}} + {{< nextlink href="/events/correlation/triage_and_notify/" >}}Triage and Notify - View, triage, get notified or receive tickets about the correlations which have been created for you{{< /nextlink >}} + {{< nextlink href="/events/correlation/analytics/" >}}Analytics - Analyze, investigate, the metrics from correlations e.g the number of cases assigned, the number by service, etc {{< /nextlink >}} {{< /whatsnext >}} ## Further Reading diff --git a/content/en/service_management/events/correlation/analytics.md b/content/en/events/correlation/analytics.md similarity index 95% rename from content/en/service_management/events/correlation/analytics.md rename to content/en/events/correlation/analytics.md index 4bbf9c27606..c9ec9198b39 100644 --- a/content/en/service_management/events/correlation/analytics.md +++ b/content/en/events/correlation/analytics.md @@ -1,5 +1,7 @@ --- title: Analytics from Cases and Events +aliases: +- /service_management/events/correlation/analytics/ further_reading: - link: "service_management/events/correlation/" tag: "Documentation" diff --git a/content/en/service_management/events/correlation/configuration.md b/content/en/events/correlation/configuration.md similarity index 94% rename from content/en/service_management/events/correlation/configuration.md rename to content/en/events/correlation/configuration.md index 20cdeb59c75..223a99ecba7 100644 --- a/content/en/service_management/events/correlation/configuration.md +++ b/content/en/events/correlation/configuration.md @@ -1,5 +1,7 @@ --- title: Configuration +aliases: +- /service_management/events/correlation/configuration/ further_reading: - link: "service_management/events/correlation/triage_and_notify" tag: "Documentation" diff --git a/content/en/service_management/events/correlation/intelligent.md b/content/en/events/correlation/intelligent.md similarity index 96% rename from content/en/service_management/events/correlation/intelligent.md rename to content/en/events/correlation/intelligent.md index 2f01cb6324a..97725773269 100644 --- a/content/en/service_management/events/correlation/intelligent.md +++ b/content/en/events/correlation/intelligent.md @@ -1,5 +1,7 @@ --- title: Intelligent Correlation +aliases: +- /service_management/events/correlation/intelligent/ further_reading: - link: "service_management/events/correlation/triage_and_notify" tag: "Documentation" diff --git a/content/en/service_management/events/correlation/patterns.md b/content/en/events/correlation/patterns.md similarity index 97% rename from content/en/service_management/events/correlation/patterns.md rename to content/en/events/correlation/patterns.md index 8d1cf928198..8819fc78447 100644 --- a/content/en/service_management/events/correlation/patterns.md +++ b/content/en/events/correlation/patterns.md @@ -1,5 +1,7 @@ --- title: Pattern-based Correlation +aliases: +- /service_management/events/correlation/patterns/ further_reading: - link: "service_management/events/correlation/triage_and_notify" tag: "Documentation" @@ -86,6 +88,6 @@ After you update an existing pattern, all live cases will stop processing. New e [1]: https://app.datadoghq.com/event/correlation [2]: https://app.datadoghq.com/event/correlation/rule/new -[3]: /service_management/events/explorer/facets/#create-a-facet -[4]: /service_management/events/explorer/facets -[5]: /service_management/events/ingest/ +[3]: /events/explorer/facets/#create-a-facet +[4]: /events/explorer/facets +[5]: /events/ingest/ diff --git a/content/en/service_management/events/correlation/triage_and_notify.md b/content/en/events/correlation/triage_and_notify.md similarity index 93% rename from content/en/service_management/events/correlation/triage_and_notify.md rename to content/en/events/correlation/triage_and_notify.md index f91cc790486..ae353b5d487 100644 --- a/content/en/service_management/events/correlation/triage_and_notify.md +++ b/content/en/events/correlation/triage_and_notify.md @@ -1,5 +1,7 @@ --- title: Triage and Notify +aliases: +- /service_management/events/correlation/triage_and_notify/ further_reading: - link: "service_management/events/correlation/" tag: "Documentation" @@ -57,6 +59,6 @@ In case management, _views_ group cases based on a configured query. You can set [1]: https://app.datadoghq.com/event/correlation [2]: https://app.datadoghq.com/cases?query=status%3AOPEN%20creation_source%3AEVENT_MANAGEMENT&page=1&page-size=25&sort=created_at -[3]: /service_management/case_management/settings#set-up-integrations -[4]: /service_management/case_management/view_and_manage#create-a-view -[5]: /service_management/case_management/view_and_manage \ No newline at end of file +[3]: /incident_response/case_management/settings#set-up-integrations +[4]: /incident_response/case_management/view_and_manage#create-a-view +[5]: /incident_response/case_management/view_and_manage \ No newline at end of file diff --git a/content/en/events/explorer/_index.md b/content/en/events/explorer/_index.md new file mode 100644 index 00000000000..e2022f81479 --- /dev/null +++ b/content/en/events/explorer/_index.md @@ -0,0 +1,33 @@ +--- +title: Events Explorer +aliases: +- /events/stream/ +- /service_management/events/correlation/ +- service_management/events/explorer/ +further_reading: +- link: "/api/latest/events/" + tag: "Documentation" + text: "Datadog Events API" +- link: "https://www.datadoghq.com/blog/datadog-events/" + tag: "Blog" + 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 >}} + +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. + +{{< whatsnext desc="Features of the Events Explorer:" >}} + {{< nextlink href="/events/explorer/searching" >}}Searching{{< /nextlink >}} + {{< nextlink href="/events/explorer/navigate" >}}Navigate the Explorer{{< /nextlink >}} + {{< nextlink href="/events/explorer/customization" >}}Customization{{< /nextlink >}} + {{< nextlink href="/events/explorer/facets" >}}Facets{{< /nextlink >}} + {{< nextlink href="/events/explorer/attributes" >}}Attributes{{< /nextlink >}} + {{< nextlink href="/events/explorer/notifications" >}}Send notifications{{< /nextlink >}} + {{< nextlink href="/events/explorer/analytics" >}}Analytics{{< /nextlink >}} + {{< nextlink href="/events/explorer/saved_views" >}}Saved views{{< /nextlink >}} +{{< /whatsnext >}} + +## Further reading + +{{< partial name="whats-next/whats-next.html" >}} diff --git a/content/en/service_management/events/explorer/analytics.md b/content/en/events/explorer/analytics.md similarity index 96% rename from content/en/service_management/events/explorer/analytics.md rename to content/en/events/explorer/analytics.md index c6df3fc321d..96226120b49 100644 --- a/content/en/service_management/events/explorer/analytics.md +++ b/content/en/events/explorer/analytics.md @@ -1,5 +1,7 @@ --- title: Analytics +aliases: +- /service_management/events/explorer/analytics/ --- ## Overview diff --git a/content/en/service_management/events/explorer/attributes.md b/content/en/events/explorer/attributes.md similarity index 94% rename from content/en/service_management/events/explorer/attributes.md rename to content/en/events/explorer/attributes.md index d3d8dc508e7..42446dcdf79 100644 --- a/content/en/service_management/events/explorer/attributes.md +++ b/content/en/events/explorer/attributes.md @@ -1,8 +1,10 @@ --- title: Reserved Attributes +aliases: +- /service_management/events/explorer/attributes/ disable_toc: false further_reading: -- link: "/service_management/events/explorer/facets" +- link: "/events/explorer/facets" tag: "Documentation" text: "Learn about Event facets" - link: "logs/processing/pipelines" @@ -38,4 +40,4 @@ To create a facet on a tag that has the same key as a reserved attribute: {{< partial name="whats-next/whats-next.html" >}} [1]: /logs/log_configuration/processors/?tab=ui#remapper -[2]: /service_management/events/explorer/facets +[2]: /events/explorer/facets diff --git a/content/en/service_management/events/explorer/customization.md b/content/en/events/explorer/customization.md similarity index 90% rename from content/en/service_management/events/explorer/customization.md rename to content/en/events/explorer/customization.md index bc4dd1db310..f29bedc7c87 100644 --- a/content/en/service_management/events/explorer/customization.md +++ b/content/en/events/explorer/customization.md @@ -1,5 +1,7 @@ --- title: Customization +aliases: +- /service_management/events/explorer/customization/ --- Customize your Events Explorer to fit your visualization and analyzing needs. diff --git a/content/en/service_management/events/explorer/facets.md b/content/en/events/explorer/facets.md similarity index 94% rename from content/en/service_management/events/explorer/facets.md rename to content/en/events/explorer/facets.md index 8bf83957687..53fb4f734b9 100644 --- a/content/en/service_management/events/explorer/facets.md +++ b/content/en/events/explorer/facets.md @@ -1,5 +1,7 @@ --- title: Facets +aliases: +- /service_management/events/explorer/facets/ further_reading: - link: "service_management/events/explorer/attributes" tag: "Documentation" @@ -29,4 +31,4 @@ For Datadog monitor events, the first event tag in alphabetic order is used to s {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/events/correlation/patterns/ +[1]: /events/correlation/patterns/ diff --git a/content/en/service_management/events/explorer/navigate.md b/content/en/events/explorer/navigate.md similarity index 96% rename from content/en/service_management/events/explorer/navigate.md rename to content/en/events/explorer/navigate.md index 48587409b45..9a4f2e541bd 100644 --- a/content/en/service_management/events/explorer/navigate.md +++ b/content/en/events/explorer/navigate.md @@ -1,5 +1,7 @@ --- title: Navigate the Explorer +aliases: +- /service_management/events/explorer/navigate/ --- {{< img src="service_management/events/explorer/navigate.png" alt="How to navigate the Events Explorer" style="width:100%;" >}} diff --git a/content/en/service_management/events/explorer/notifications.md b/content/en/events/explorer/notifications.md similarity index 93% rename from content/en/service_management/events/explorer/notifications.md rename to content/en/events/explorer/notifications.md index d5b91264841..1f7236c9275 100644 --- a/content/en/service_management/events/explorer/notifications.md +++ b/content/en/events/explorer/notifications.md @@ -1,5 +1,7 @@ --- title: Notifications +aliases: +- /service_management/events/explorer/notifications/ disable_toc: false further_reading: - link: "/monitors/notify/" diff --git a/content/en/service_management/events/explorer/saved_views.md b/content/en/events/explorer/saved_views.md similarity index 93% rename from content/en/service_management/events/explorer/saved_views.md rename to content/en/events/explorer/saved_views.md index 64e340d8a2e..b3241fe5ac4 100644 --- a/content/en/service_management/events/explorer/saved_views.md +++ b/content/en/events/explorer/saved_views.md @@ -1,7 +1,9 @@ --- title: Saved Views +aliases: +- /service_management/events/explorer/saved_views/ further_reading: -- link: "/service_management/events/explorer/" +- link: "/events/explorer/" tag: "Documentation" text: "Learn more about the Events Explorer" --- @@ -46,5 +48,5 @@ In the default view entry in the **Views** panel, you can: {{< partial name="whats-next/whats-next.html" >}} [1]: https://app.datadoghq.com/event/explorer -[2]: /service_management/events/explorer/searching -[3]: /service_management/events/explorer/searching \ No newline at end of file +[2]: /events/explorer/searching +[3]: /events/explorer/searching \ No newline at end of file diff --git a/content/en/service_management/events/explorer/searching.md b/content/en/events/explorer/searching.md similarity index 95% rename from content/en/service_management/events/explorer/searching.md rename to content/en/events/explorer/searching.md index 12b705ed076..9c36277411b 100644 --- a/content/en/service_management/events/explorer/searching.md +++ b/content/en/events/explorer/searching.md @@ -1,5 +1,7 @@ --- title: Search Syntax +aliases: +- /service_management/events/explorer/searching/ further_reading: - link: "/getting_started/search/" tag: "Documentation" diff --git a/content/en/service_management/events/guides/_index.md b/content/en/events/guides/_index.md similarity index 54% rename from content/en/service_management/events/guides/_index.md rename to content/en/events/guides/_index.md index 42b288735a5..20ea23432b3 100644 --- a/content/en/service_management/events/guides/_index.md +++ b/content/en/events/guides/_index.md @@ -4,10 +4,9 @@ private: true disable_toc: true aliases: - /developers/events/ -- /event/guides/ -- /events/guides/ +- /service_management/events/guides/ further_reading: -- link: "/service_management/events/explorer/" +- link: "/events/explorer/" tag: "Documentation" text: "Datadog Events Explorer" - link: "/monitors/types/event/" @@ -23,22 +22,22 @@ cascade: An event represents any record of activity noteworthy for engineers (devs, ops, and security). {{< whatsnext desc="Send your custom events to Datadog:">}} - {{< nextlink href="/service_management/events/guides/agent/" >}}Custom Agent Check{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/dogstatsd/" >}}DogStatsD{{< /nextlink >}} - {{< nextlink href="/service_management/events/guides/email/" >}}Email{{< /nextlink >}} + {{< nextlink href="/events/guides/agent/" >}}Custom Agent Check{{< /nextlink >}} + {{< nextlink href="/events/guides/dogstatsd/" >}}DogStatsD{{< /nextlink >}} + {{< nextlink href="/events/guides/email/" >}}Email{{< /nextlink >}} {{< nextlink href="/api/v1/events/#post-an-event" >}}Datadog API{{< /nextlink >}} {{< /whatsnext >}} {{< whatsnext desc="Ensure your events are tagged:">}} - {{< nextlink href="/service_management/events/guides/recommended_event_tags/" >}}Best Practices for Tagging Events{{< /nextlink >}} + {{< nextlink href="/events/guides/recommended_event_tags/" >}}Best Practices for Tagging Events{{< /nextlink >}} {{< /whatsnext >}} {{< whatsnext desc="Learn more about Event Management use cases:">}} - {{< nextlink href="/service_management/events/guides/usage" >}}Use cases for events{{< /nextlink >}} + {{< nextlink href="/events/guides/usage" >}}Use cases for events{{< /nextlink >}} {{< /whatsnext >}} {{< whatsnext desc="Other guides:">}} - {{< nextlink href="/service_management/events/guides/migrating_to_new_events_features/" >}}Migrating to the New Events Features{{< /nextlink >}} + {{< nextlink href="/events/guides/migrating_to_new_events_features/" >}}Migrating to the New Events Features{{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/en/service_management/events/guides/agent.md b/content/en/events/guides/agent.md similarity index 99% rename from content/en/service_management/events/guides/agent.md rename to content/en/events/guides/agent.md index 134af9bc847..8414b0ee922 100644 --- a/content/en/service_management/events/guides/agent.md +++ b/content/en/events/guides/agent.md @@ -1,9 +1,7 @@ --- title: Events with a Custom Agent Check - aliases: -- /events/agent/ -- /events/guides/agent +- /service_management/events/guides/agent/ further_reading: - link: "/developers/custom_checks/write_agent_check/" tag: "Documentation" diff --git a/content/en/service_management/events/guides/dogstatsd.md b/content/en/events/guides/dogstatsd.md similarity index 99% rename from content/en/service_management/events/guides/dogstatsd.md rename to content/en/events/guides/dogstatsd.md index 45696e2a4c6..21cef2a6ca7 100644 --- a/content/en/service_management/events/guides/dogstatsd.md +++ b/content/en/events/guides/dogstatsd.md @@ -4,7 +4,7 @@ title: Events with DogStatsD description: Overview of the features of DogStatsD, including data types and tagging. aliases: - /developers/events/dogstatsd/ -- /events/guides/dogstatsd +- /service_management/events/guides/dogstatsd/ further_reading: - link: "/developers/dogstatsd/" tag: "Documentation" @@ -212,4 +212,4 @@ $statsd->event('An error occurred.', [1]: /developers/dogstatsd/ -[2]: /service_management/events/ +[2]: /events/ diff --git a/content/en/service_management/events/guides/email.md b/content/en/events/guides/email.md similarity index 99% rename from content/en/service_management/events/guides/email.md rename to content/en/events/guides/email.md index 87358ed9596..f4c6f8d3666 100644 --- a/content/en/service_management/events/guides/email.md +++ b/content/en/events/guides/email.md @@ -4,7 +4,7 @@ title: Events with email aliases: - /developers/events/email/ - /guides/eventsemail -- /events/guides/email +- /service_management/events/guides/email/ --- {{< site-region region="gov" >}} diff --git a/content/en/service_management/events/guides/migrating_to_new_events_features.md b/content/en/events/guides/migrating_to_new_events_features.md similarity index 97% rename from content/en/service_management/events/guides/migrating_to_new_events_features.md rename to content/en/events/guides/migrating_to_new_events_features.md index ea8aba64ce0..fc250059f50 100644 --- a/content/en/service_management/events/guides/migrating_to_new_events_features.md +++ b/content/en/events/guides/migrating_to_new_events_features.md @@ -1,9 +1,7 @@ --- title: Migrating to the New Events Features - aliases: -- /events/guides/migrating_from_stream_to_explorer -- /events/guides/migrating_to_new_events_features +- /service_management/events/guides/migrating_to_new_events_features/ further_reading: - link: "https://www.datadoghq.com/blog/datadog-events/" tag: "Blog" @@ -195,10 +193,10 @@ Legacy Event Monitors do not support cardinality rollup. {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/events/explorer -[2]: /service_management/events/explorer/analytics -[3]: /service_management/events/usage/#custom-metrics +[1]: /events/explorer +[2]: /events/explorer/analytics +[3]: /events/usage/#custom-metrics [4]: https://app.datadoghq.com/dash/integration/30532/monitor-notifications-overview -[5]: /service_management/events/guides/new_events_sources/ +[5]: /events/guides/new_events_sources/ [6]: /help/ [7]: /api/latest/monitors/#create-a-monitor diff --git a/content/en/service_management/events/guides/new_events_sources.md b/content/en/events/guides/new_events_sources.md similarity index 100% rename from content/en/service_management/events/guides/new_events_sources.md rename to content/en/events/guides/new_events_sources.md diff --git a/content/en/service_management/events/guides/recommended_event_tags.md b/content/en/events/guides/recommended_event_tags.md similarity index 97% rename from content/en/service_management/events/guides/recommended_event_tags.md rename to content/en/events/guides/recommended_event_tags.md index 99c7cc42ce2..05d90229b15 100644 --- a/content/en/service_management/events/guides/recommended_event_tags.md +++ b/content/en/events/guides/recommended_event_tags.md @@ -1,9 +1,8 @@ --- title: Best Practices For Tagging Events - -description: Learn about recommended event tags and how to add them. aliases: -- /events/guides/recommended_event_tags +- /service_management/events/guides/recommended_event_tags/ +description: Learn about recommended event tags and how to add them. further_reading: - link: "/getting_started/tagging/assigning_tags" tag: "Documentation" @@ -43,7 +42,7 @@ You can add the following core attributes to your events: {{< partial name="whats-next/whats-next.html" >}} [1]: /getting_started/tagging/unified_service_tagging -[2]: /service_management/events/explorer +[2]: /events/explorer [3]: /api/latest/events/#post-an-event [4]: /getting_started/monitors/#notify-your-services-and-your-team-members [5]: /getting_started/tagging/assigning_tags diff --git a/content/en/service_management/events/guides/usage.md b/content/en/events/guides/usage.md similarity index 94% rename from content/en/service_management/events/guides/usage.md rename to content/en/events/guides/usage.md index ac90d0ebf27..e8ca67c5632 100644 --- a/content/en/service_management/events/guides/usage.md +++ b/content/en/events/guides/usage.md @@ -2,11 +2,12 @@ title: Using Events aliases: - /service_management/events/usage +- /service_management/events/guides/usage/ further_reading: - link: "/logs/log_configuration/processors/" tag: "Documentation" text: "Learn more about processing pipelines" -- link: "/service_management/events/explorer/" +- link: "/events/explorer/" tag: "Documentation" text: "Triage events with the Events Explorer" --- @@ -49,8 +50,8 @@ Send monitor alerts and notifications based on significant event queries. To con [3]: https://app.datadoghq.com/event/pipelines [4]: /help/ [5]: https://app.datadoghq.com/event/configuration/generate-metrics -[6]: /service_management/events/explorer/analytics -[7]: /service_management/events/explorer/ +[6]: /events/explorer/analytics +[7]: /events/explorer/ [8]: /dashboards/widgets/alert_graph/ [9]: https://app.datadoghq.com/dash/integration/30532/monitor-notifications-overview [10]: /dashboards/change_overlays/ diff --git a/content/en/service_management/events/ingest.md b/content/en/events/ingest.md similarity index 79% rename from content/en/service_management/events/ingest.md rename to content/en/events/ingest.md index f26d6bf85bf..0e66228485c 100644 --- a/content/en/service_management/events/ingest.md +++ b/content/en/events/ingest.md @@ -1,5 +1,7 @@ --- title: Send Events to Datadog +aliases: +- /service_management/events/ingest/ --- ## Standard events @@ -16,9 +18,9 @@ You can also submit your own custom events using the Datadog API, Custom Agent C {{< whatsnext desc="Send your custom events to 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/" >}}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/" >}}Email{{< /nextlink >}} + {{< nextlink href="/events/guides/dogstatsd/" >}}DogStatsD{{< /nextlink >}} {{< nextlink href="/integrations/guide/events-from-sns-emails/" >}}Amazon SNS Emails{{< /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/en/service_management/events/pipelines_and_processors/_index.md b/content/en/events/pipelines_and_processors/_index.md similarity index 78% rename from content/en/service_management/events/pipelines_and_processors/_index.md rename to content/en/events/pipelines_and_processors/_index.md index 3cc10c2205a..42376cd5b63 100644 --- a/content/en/service_management/events/pipelines_and_processors/_index.md +++ b/content/en/events/pipelines_and_processors/_index.md @@ -1,11 +1,13 @@ --- title: Pipelines and Processors +aliases: +- /service_management/events/pipelines_and_processors/ description: Learn how to use Event Management Pipelines to process and enrich events from various sources with processors further_reading: -- link: "/service_management/events/" +- link: "/events/" tag: "Documentation" text: "Event Management" -- link: "/service_management/events/correlation/" +- link: "/events/correlation/" tag: "Documentation" text: "Event Correlation" --- @@ -59,13 +61,13 @@ You can add processors after you create a pipeline. The processors available are [1]: https://app.datadoghq.com/event/pipelines [2]: https://app.datadoghq.com/event/explorer -[3]: /service_management/events/pipelines_and_processors/aggregation_key -[4]: /service_management/events/pipelines_and_processors/arithmetic_processor -[5]: /service_management/events/pipelines_and_processors/date_remapper -[6]: /service_management/events/pipelines_and_processors/category_processor -[7]: /service_management/events/pipelines_and_processors/grok_parser -[8]: /service_management/events/pipelines_and_processors/lookup_processor -[9]: /service_management/events/pipelines_and_processors/remapper -[10]: /service_management/events/pipelines_and_processors/service_remapper -[11]: /service_management/events/pipelines_and_processors/status_remapper -[12]: /service_management/events/pipelines_and_processors/string_builder_processor +[3]: /events/pipelines_and_processors/aggregation_key +[4]: /events/pipelines_and_processors/arithmetic_processor +[5]: /events/pipelines_and_processors/date_remapper +[6]: /events/pipelines_and_processors/category_processor +[7]: /events/pipelines_and_processors/grok_parser +[8]: /events/pipelines_and_processors/lookup_processor +[9]: /events/pipelines_and_processors/remapper +[10]: /events/pipelines_and_processors/service_remapper +[11]: /events/pipelines_and_processors/status_remapper +[12]: /events/pipelines_and_processors/string_builder_processor diff --git a/content/en/service_management/events/pipelines_and_processors/aggregation_key.md b/content/en/events/pipelines_and_processors/aggregation_key.md similarity index 94% rename from content/en/service_management/events/pipelines_and_processors/aggregation_key.md rename to content/en/events/pipelines_and_processors/aggregation_key.md index d5b49b84812..cff10dd6468 100644 --- a/content/en/service_management/events/pipelines_and_processors/aggregation_key.md +++ b/content/en/events/pipelines_and_processors/aggregation_key.md @@ -1,5 +1,7 @@ --- title: Aggregation Key Processor +aliases: +- /service_management/events/pipelines_and_processors/aggregation_key/ description: Generate custom aggregation keys based on event attributes or tags to enable effective deduplication and improve event correlations --- @@ -22,5 +24,5 @@ The aggregation key processor performs the following actions: * If there are multiple values in the tag key, all values are sorted alphabetically and concatenated to generate the aggregation key. * Based on these values, it generates a hash and adds the generated aggregation key to the event. -[1]: /service_management/events/correlation/ +[1]: /events/correlation/ [2]: /getting_started/tagging/ \ No newline at end of file diff --git a/content/en/service_management/events/pipelines_and_processors/arithmetic_processor.md b/content/en/events/pipelines_and_processors/arithmetic_processor.md similarity index 94% rename from content/en/service_management/events/pipelines_and_processors/arithmetic_processor.md rename to content/en/events/pipelines_and_processors/arithmetic_processor.md index 271cfe4871b..4b93ac7f8d2 100644 --- a/content/en/service_management/events/pipelines_and_processors/arithmetic_processor.md +++ b/content/en/events/pipelines_and_processors/arithmetic_processor.md @@ -1,5 +1,7 @@ --- title: Arithmetic Processor +aliases: +- /service_management/events/pipelines_and_processors/arithmetic_processor/ description: Add a new attribute to an event with the result of a formula to remap time attributes or compute operations on event attributes --- diff --git a/content/en/service_management/events/pipelines_and_processors/category_processor.md b/content/en/events/pipelines_and_processors/category_processor.md similarity index 94% rename from content/en/service_management/events/pipelines_and_processors/category_processor.md rename to content/en/events/pipelines_and_processors/category_processor.md index 6e4339eca70..8e1088b58fb 100644 --- a/content/en/service_management/events/pipelines_and_processors/category_processor.md +++ b/content/en/events/pipelines_and_processors/category_processor.md @@ -1,5 +1,7 @@ --- title: Category Processor +aliases: +- /service_management/events/pipelines_and_processors/category_processor/ description: Add a new attribute to events matching a search query to create groups for analytical views --- diff --git a/content/en/service_management/events/pipelines_and_processors/date_remapper.md b/content/en/events/pipelines_and_processors/date_remapper.md similarity index 95% rename from content/en/service_management/events/pipelines_and_processors/date_remapper.md rename to content/en/events/pipelines_and_processors/date_remapper.md index 9e60c425290..68853c1b9f4 100644 --- a/content/en/service_management/events/pipelines_and_processors/date_remapper.md +++ b/content/en/events/pipelines_and_processors/date_remapper.md @@ -1,5 +1,7 @@ --- title: Date Remapper +aliases: +- /service_management/events/pipelines_and_processors/date_remapper/ description: Define a custom date attribute as the official event timestamp for events with dates not in the default attribute list --- diff --git a/content/en/service_management/events/pipelines_and_processors/grok_parser.md b/content/en/events/pipelines_and_processors/grok_parser.md similarity index 99% rename from content/en/service_management/events/pipelines_and_processors/grok_parser.md rename to content/en/events/pipelines_and_processors/grok_parser.md index d80b216d6e3..8c1f5a9f8ea 100644 --- a/content/en/service_management/events/pipelines_and_processors/grok_parser.md +++ b/content/en/events/pipelines_and_processors/grok_parser.md @@ -1,5 +1,7 @@ --- title: Grok Parser +aliases: +- /service_management/events/pipelines_and_processors/grok_parser/ description: Create custom grok rules to parse the full message or specific attributes of raw events into structured data --- @@ -659,5 +661,5 @@ If your events contain ASCII control characters, they are serialized upon ingest [1]: https://github.com/google/re2/wiki/Syntax [2]: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones -[3]: /service_management/events/pipelines_and_processors/date_remapper -[4]: /service_management/events/pipelines_and_processors/grok_parser/?tab=filters&tabs=filters#matcher-and-filter +[3]: /events/pipelines_and_processors/date_remapper +[4]: /events/pipelines_and_processors/grok_parser/?tab=filters&tabs=filters#matcher-and-filter diff --git a/content/en/service_management/events/pipelines_and_processors/lookup_processor.md b/content/en/events/pipelines_and_processors/lookup_processor.md similarity index 95% rename from content/en/service_management/events/pipelines_and_processors/lookup_processor.md rename to content/en/events/pipelines_and_processors/lookup_processor.md index cd593ba3af3..b2f85d3ace6 100644 --- a/content/en/service_management/events/pipelines_and_processors/lookup_processor.md +++ b/content/en/events/pipelines_and_processors/lookup_processor.md @@ -1,5 +1,7 @@ --- title: Lookup Processor +aliases: +- /service_management/events/pipelines_and_processors/lookup_processor/ description: Map event attributes to human-readable values using Reference Tables or manual mapping tables for event enrichment --- diff --git a/content/en/service_management/events/pipelines_and_processors/remapper.md b/content/en/events/pipelines_and_processors/remapper.md similarity index 93% rename from content/en/service_management/events/pipelines_and_processors/remapper.md rename to content/en/events/pipelines_and_processors/remapper.md index b059602c7bf..d874be478c0 100644 --- a/content/en/service_management/events/pipelines_and_processors/remapper.md +++ b/content/en/events/pipelines_and_processors/remapper.md @@ -1,5 +1,7 @@ --- title: Remapper +aliases: +- /service_management/events/pipelines_and_processors/remapper/ description: Remap source attributes or tags to target attributes or tags with optional type casting --- diff --git a/content/en/service_management/events/pipelines_and_processors/service_remapper.md b/content/en/events/pipelines_and_processors/service_remapper.md similarity index 87% rename from content/en/service_management/events/pipelines_and_processors/service_remapper.md rename to content/en/events/pipelines_and_processors/service_remapper.md index 1ca9f838d14..669cad001be 100644 --- a/content/en/service_management/events/pipelines_and_processors/service_remapper.md +++ b/content/en/events/pipelines_and_processors/service_remapper.md @@ -1,5 +1,7 @@ --- title: Service Remapper +aliases: +- /service_management/events/pipelines_and_processors/service_remapper/ description: Assign one or more attributes to events as the official service --- diff --git a/content/en/service_management/events/pipelines_and_processors/status_remapper.md b/content/en/events/pipelines_and_processors/status_remapper.md similarity index 95% rename from content/en/service_management/events/pipelines_and_processors/status_remapper.md rename to content/en/events/pipelines_and_processors/status_remapper.md index ba65ec60525..9394ffe5353 100644 --- a/content/en/service_management/events/pipelines_and_processors/status_remapper.md +++ b/content/en/events/pipelines_and_processors/status_remapper.md @@ -1,5 +1,7 @@ --- title: Status Remapper +aliases: +- /service_management/events/pipelines_and_processors/status_remapper/ description: Assign attributes as the official status to events to add severity levels based on Syslog standards --- diff --git a/content/en/service_management/events/pipelines_and_processors/string_builder_processor.md b/content/en/events/pipelines_and_processors/string_builder_processor.md similarity index 92% rename from content/en/service_management/events/pipelines_and_processors/string_builder_processor.md rename to content/en/events/pipelines_and_processors/string_builder_processor.md index 95238fc59e7..a4e0f6bf98f 100644 --- a/content/en/service_management/events/pipelines_and_processors/string_builder_processor.md +++ b/content/en/events/pipelines_and_processors/string_builder_processor.md @@ -1,5 +1,7 @@ --- title: String Builder Processor +aliases: +- /service_management/events/pipelines_and_processors/string_builder_processor/ description: Add a new attribute to an event with the result of a template to aggregate different attributes or raw strings --- diff --git a/content/en/service_management/events/triage_inbox.md b/content/en/events/triage_inbox.md similarity index 92% rename from content/en/service_management/events/triage_inbox.md rename to content/en/events/triage_inbox.md index 062d53f147d..11fbfd5d655 100644 --- a/content/en/service_management/events/triage_inbox.md +++ b/content/en/events/triage_inbox.md @@ -1,10 +1,12 @@ --- title: Event Management Triage Inbox +aliases: +- /service_management/events/triage_inbox/ further_reading: -- link: "/service_management/events/ingest//" +- link: "/events/ingest/" tag: "doc" text: "Send events to Datadog" -- link: "/service_management/events/correlation/" +- link: "/events/correlation/" tag: "doc" text: "Learn more about event correlation" - link: "https://www.datadoghq.com/blog/datadog-event-management/" @@ -24,7 +26,7 @@ Case triage and investigation begins in the Triage Inbox, where you can sort, fi ## Getting Started -1. Navigate to [**Service Management** > **Event Management** > **Triage Inbox**][4]. +1. Navigate to [**Event Management** > **Triage Inbox**][4]. 2. Select a project from the left-hand panel to display out-of-the-box status views such as **Open**, **In Progress**, **Closed**, and **Archived**. 3. Use the display settings icon to choose between **split view** (for detailed case investigation) or **table view** (for bulk case review and column configuration). Customize your inbox ranking with the **Sort By** dropdown-options include **Priority**, **Created at**, or **Last Updated**. Click **Save** to re-use your customized inbox for future use. 5. Update the status, priority, and assignment directly on case cards during triage. @@ -59,8 +61,8 @@ On the right hand split-view side panel, you can perform the following: {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/incident_management/ -[2]: /service_management/on-call/ +[1]: /incident_response/incident_management/ +[2]: /incident_response/on-call/ [3]: /actions/workflows/ [4]: https://app.datadoghq.com/event/correlation -[5]: /service_management/case_management/automation_rules/ \ No newline at end of file +[5]: /incident_response/case_management/automation_rules/ \ No newline at end of file diff --git a/content/en/getting_started/_index.md b/content/en/getting_started/_index.md index a3bb12bcf3a..31503b41559 100644 --- a/content/en/getting_started/_index.md +++ b/content/en/getting_started/_index.md @@ -63,7 +63,7 @@ The table below lists a few examples of Datadog products:

Troubleshooting

diff --git a/content/en/getting_started/incident_management/_index.md b/content/en/getting_started/incident_management/_index.md index 1149672e774..9ad6b955947 100644 --- a/content/en/getting_started/incident_management/_index.md +++ b/content/en/getting_started/incident_management/_index.md @@ -5,7 +5,7 @@ further_reading: - link: 'https://learn.datadoghq.com/courses/intro-to-incident-management' tag: 'Learning Center' text: 'Introduction to Incident Management' - - link: '/service_management/incident_management/datadog_clipboard' + - link: '/incident_response/incident_management/datadog_clipboard' tag: 'Documentation' text: 'Datadog Clipboard' - link: 'https://www.youtube.com/watch?v=QIambwILy_M' @@ -20,7 +20,7 @@ further_reading: - link: 'https://www.datadoghq.com/blog/incident-response-with-datadog/' tag: 'Blog' text: 'Incident Management with Datadog' - - link: '/service_management/incident_management/incident_settings' + - link: '/incident_response/incident_management/incident_settings' tag: 'Documentation' text: 'Notification Rules' - link: '/integrations/slack/?tab=slackapplicationus#using-datadog-incidents' @@ -189,15 +189,15 @@ You can also declare and edit incidents and quickly communicate to your teams th {{< partial name="whats-next/whats-next.html" >}} [1]: /integrations/slack/ -[2]: /service_management/incident_management/datadog_clipboard +[2]: /incident_response/incident_management/datadog_clipboard [3]: /notebooks/#overview -[4]: /service_management/incident_management/#from-a-graph -[5]: /service_management/incident_management/#from-a-monitor +[4]: /incident_response/incident_management/#from-a-graph +[5]: /incident_response/incident_management/#from-a-monitor [6]: /api/latest/incidents/#create-an-incident [7]: https://app.datadoghq.com/notebook/list [8]: https://app.datadoghq.com/incidents/settings#Messages -[9]: /service_management/incident_management/#status-levels -[10]: /service_management/incident_management/incident_settings +[9]: /incident_response/incident_management/#status-levels +[10]: /incident_response/incident_management/incident_settings [11]: https://app.datadoghq.com/incidents/settings [12]: /mobile/ [13]: https://apps.apple.com/app/datadog/id1391380318 diff --git a/content/en/getting_started/monitors/_index.md b/content/en/getting_started/monitors/_index.md index c48f0a79f2d..e7521f2275c 100644 --- a/content/en/getting_started/monitors/_index.md +++ b/content/en/getting_started/monitors/_index.md @@ -159,6 +159,6 @@ You can view Monitor Saved Views from your mobile home screen or view and mute m [12]: https://apps.apple.com/app/datadog/id1391380318 [13]: https://play.google.com/store/apps/details?id=com.datadog.app [14]: /service_management/workflows/ -[15]: /service_management/case_management/ +[15]: /incident_response/case_management/ [16]: /account_management/teams/ [17]: https://app.datadoghq.com/monitors/manage diff --git a/content/en/getting_started/search/product_specific_reference.md b/content/en/getting_started/search/product_specific_reference.md index 2f02c05452b..4faaabd326e 100644 --- a/content/en/getting_started/search/product_specific_reference.md +++ b/content/en/getting_started/search/product_specific_reference.md @@ -131,7 +131,7 @@ service:database @db.statement:"SELECT *" @db.row_count:>1000 {{< nextlink href="/quality_gates/explorer/search_syntax" >}}Quality Gates Explorer Syntax: Query quality gate rules and evaluation results{{< /nextlink >}} {{< nextlink href="/real_user_monitoring/explorer/search_syntax" >}}RUM Explorer Search: Search user sessions, views, actions, and errors{{< /nextlink >}} {{< nextlink href="/security/sensitive_data_scanner/scanning_rules/custom_rules" >}}Sensitive Data Scanner Custom Rules: Regex patterns and matching syntax for scanning sensitive data{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/searching" >}}Service Management Events Search: Query and filter service management events{{< /nextlink >}} + {{< nextlink href="/events/explorer/searching" >}}Service Management Events Search: Query and filter service management events{{< /nextlink >}} {{< nextlink href="/logs/workspaces/sql_reference" >}}SQL Reference for Logs: SQL syntax for advanced log analysis in Workspaces{{< /nextlink >}} {{< nextlink href="/tests/explorer/search_syntax" >}}Test Optimization Explorer Search Syntax: Search and analyze test execution data{{< /nextlink >}} {{< nextlink href="/observability_pipelines/search_syntax/logs" >}}Observability Pipelines Search Syntax: Filter logs for your processors{{< /nextlink >}} diff --git a/content/en/getting_started/tagging/using_tags.md b/content/en/getting_started/tagging/using_tags.md index 3f777fdbdfc..16b19ce3f91 100644 --- a/content/en/getting_started/tagging/using_tags.md +++ b/content/en/getting_started/tagging/using_tags.md @@ -312,7 +312,7 @@ When creating a [metric-based SLO][1], use metric tags in the SLO's success rati * **from** text box to limit the metric scope to only those tags. * **sum by** text box to create a grouped metric-based SLO that display a status percentage and remaining error budget for both the overall SLO and for each tag value. -[1]: /service_management/service_level_objectives/metric/ +[1]: /service_level_objectives/metric/ {{% /tab %}} {{% tab "Monitor-based SLOs" %}} @@ -320,7 +320,7 @@ When creating a [monitor-based SLO][1] using a single [grouped monitor][2], use {{< img src="tagging/using_tags/monitor_based_slo_tags.png" alt="Monitor-based SLO Tags" style="width:80%;">}} -[1]: /service_management/service_level_objectives/monitor/ +[1]: /service_level_objectives/monitor/ [2]: /getting_started/tagging/using_tags/?tab=newmonitor#monitors {{% /tab %}} {{< /tabs >}} @@ -386,7 +386,7 @@ See this list for links to respective sections: {{< partial name="whats-next/whats-next.html" >}} [1]: /getting_started/tagging/assigning_tags/ -[2]: /service_management/events/explorer +[2]: /events/explorer [3]: /integrations/ [4]: /infrastructure/hostmap/ [5]: /infrastructure/ diff --git a/content/en/glossary/terms/slo.md b/content/en/glossary/terms/slo.md index f5c88203403..f8d4b9276be 100644 --- a/content/en/glossary/terms/slo.md +++ b/content/en/glossary/terms/slo.md @@ -4,4 +4,4 @@ core_product: - slos --- An SLO is a target percentage for application performance over a specific period of time. -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/glossary/terms/slo_list.md b/content/en/glossary/terms/slo_list.md index f347fe1b93c..d2807e1dc3d 100644 --- a/content/en/glossary/terms/slo_list.md +++ b/content/en/glossary/terms/slo_list.md @@ -6,4 +6,4 @@ related_terms: - service level objective (SLO) - dashboard --- -The SLO List widget displays a subset of SLOs over their primary time window. All other configured time windows are available in the SLO’s side panel on the SLO page. For more information, see the documentation. \ No newline at end of file +The SLO List widget displays a subset of SLOs over their primary time window. All other configured time windows are available in the SLO's side panel on the SLO page. For more information, see the documentation. \ No newline at end of file diff --git a/content/en/service_management/case_management/_index.md b/content/en/incident_response/case_management/_index.md similarity index 74% rename from content/en/service_management/case_management/_index.md rename to content/en/incident_response/case_management/_index.md index 572fa6f3dd5..fb7470f9d7f 100644 --- a/content/en/service_management/case_management/_index.md +++ b/content/en/incident_response/case_management/_index.md @@ -2,6 +2,7 @@ title: Case Management aliases: - /monitors/case_management/ +- /service_management/case_management/ further_reading: - link: https://www.datadoghq.com/blog/datadog-forms tag: Blog @@ -32,11 +33,11 @@ While investigating, populate the case with graphs, logs, and other telemetry da ## Getting started {{< whatsnext desc="Learn more about case management:">}} - {{< nextlink href="/service_management/case_management/create_case" >}}Create a case{{< /nextlink >}} - {{< nextlink href="/service_management/case_management/projects" >}}Projects{{< /nextlink >}} - {{< nextlink href="/service_management/case_management/create_notifications_and_third_party_tickets" >}}Create notifications and third party tickets{{< /nextlink >}} - {{< nextlink href="/service_management/case_management/view_and_manage" >}}View and manage cases{{< /nextlink >}} - {{< nextlink href="/service_management/case_management/settings" >}}Manage membership and status transitions within projects{{< /nextlink >}} + {{< nextlink href="/incident_response/case_management/create_case" >}}Create a case{{< /nextlink >}} + {{< nextlink href="/incident_response/case_management/projects" >}}Projects{{< /nextlink >}} + {{< nextlink href="/incident_response/case_management/create_notifications_and_third_party_tickets" >}}Create notifications and third party tickets{{< /nextlink >}} + {{< nextlink href="/incident_response/case_management/view_and_manage" >}}View and manage cases{{< /nextlink >}} + {{< nextlink href="/incident_response/case_management/settings" >}}Manage membership and status transitions within projects{{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/en/service_management/case_management/automation_rules.md b/content/en/incident_response/case_management/automation_rules.md similarity index 95% rename from content/en/service_management/case_management/automation_rules.md rename to content/en/incident_response/case_management/automation_rules.md index 9f5e303e17f..b196eafcba4 100644 --- a/content/en/service_management/case_management/automation_rules.md +++ b/content/en/incident_response/case_management/automation_rules.md @@ -1,7 +1,9 @@ --- title: Case automation rules +aliases: +- /service_management/case_management/automation_rules/ further_reading: -- link: "/service_management/case_management" +- link: "/incident_response/case_management" tag: "Documentation" text: "Learn more about Case management" --- diff --git a/content/en/service_management/case_management/create_case.md b/content/en/incident_response/case_management/create_case.md similarity index 95% rename from content/en/service_management/case_management/create_case.md rename to content/en/incident_response/case_management/create_case.md index 463a1dc67b8..27cf02d5828 100644 --- a/content/en/service_management/case_management/create_case.md +++ b/content/en/incident_response/case_management/create_case.md @@ -1,10 +1,12 @@ --- title: Create a Case +aliases: +- /service_management/case_management/create_case/ further_reading: -- link: "service_management/case_management/view_and_manage" +- link: "/incident_response/case_management/view_and_manage" tag: "Documentation" text: "View and Manage Cases" -- link: "service_management/case_management/customization" +- link: "/incident_response/case_management/customization" tag: "Documentation" text: "Case Customization" @@ -79,4 +81,4 @@ Create a case through the [API endpoint][5]. [4]: https://app.datadoghq.com/cases/settings [5]: /api/latest/case-management/#create-a-case [6]: /service_management/workflows/trigger/ -[7]: /service_management/case_management/customization +[7]: /incident_response/case_management/customization diff --git a/content/en/service_management/case_management/customization.md b/content/en/incident_response/case_management/customization.md similarity index 92% rename from content/en/service_management/case_management/customization.md rename to content/en/incident_response/case_management/customization.md index 6f3859a6257..adc16352d95 100644 --- a/content/en/service_management/case_management/customization.md +++ b/content/en/incident_response/case_management/customization.md @@ -1,13 +1,15 @@ --- title: Customization +aliases: +- /service_management/case_management/customization/ further_reading: -- link: "service_management/case_management/" +- link: "/incident_response/case_management/" tag: "Documentation" text: "Case Management Overview" -- link: "service_management/case_management/create_case" +- link: "/incident_response/case_management/create_case" tag: "Documentation" text: "Create a case" -- link: "service_management/case_management/settings" +- link: "/incident_response/case_management/settings" tag: "Documentation" text: "Settings" --- @@ -88,5 +90,5 @@ You can add attributes that reflect your team's specific needs, such as escalati {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/case_management/create_case#case-types +[1]: /incident_response/case_management/create_case#case-types [2]: https://app.datadoghq.com/cases/settings?type=shared diff --git a/content/en/service_management/case_management/notifications_integrations.md b/content/en/incident_response/case_management/notifications_integrations.md similarity index 98% rename from content/en/service_management/case_management/notifications_integrations.md rename to content/en/incident_response/case_management/notifications_integrations.md index 1912b1f6153..c6edf351ccb 100644 --- a/content/en/service_management/case_management/notifications_integrations.md +++ b/content/en/incident_response/case_management/notifications_integrations.md @@ -2,8 +2,9 @@ title: Notifications and Integrations aliases: - /service_management/case_management/create_notifications_and_third_party_tickets +- /service_management/case_management/notifications_integrations/ further_reading: -- link: "/service_management/case_management/troubleshooting" +- link: "/incident_response/case_management/troubleshooting" tag: "Documentation" text: "Troubleshooting third-party integrations" --- @@ -145,4 +146,4 @@ When enabled, any case that meets your specified query criteria (at any point in [1]: https://app.datadoghq.com/cases/settings [2]: /integrations/jira/#configure-a-jira-webhook [3]: /integrations/servicenow/#itom-and-itsm-setup -[4]: /service_management/on-call/ +[4]: /incident_response/on-call/ diff --git a/content/en/service_management/case_management/projects.md b/content/en/incident_response/case_management/projects.md similarity index 93% rename from content/en/service_management/case_management/projects.md rename to content/en/incident_response/case_management/projects.md index 74022eeb9f4..3f738cc9bbe 100644 --- a/content/en/service_management/case_management/projects.md +++ b/content/en/incident_response/case_management/projects.md @@ -1,8 +1,10 @@ --- title: Projects +aliases: +- /service_management/case_management/projects/ disable_toc: false further_reading: -- link: "service_management/case_management/create_case" +- link: "incident_response/case_management/create_case" tag: "Documentation" text: "Create a case" --- diff --git a/content/en/service_management/case_management/settings.md b/content/en/incident_response/case_management/settings.md similarity index 90% rename from content/en/service_management/case_management/settings.md rename to content/en/incident_response/case_management/settings.md index 73e688ec21d..43ee7b66397 100644 --- a/content/en/service_management/case_management/settings.md +++ b/content/en/incident_response/case_management/settings.md @@ -1,10 +1,12 @@ --- title: Settings +aliases: +- /service_management/case_management/settings/ further_reading: -- link: "/service_management/case_management/troubleshooting" +- link: "/incident_response/case_management/troubleshooting" tag: "Documentation" text: "Troubleshooting third-party integrations" -- link: "/service_management/case_management/customization" +- link: "/incident_response/case_management/customization" tag: "Documentation" text: "Case Customization" --- @@ -51,5 +53,5 @@ Add custom case types and attributes to projects so that you can tailor your cas [1]: /account_management/rbac/granular_access [2]: https://app.datadoghq.com/cases/settings -[3]: /service_management/case_management/create_notifications_and_third_party_tickets -[4]: /service_management/case_management/customization +[3]: /incident_response/case_management/create_notifications_and_third_party_tickets +[4]: /incident_response/case_management/customization diff --git a/content/en/service_management/case_management/troubleshooting.md b/content/en/incident_response/case_management/troubleshooting.md similarity index 96% rename from content/en/service_management/case_management/troubleshooting.md rename to content/en/incident_response/case_management/troubleshooting.md index b5634e03e01..542f55750e3 100644 --- a/content/en/service_management/case_management/troubleshooting.md +++ b/content/en/incident_response/case_management/troubleshooting.md @@ -1,5 +1,7 @@ --- title: Troubleshooting +aliases: +- /service_management/case_management/troubleshooting/ --- ## Overview diff --git a/content/en/service_management/case_management/view_and_manage/_index.md b/content/en/incident_response/case_management/view_and_manage/_index.md similarity index 95% rename from content/en/service_management/case_management/view_and_manage/_index.md rename to content/en/incident_response/case_management/view_and_manage/_index.md index a0793233998..9fe04600aba 100644 --- a/content/en/service_management/case_management/view_and_manage/_index.md +++ b/content/en/incident_response/case_management/view_and_manage/_index.md @@ -1,7 +1,9 @@ --- title: View and Manage Cases +aliases: +- /service_management/case_management/view_and_manage/ further_reading: -- link: "service_management/case_management/settings" +- link: "incident_response/case_management/settings" tag: "Documentation" text: "Case settings" --- @@ -108,9 +110,9 @@ You can export cases directly from a case details page: {{< partial name="whats-next/whats-next.html" >}} [1]: https://app.datadoghq.com/cases -[2]: /service_management/case_management/create_notifications_and_third_party_tickets +[2]: /incident_response/case_management/create_notifications_and_third_party_tickets [3]: /notebooks/ -[4]: /service_management/incident_management/#describing-the-incident -[5]: /service_management/case_management/settings/#jira +[4]: /incident_response/incident_management/#describing-the-incident +[5]: /incident_response/case_management/settings/#jira [6]: /coscreen/ [7]: https://docs.datadoghq.com/dashboards/ diff --git a/content/en/service_management/incident_management/_index.md b/content/en/incident_response/incident_management/_index.md similarity index 95% rename from content/en/service_management/incident_management/_index.md rename to content/en/incident_response/incident_management/_index.md index 582a7d9d385..d1ebb12c9b1 100644 --- a/content/en/service_management/incident_management/_index.md +++ b/content/en/incident_response/incident_management/_index.md @@ -3,6 +3,7 @@ title: Incident Management description: Create and manage incidents aliases: - /monitors/incident_management/ +- /service_management/incident_management/ further_reading: - link: "https://app.datadoghq.com/release-notes?category=Incident%20Management" tag: "Release Notes" @@ -50,7 +51,7 @@ Incident Management requires no installation. Get started by taking a Learning C {{< whatsnext desc="Learn more about Incident Management:">}} {{< nextlink href="https://learn.datadoghq.com/courses/intro-to-incident-management" >}}Learn about Datadog Incident Management by working through a hands-on examples{{< /nextlink >}} {{< nextlink href="https://docs.datadoghq.com/getting_started/incident_management/" >}}Guided walkthrough of an Incident workflow{{< /nextlink >}} - {{< nextlink href="/service_management/incident_management/declare" >}}Declare an incident{{< /nextlink >}} + {{< nextlink href="/incident_response/incident_management/declare" >}}Declare an incident{{< /nextlink >}} {{< /whatsnext >}} ## View your incidents @@ -119,11 +120,11 @@ Incident Management is a seat-based SKU. To learn more about how Incident Manage [3]: /mobile [4]: https://apps.apple.com/app/datadog/id1391380318 [5]: https://play.google.com/store/apps/details?id=com.datadog.app -[6]: /service_management/incident_management/declare +[6]: /incident_response/incident_management/declare [7]: /account_management/teams/ [8]: /getting_started/tagging/assigning_tags?tab=noncontainerizedenvironments#overview [9]: /tracing/#2-instrument-your-application -[10]: /service_management/incident_management/analytics/ +[10]: /incident_response/incident_management/analytics/ [11]: /integrations/slack/?tab=slackapplicationbeta#using-the-slack-app [12]: /integrations/pagerduty/ [13]: /integrations/opsgenie/ @@ -133,16 +134,16 @@ Incident Management is a seat-based SKU. To learn more about how Incident Manage [17]: /integrations/webhooks/#sending-sms-through-twilio [18]: /integrations/statuspage/ [19]: /integrations/servicenow/ -[20]: /service_management/incident_management/describe +[20]: /incident_response/incident_management/describe [21]: /coterm [22]: /integrations/confluence/ [23]: /integrations/microsoft-teams/?tab=datadogapprecommended#datadog-incident-management-in-microsoft-teams [24]: /integrations/zoom-incident-management/ [25]: /integrations/statuspage/ -[26]: /service_management/status_pages/ -[27]: /service_management/on-call/ +[26]: /incident_response/status_pages/ +[27]: /incident_response/on-call/ [28]: /notebooks/ [29]: /actions/workflows/ -[30]: /service_management/incident_management/declare#from-a-monitor +[30]: /incident_response/incident_management/declare#from-a-monitor [31]: https://www.datadoghq.com/pricing/?product=incident-response#products [32]: /account_management/billing/incident_response/ diff --git a/content/en/service_management/incident_management/analytics.md b/content/en/incident_response/incident_management/analytics.md similarity index 95% rename from content/en/service_management/incident_management/analytics.md rename to content/en/incident_response/incident_management/analytics.md index 45d2307de9d..afe09a588d1 100644 --- a/content/en/service_management/incident_management/analytics.md +++ b/content/en/incident_response/incident_management/analytics.md @@ -3,8 +3,9 @@ title: Incident Management Analytics description: Track and analyze aggregated incident management statistics in Dashboards and Notebooks aliases: - /monitors/incident_management/analytics +- /service_management/incident_management/analytics/ further_reading: -- link: "/service_management/incident_management/incident_settings" +- link: "/incident_response/incident_management/incident_settings" tag: "Documentation" text: "Incident Settings" - link: "https://app.datadoghq.com/dash/integration/30523/incident-management-overview" @@ -63,7 +64,7 @@ To address this, organizations can enable **timestamp overrides**, which allow i Overrides only influence search and analytics. They do not change the history automatically recorded to the incident timeline. They do not apply to the analytic measures `Status Active Duration` or `Status Stable Duration`, which are driven by the cumulative length of status segments on incident timelines. -To enable timestamp overrides, go to [**Service Management** > **Incidents** > **Settings** > **Information**][11]. +To enable timestamp overrides, go to [**Incidents** > **Settings** > **Information**][11]. To create, update, or delete timestamp overrides, users must have the **Incidents Write** permission. @@ -114,7 +115,7 @@ Use the out-of-the-box Notebook template to create the Incident Report or build [4]: https://app.datadoghq.com/notebook/template/11/incident-management-overview [5]: /dashboards/querying/#select-your-visualization [6]: /dashboards/querying/#create-a-title -[7]: /service_management/incident_management/incident_settings#property-fields +[7]: /incident_response/incident_management/incident_settings#property-fields [8]: /dashboards/widgets/timeseries/ [9]: https://app.datadoghq.com/notebook/template/11/incident-report [10]: /notebooks/#share-notebooks diff --git a/content/en/service_management/incident_management/datadog_clipboard.md b/content/en/incident_response/incident_management/datadog_clipboard.md similarity index 98% rename from content/en/service_management/incident_management/datadog_clipboard.md rename to content/en/incident_response/incident_management/datadog_clipboard.md index 831ba3285bf..3c7ae32d858 100644 --- a/content/en/service_management/incident_management/datadog_clipboard.md +++ b/content/en/incident_response/incident_management/datadog_clipboard.md @@ -3,6 +3,7 @@ title: Datadog Clipboard description: Create and manage incidents aliases: - /monitors/incident_management/datadog_clipboard +- /service_management/incident_management/datadog_clipboard/ further_reading: - link: "https://www.datadoghq.com/blog/datadog-clipboard/" tag: "Blog" diff --git a/content/en/service_management/incident_management/declare.md b/content/en/incident_response/incident_management/declare.md similarity index 92% rename from content/en/service_management/incident_management/declare.md rename to content/en/incident_response/incident_management/declare.md index dbdd93f02f6..f9027fc9334 100644 --- a/content/en/service_management/incident_management/declare.md +++ b/content/en/incident_response/incident_management/declare.md @@ -1,5 +1,7 @@ --- title: Declare an Incident +aliases: +- /service_management/incident_management/declare/ --- ## Overview @@ -103,19 +105,19 @@ You can declare an incident from individual Handoff Notification cards. ## What's next {{< whatsnext desc="Add helpful information to your incident and give context to everyone that is involved in the investigation.">}} - {{< nextlink href="/service_management/incident_management/describe" >}}Describe the Incident: Add context and details{{< /nextlink >}} + {{< nextlink href="/incident_response/incident_management/describe" >}}Describe the Incident: Add context and details{{< /nextlink >}} {{< /whatsnext >}} [1]: https://app.datadoghq.com/incidents -[2]: /service_management/incident_management/incident_settings#information +[2]: /incident_response/incident_management/incident_settings#information [3]: /security/workload_protection/security_signals/#declare-an-incident [4]:/security/workload_protection/security_signals/#declare-an-incident -[5]: /service_management/case_management/view_and_manage -[6]: /service_management/incident_management/datadog_clipboard +[5]: /incident_response/case_management/view_and_manage +[6]: /incident_response/incident_management/datadog_clipboard [7]: /integrations/slack/?tab=slackapplicationbeta#using-the-slack-app [8]: https://app.datadoghq.com/synthetics/tests [9]: https://app.datadoghq.com/incidents/settings?section=global-settings -[10]: /service_management/incident_management/incident_settings/property_fields -[11]: /service_management/incident_management/incident_settings/notification_rules -[12]: /service_management/on-call/ +[10]: /incident_response/incident_management/incident_settings/property_fields +[11]: /incident_response/incident_management/incident_settings/notification_rules +[12]: /incident_response/on-call/ [13]: https://app.datadoghq.com/on-call/pages \ No newline at end of file diff --git a/content/en/service_management/incident_management/describe.md b/content/en/incident_response/incident_management/describe.md similarity index 88% rename from content/en/service_management/incident_management/describe.md rename to content/en/incident_response/incident_management/describe.md index 66b720ae41f..a06c8bf35eb 100644 --- a/content/en/service_management/incident_management/describe.md +++ b/content/en/incident_response/incident_management/describe.md @@ -1,10 +1,12 @@ --- title: Describe an Incident +aliases: +- /service_management/incident_management/describe/ further_reading: -- link: "/service_management/incident_management/incident_settings" +- link: "/incident_response/incident_management/incident_settings" tag: "Documentation" text: "Customize incidents in Incident Settings" -- link: "/service_management/incident_management/notification" +- link: "/incident_response/incident_management/notification" tag: "Documentation" text: "Configure Incident Notifications" --- @@ -37,5 +39,5 @@ The default statuses are **Active**, **Stable**, and **Resolved**. You can add t {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/incident_management/declare +[1]: /incident_response/incident_management/declare [2]: https://app.datadoghq.com/incidents/settings#Property-Fields \ No newline at end of file diff --git a/content/en/service_management/incident_management/follow-ups.md b/content/en/incident_response/incident_management/follow-ups.md similarity index 99% rename from content/en/service_management/incident_management/follow-ups.md rename to content/en/incident_response/incident_management/follow-ups.md index 6286dccca6d..84dd767eed9 100644 --- a/content/en/service_management/incident_management/follow-ups.md +++ b/content/en/incident_response/incident_management/follow-ups.md @@ -1,6 +1,8 @@ --- title: Incident Follow-ups description: Manage follow-up tasks defined during your incident response process. +aliases: +- /service_management/incident_management/follow-ups/ further_reading: - link: "/service_management/incident_management/incident_settings" tag: "Documentation" diff --git a/content/en/service_management/incident_management/guides/_index.md b/content/en/incident_response/incident_management/guides/_index.md similarity index 79% rename from content/en/service_management/incident_management/guides/_index.md rename to content/en/incident_response/incident_management/guides/_index.md index 9143e269a47..497a1e79c4a 100644 --- a/content/en/service_management/incident_management/guides/_index.md +++ b/content/en/incident_response/incident_management/guides/_index.md @@ -1,9 +1,11 @@ --- title: Incident Management Guides +aliases: +- /service_management/incident_management/guides/ private: true disable_toc: true further_reading: -- link: "/service_management/incident_management" +- link: "/incident_response/incident_management" tag: "Documentation" text: "Learn more about Incident Management" - link: "https://app.datadoghq.com/release-notes?category=Service%20Management" diff --git a/content/en/service_management/incident_management/incident_ai.md b/content/en/incident_response/incident_management/incident_ai.md similarity index 98% rename from content/en/service_management/incident_management/incident_ai.md rename to content/en/incident_response/incident_management/incident_ai.md index 57d996c6c18..ac61d6fd39f 100644 --- a/content/en/service_management/incident_management/incident_ai.md +++ b/content/en/incident_response/incident_management/incident_ai.md @@ -4,6 +4,7 @@ description: "Learn how to use Incident AI to automate incident coordination, ge aliases: - /bits_ai/managing_incidents/ - /bits_ai/bits_ai_sre/coordinate_incidents +- /service_management/incident_management/incident_ai/ further_reading: - link: "/bits_ai/bits_ai_sre/" tag: "Documentation" @@ -146,4 +147,4 @@ To generate an AI-assisted postmortem draft: [2]: https://app.datadoghq.com/incidents/settings?section=notification-rules [3]: https://app.datadoghq.com/incidents/settings?section=postmortem-templates [4]: https://app.datadoghq.com/incidents/settings?section=integrations -[5]: /service_management/incident_management/follow-ups +[5]: /incident_response/incident_management/follow-ups diff --git a/content/en/service_management/incident_management/incident_settings/_index.md b/content/en/incident_response/incident_management/incident_settings/_index.md similarity index 62% rename from content/en/service_management/incident_management/incident_settings/_index.md rename to content/en/incident_response/incident_management/incident_settings/_index.md index 7e1832176cb..1206f1e9278 100644 --- a/content/en/service_management/incident_management/incident_settings/_index.md +++ b/content/en/incident_response/incident_management/incident_settings/_index.md @@ -4,6 +4,7 @@ description: Configure and customize your Incident Management experience aliases: - /monitors/incident_management/notification_rules - /monitors/incident_management/incident_settings +- /service_management/incident_management/incident_settings/ --- ## Overview @@ -30,13 +31,13 @@ To create an incident type: ## Customize incident response {{< whatsnext desc="Set additional customizations on the following:">}} - {{< nextlink href="/service_management/incident_management/incident_settings/information" >}}Information{{< /nextlink >}} - {{< nextlink href="/service_management/incident_management/incident_settings/integrations" >}}Integrations{{< /nextlink >}} - {{< nextlink href="/service_management/incident_management/follow-ups" >}}Follow-ups{{< /nextlink >}} - {{< nextlink href="/service_management/incident_management/incident_settings/notification_rules" >}}Notification Rules{{< /nextlink >}} - {{< nextlink href="/service_management/incident_management/incident_settings/property_fields" >}}Property Fields{{< /nextlink >}} - {{< nextlink href="/service_management/incident_management/incident_settings/responder_types" >}}Responder Types{{< /nextlink >}} - {{< nextlink href="/service_management/incident_management/incident_settings/templates" >}}Templates{{< /nextlink >}} + {{< nextlink href="/incident_response/incident_management/incident_settings/information" >}}Information{{< /nextlink >}} + {{< nextlink href="/incident_response/incident_management/incident_settings/integrations" >}}Integrations{{< /nextlink >}} + {{< nextlink href="/incident_response/incident_management/follow-ups" >}}Follow-ups{{< /nextlink >}} + {{< nextlink href="/incident_response/incident_management/incident_settings/notification_rules" >}}Notification Rules{{< /nextlink >}} + {{< nextlink href="/incident_response/incident_management/incident_settings/property_fields" >}}Property Fields{{< /nextlink >}} + {{< nextlink href="/incident_response/incident_management/incident_settings/responder_types" >}}Responder Types{{< /nextlink >}} + {{< nextlink href="/incident_response/incident_management/incident_settings/templates" >}}Templates{{< /nextlink >}} {{< /whatsnext >}} [1]: https://app.datadoghq.com/incidents/settings diff --git a/content/en/service_management/incident_management/incident_settings/information.md b/content/en/incident_response/incident_management/incident_settings/information.md similarity index 94% rename from content/en/service_management/incident_management/incident_settings/information.md rename to content/en/incident_response/incident_management/incident_settings/information.md index 07898213442..983a2e05bd4 100644 --- a/content/en/service_management/incident_management/incident_settings/information.md +++ b/content/en/incident_response/incident_management/incident_settings/information.md @@ -1,5 +1,7 @@ --- title: Information +aliases: +- /service_management/incident_management/incident_settings/information/ --- ## Overview @@ -80,7 +82,7 @@ When test incidents are enabled in an incident type, any user with the **Inciden Test incidents are visually distinguished by a purple banner. By default, test incidents do not by appear in incident search, execute automations, execute notification rules, or affect analytics. The declarer can opt into these functions during declaration. [1]: https://app.datadoghq.com/incidents/settings#Information -[2]: /service_management/incident_management/incident_settings/notification_rules -[3]: /service_management/incident_management/analytics -[4]: /service_management/incident_management/#from-the-incidents-page +[2]: /incident_response/incident_management/incident_settings/notification_rules +[3]: /incident_response/incident_management/analytics +[4]: /incident_response/incident_management/#from-the-incidents-page [5]: https://app.datadoghq.com/incidents diff --git a/content/en/service_management/incident_management/incident_settings/integrations.md b/content/en/incident_response/incident_management/incident_settings/integrations.md similarity index 87% rename from content/en/service_management/incident_management/incident_settings/integrations.md rename to content/en/incident_response/incident_management/incident_settings/integrations.md index d1fcabde9c4..da4dd63361c 100644 --- a/content/en/service_management/incident_management/incident_settings/integrations.md +++ b/content/en/incident_response/incident_management/incident_settings/integrations.md @@ -1,7 +1,9 @@ --- title: Integrations +aliases: +- /service_management/incident_management/incident_settings/integrations/ further_reading: -- link: "/service_management/incident_management/integrations" +- link: "/incident_response/incident_management/integrations" tag: "Documentation" text: "Incident Integrations" --- @@ -41,10 +43,10 @@ In addition to integrating with Slack and Microsoft Teams, Incident Management a [1]: https://app.datadoghq.com/integrations [2]: https://app.datadoghq.com/incidents/settings#Integrations [3]: /integrations/slack/?tab=slackapplicationbeta#using-the-slack-app -[4]: /service_management/incident_management/integrations/slack/ +[4]: /incident_response/incident_management/integrations/slack/ [5]: /integrations/microsoft-teams/?tab=datadogapprecommended [6]: /integrations/microsoft-teams/?tab=datadogapprecommended#datadog-incident-management-in-microsoft-teams -[7]: /service_management/incident_management/incident_settings/notification_rules +[7]: /incident_response/incident_management/incident_settings/notification_rules [8]: /integrations/pagerduty/ [9]: /integrations/opsgenie/ [10]: /coscreen @@ -54,4 +56,4 @@ In addition to integrating with Slack and Microsoft Teams, Incident Management a [14]: /integrations/statuspage/ [15]: /integrations/servicenow/ [16]: /integrations/zoom_incident_management/ -[17]: /service_management/incident_management/integrations/microsoft_teams +[17]: /incident_response/incident_management/integrations/microsoft_teams diff --git a/content/en/service_management/incident_management/incident_settings/notification_rules.md b/content/en/incident_response/incident_management/incident_settings/notification_rules.md similarity index 96% rename from content/en/service_management/incident_management/incident_settings/notification_rules.md rename to content/en/incident_response/incident_management/incident_settings/notification_rules.md index c506e8f3afb..c45644042e6 100644 --- a/content/en/service_management/incident_management/incident_settings/notification_rules.md +++ b/content/en/incident_response/incident_management/incident_settings/notification_rules.md @@ -1,7 +1,9 @@ --- title: Notification Rules +aliases: +- /service_management/incident_management/incident_settings/notification_rules/ further_reading: -- link: "/service_management/incident_management/incident_settings/templates" +- link: "/incident_response/incident_management/incident_settings/templates" tag: "Documentation" text: "Customize message templates" --- @@ -62,7 +64,7 @@ When defining a notification rule's recipients, you can use `@` handles for any [1]: https://app.datadoghq.com/incidents/settings#Rules [2]: /monitors/notifications/?tab=is_alert#configure-notifications-and-automations [3]: /mobile/ -[4]: /service_management/on-call/ +[4]: /incident_response/on-call/ [5]: /actions/workflows/ [6]: /integrations/webhooks/ -[7]: /service_management/on-call/ \ No newline at end of file +[7]: /incident_response/on-call/ \ No newline at end of file diff --git a/content/en/service_management/incident_management/incident_settings/property_fields.md b/content/en/incident_response/incident_management/incident_settings/property_fields.md similarity index 89% rename from content/en/service_management/incident_management/incident_settings/property_fields.md rename to content/en/incident_response/incident_management/incident_settings/property_fields.md index ffa48f24b30..e2533ee7d88 100644 --- a/content/en/service_management/incident_management/incident_settings/property_fields.md +++ b/content/en/incident_response/incident_management/incident_settings/property_fields.md @@ -1,5 +1,7 @@ --- title: Property Fields +aliases: +- /service_management/incident_management/incident_settings/property_fields/ --- ## Overview @@ -79,16 +81,16 @@ Single-Select, Multi-Select, Text Array, Number, and Datetime fields are searcha In Incident Management Analytics, number fields appear as measures that can be graphed and visualized in [Dashboards][7] and [Notebooks][8]. -[1]: /service_management/incident_management/investigate#overview-tab +[1]: /incident_response/incident_management/investigate#overview-tab [2]: https://app.datadoghq.com/incidents -[3]: /service_management/incident_management/analytics +[3]: /incident_response/incident_management/analytics [4]: /tracing/ [5]: /account_management/teams/ [6]: /getting_started/tagging/using_tags/?tab=assignment#metrics [7]: /dashboards/ [8]: /notebooks/ -[9]: /service_management/incident_management/incident_settings/notification_rules -[10]: /service_management/incident_management/investigate/timeline -[11]: /service_management/incident_management/declare -[12]: /service_management/incident_management/incident_settings/property_fields#custom-fields-in-search-and-analytics +[9]: /incident_response/incident_management/incident_settings/notification_rules +[10]: /incident_response/incident_management/investigate/timeline +[11]: /incident_response/incident_management/declare +[12]: /incident_response/incident_management/incident_settings/property_fields#custom-fields-in-search-and-analytics [13]: /actions/workflows/ diff --git a/content/en/service_management/incident_management/incident_settings/responder_types.md b/content/en/incident_response/incident_management/incident_settings/responder_types.md similarity index 91% rename from content/en/service_management/incident_management/incident_settings/responder_types.md rename to content/en/incident_response/incident_management/incident_settings/responder_types.md index f5e9ebb2500..7ed147d0a3c 100644 --- a/content/en/service_management/incident_management/incident_settings/responder_types.md +++ b/content/en/incident_response/incident_management/incident_settings/responder_types.md @@ -1,7 +1,9 @@ --- title: Responder Types +aliases: +- /service_management/incident_management/incident_settings/responder_types/ further_reading: -- link: "/service_management/incident_management/describe/#response-team" +- link: "/incident_response/incident_management/describe/#response-team" tag: "Documentation" text: "Describe an incident" --- @@ -34,6 +36,6 @@ Responder types allow your responders to understand what their responsibilities {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/incident_management/response_team +[1]: /incident_response/incident_management/response_team [2]: /account_management/rbac/?tab=datadogapplication#pagetitle [3]: https://app.datadoghq.com/incidents/settings#Responder-Types diff --git a/content/en/service_management/incident_management/incident_settings/templates.md b/content/en/incident_response/incident_management/incident_settings/templates.md similarity index 92% rename from content/en/service_management/incident_management/incident_settings/templates.md rename to content/en/incident_response/incident_management/incident_settings/templates.md index 79a90f868b6..95e87749603 100644 --- a/content/en/service_management/incident_management/incident_settings/templates.md +++ b/content/en/incident_response/incident_management/incident_settings/templates.md @@ -1,7 +1,9 @@ --- title: Templates +aliases: +- /service_management/incident_management/incident_settings/templates/ further_reading: -- link: "/service_management/incident_management/notification" +- link: "/incident_response/incident_management/notification" tag: "Documentation" text: "Learn more about Incident Management Notifications" --- @@ -44,6 +46,6 @@ To create a postmortem template: {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/incident_management/notifications +[1]: /incident_response/incident_management/notifications [2]: /notebooks/ [3]: /integrations/confluence/ \ No newline at end of file diff --git a/content/en/service_management/incident_management/integrations/_index.md b/content/en/incident_response/incident_management/integrations/_index.md similarity index 64% rename from content/en/service_management/incident_management/integrations/_index.md rename to content/en/incident_response/incident_management/integrations/_index.md index 1e98cbed282..43784fc760f 100644 --- a/content/en/service_management/incident_management/integrations/_index.md +++ b/content/en/incident_response/incident_management/integrations/_index.md @@ -1,8 +1,10 @@ --- title: Incident Integrations description: "Learn how to connect Datadog Incident Management with third-party tools to automate workflows, sync communications, and streamline incident response." +aliases: +- /service_management/incident_management/integrations/ further_reading: -- link: "/service_management/incident_management/incident_settings/integrations" +- link: "/incident_response/incident_management/incident_settings/integrations" tag: "Documentation" text: "Incident Settings: Integrations" --- @@ -24,16 +26,16 @@ Configure and manage incident-related integrations from the **Incident Settings* ## Setup {{< whatsnext desc="Set up and use the following integrations within the context of Datadog Incident Management:">}} - {{< nextlink href="/service_management/incident_management/integrations/slack" >}}Slack{{< /nextlink >}} - {{< nextlink href="/service_management/incident_management/integrations/microsoft_teams" >}}Microsoft Teams{{< /nextlink >}} - {{< nextlink href="/service_management/incident_management/integrations/jira" >}}Jira{{< /nextlink >}} - {{< nextlink href="/service_management/incident_management/integrations/servicenow" >}}ServiceNow{{< /nextlink >}} - {{< nextlink href="/service_management/incident_management/integrations/status_pages" >}}Status Pages{{< /nextlink >}} - {{< nextlink href="/service_management/incident_management/integrations/statuspage" >}}Atlassian Statuspage{{< /nextlink >}} + {{< nextlink href="/incident_response/incident_management/integrations/slack" >}}Slack{{< /nextlink >}} + {{< nextlink href="/incident_response/incident_management/integrations/microsoft_teams" >}}Microsoft Teams{{< /nextlink >}} + {{< nextlink href="/incident_response/incident_management/integrations/jira" >}}Jira{{< /nextlink >}} + {{< nextlink href="/incident_response/incident_management/integrations/servicenow" >}}ServiceNow{{< /nextlink >}} + {{< nextlink href="/incident_response/incident_management/integrations/status_pages" >}}Status Pages{{< /nextlink >}} + {{< nextlink href="/incident_response/incident_management/integrations/statuspage" >}}Atlassian Statuspage{{< /nextlink >}} {{< /whatsnext >}} ## Further reading {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/incident_management/incident_settings/integrations +[1]: /incident_response/incident_management/incident_settings/integrations diff --git a/content/en/service_management/incident_management/integrations/jira.md b/content/en/incident_response/incident_management/integrations/jira.md similarity index 95% rename from content/en/service_management/incident_management/integrations/jira.md rename to content/en/incident_response/incident_management/integrations/jira.md index f80c80e0074..61726f2ff1a 100644 --- a/content/en/service_management/incident_management/integrations/jira.md +++ b/content/en/incident_response/incident_management/integrations/jira.md @@ -2,6 +2,7 @@ title: Integrate Jira with Datadog Incident Management aliases: - /service_management/incident_management/guides/jira +- /service_management/incident_management/integrations/jira/ further_reading: - link: "integrations/jira/" tag: "Documentation" @@ -9,7 +10,7 @@ further_reading: - link: "https://app.datadoghq.com/integrations/jira" tag: "App" text: "In-app Jira integration tile" -- link: "/service_management/incident_management/follow-ups" +- link: "/incident_response/incident_management/follow-ups" tag: "Documentation" text: "Export follow-ups to Jira" diff --git a/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md b/content/en/incident_response/incident_management/integrations/microsoft_teams/_index.md similarity index 96% rename from content/en/service_management/incident_management/integrations/microsoft_teams/_index.md rename to content/en/incident_response/incident_management/integrations/microsoft_teams/_index.md index 6ec1a820cfc..93a644cefa5 100644 --- a/content/en/service_management/incident_management/integrations/microsoft_teams/_index.md +++ b/content/en/incident_response/incident_management/integrations/microsoft_teams/_index.md @@ -1,8 +1,10 @@ --- title: Integrate Microsoft Teams with Datadog Incident Management description: Integrate Microsoft Teams with Datadog Incident Management to automate incident channel creation, synchronize messages, and collaborate with your team directly within Microsoft Teams. +aliases: +- /service_management/incident_management/integrations/microsoft_teams/ further_reading: -- link: "/service_management/incident_management/incident_settings/integrations" +- link: "/incident_response/incident_management/incident_settings/integrations" tag: "Documentation" text: "Incident Integrations Settings" - link: "/integrations/microsoft-teams" @@ -145,4 +147,4 @@ You can view the full list of available commands at any time by typing `@Datadog [1]: /integrations/microsoft-teams/?tab=datadogapprecommended [2]: https://app.datadoghq.com/incidents/settings#Integrations [3]: /integrations/microsoft-teams/?tab=datadogapprecommended#datadog-incident-management-in-microsoft-teams -[4]: /service_management/incident_management/incident_settings/notification_rules \ No newline at end of file +[4]: /incident_response/incident_management/incident_settings/notification_rules \ No newline at end of file diff --git a/content/en/service_management/incident_management/integrations/servicenow.md b/content/en/incident_response/incident_management/integrations/servicenow.md similarity index 99% rename from content/en/service_management/incident_management/integrations/servicenow.md rename to content/en/incident_response/incident_management/integrations/servicenow.md index 44ffd459815..17191b52603 100644 --- a/content/en/service_management/incident_management/integrations/servicenow.md +++ b/content/en/incident_response/incident_management/integrations/servicenow.md @@ -1,5 +1,7 @@ --- title: Integrate ServiceNow with Datadog Incident Management +aliases: +- /service_management/incident_management/integrations/servicenow/ further_reading: - link: "integrations/servicenow/" tag: "Documentation" diff --git a/content/en/service_management/incident_management/integrations/slack/_index.md b/content/en/incident_response/incident_management/integrations/slack/_index.md similarity index 97% rename from content/en/service_management/incident_management/integrations/slack/_index.md rename to content/en/incident_response/incident_management/integrations/slack/_index.md index 36c655ecbf1..0c75814f423 100644 --- a/content/en/service_management/incident_management/integrations/slack/_index.md +++ b/content/en/incident_response/incident_management/integrations/slack/_index.md @@ -1,6 +1,8 @@ --- title: Integrate Slack with Datadog Incident Management description: Manage Datadog incidents directly from Slack. +aliases: +- /service_management/incident_management/integrations/slack/ further_reading: - link: "integrations/slack/" tag: "Documentation" @@ -35,7 +37,7 @@ The Slack integration documentation is organized around the typical lifecycle of Install the integration through the [Slack Integration tile][1] with the proper [OAuth scopes][6]. For more information, see the [Slack integration][2] documentation. -After the integration is installed, navigate to [**Service Management** > **Incidents** > **Settings** > **Integrations**][3] to enable Slack capabilities for Incident Management. +After the integration is installed, navigate to [**Incidents** > **Settings** > **Integrations**][3] to enable Slack capabilities for Incident Management. ## Declaring incidents from Slack @@ -199,5 +201,5 @@ You can view the full list of available Slack commands at any time by typing `/d [2]: /integrations/slack/?tab=datadogforslack [3]: https://app.datadoghq.com/incidents/settings#Integrations [4]: /integrations/jira/ -[5]: /service_management/incident_management/incident_settings/notification_rules/ +[5]: /incident_response/incident_management/incident_settings/notification_rules/ [6]: /integrations/slack/?tab=datadogforslack#permissions diff --git a/content/en/service_management/incident_management/integrations/status_pages.md b/content/en/incident_response/incident_management/integrations/status_pages.md similarity index 96% rename from content/en/service_management/incident_management/integrations/status_pages.md rename to content/en/incident_response/incident_management/integrations/status_pages.md index 3fe22c077cf..ca15865e421 100644 --- a/content/en/service_management/incident_management/integrations/status_pages.md +++ b/content/en/incident_response/incident_management/integrations/status_pages.md @@ -1,11 +1,13 @@ --- title: Integrate Datadog Status Pages with Datadog Incident Management description: Learn how to integrate Datadog Status Pages with Incident Management to communicate real-time service status during incidents. +aliases: +- /service_management/incident_management/integrations/status_pages/ further_reading: - link: https://www.datadoghq.com/blog/status-pages tag: Blog text: Keep stakeholders informed with Datadog Status Pages -- link: "/service_management/status_pages/" +- link: "/incident_response/status_pages/" tag: "Documentation" text: "Learn more about Datadog Status Pages" --- diff --git a/content/en/service_management/incident_management/integrations/statuspage.md b/content/en/incident_response/incident_management/integrations/statuspage.md similarity index 98% rename from content/en/service_management/incident_management/integrations/statuspage.md rename to content/en/incident_response/incident_management/integrations/statuspage.md index 283cbbd007c..7ddd9e376a9 100644 --- a/content/en/service_management/incident_management/integrations/statuspage.md +++ b/content/en/incident_response/incident_management/integrations/statuspage.md @@ -2,6 +2,7 @@ title: Integrate Atlassian Statuspage with Datadog Incident Management aliases: - /service_management/incident_management/guides/statuspage +- /service_management/incident_management/integrations/statuspage/ further_reading: - link: "integrations/statuspage/" tag: "Documentation" diff --git a/content/en/service_management/incident_management/investigate/_index.md b/content/en/incident_response/incident_management/investigate/_index.md similarity index 84% rename from content/en/service_management/incident_management/investigate/_index.md rename to content/en/incident_response/incident_management/investigate/_index.md index 25fc9b900b0..d6be6a55e6d 100644 --- a/content/en/service_management/incident_management/investigate/_index.md +++ b/content/en/incident_response/incident_management/investigate/_index.md @@ -4,11 +4,12 @@ description: Manage the context and work for an incident aliases: - /monitors/incident_management/incident_details - /service_management/incident_management/incident_details +- /service_management/incident_management/investigate/ further_reading: -- link: "/service_management/incident_management/declare" +- link: "/incident_response/incident_management/declare" tag: "Documentation" text: "Declare an Incident" -- link: "/service_management/incident_management/describe" +- link: "/incident_response/incident_management/describe" tag: "Documentation" text: "Describe an Incident" --- @@ -64,7 +65,7 @@ In addition to housing your property fields, the Overview tab also provides the After declaring an incident, responders can use the Incident Details Page to apply available information so that they can describe and analyze the incident thoroughly. {{< whatsnext desc="To learn more about other investigative tools, see the following pages:">}} - {{< nextlink href="/service_management/incident_management/investigate/timeline" >}}Timeline: Track the sequence of events leading to and during the incident. Use visualizations and time-based data to understand the chronology and impact of events. + {{< nextlink href="/incident_response/incident_management/investigate/timeline" >}}Timeline: Track the sequence of events leading to and during the incident. Use visualizations and time-based data to understand the chronology and impact of events. {{< /nextlink >}} {{< /whatsnext >}} @@ -72,11 +73,11 @@ After declaring an incident, responders can use the Incident Details Page to app {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/incident_management/describe/#incident-details -[2]: /service_management/incident_management/#integrations -[3]: /service_management/incident_management/incident_settings#integrations -[4]: /service_management/incident_management/incident_settings/templates#postmortems +[1]: /incident_response/incident_management/describe/#incident-details +[2]: /incident_response/incident_management/#integrations +[3]: /incident_response/incident_management/incident_settings#integrations +[4]: /incident_response/incident_management/incident_settings/templates#postmortems [5]: https://app.datadoghq.com/incidents/settings#Postmortems -[6]: /service_management/incident_management/incident_settings/property_fields -[7]: /service_management/incident_management/notification/ -[8]: /service_management/incident_management/investigate/timeline +[6]: /incident_response/incident_management/incident_settings/property_fields +[7]: /incident_response/incident_management/notification/ +[8]: /incident_response/incident_management/investigate/timeline diff --git a/content/en/service_management/incident_management/investigate/timeline.md b/content/en/incident_response/incident_management/investigate/timeline.md similarity index 95% rename from content/en/service_management/incident_management/investigate/timeline.md rename to content/en/incident_response/incident_management/investigate/timeline.md index 244542df7a7..97eafdcfa62 100644 --- a/content/en/service_management/incident_management/investigate/timeline.md +++ b/content/en/incident_response/incident_management/investigate/timeline.md @@ -1,7 +1,9 @@ --- title: Timeline +aliases: +- /service_management/incident_management/investigate/timeline/ further_reading: -- link: "/service_management/incident_management/investigate/" +- link: "/incident_response/incident_management/investigate/" tag: "Documentation" text: "Investigate incidents" --- @@ -54,6 +56,6 @@ You can also add an image to an existing cell: {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/incident_management/#integrations +[1]: /incident_response/incident_management/#integrations [2]: /integrations/slack/?tab=slackapplicationus#using-datadog-incidents [3]: https://app.datadoghq.com/organization-settings/public-sharing/settings diff --git a/content/en/service_management/incident_management/notification.md b/content/en/incident_response/incident_management/notification.md similarity index 93% rename from content/en/service_management/incident_management/notification.md rename to content/en/incident_response/incident_management/notification.md index 7c845bfc162..c4de41a1fc0 100644 --- a/content/en/service_management/incident_management/notification.md +++ b/content/en/incident_response/incident_management/notification.md @@ -1,7 +1,9 @@ --- title: Incident Notification +aliases: +- /service_management/incident_management/notification/ further_reading: -- link: "/service_management/incident_management/incident_settings" +- link: "/incident_response/incident_management/incident_settings" tag: "Documentation" text: "Customize notifications in Incident Settings" - link: "/monitors/notify/variables/?tab=is_alert" @@ -69,7 +71,7 @@ For more information on how to create a message template, see the [Incident Sett {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/incident_management/incident_settings/notification_rules +[1]: /incident_response/incident_management/incident_settings/notification_rules [2]: /monitors/notify/variables/?tab=is_alert -[3]: /service_management/incident_management/incident_settings/templates -[4]: /service_management/on-call/ \ No newline at end of file +[3]: /incident_response/incident_management/incident_settings/templates +[4]: /incident_response/on-call/ \ No newline at end of file diff --git a/content/en/service_management/incident_management/response_team.md b/content/en/incident_response/incident_management/response_team.md similarity index 91% rename from content/en/service_management/incident_management/response_team.md rename to content/en/incident_response/incident_management/response_team.md index bc3ea939f11..53d074778ee 100644 --- a/content/en/service_management/incident_management/response_team.md +++ b/content/en/incident_response/incident_management/response_team.md @@ -1,7 +1,9 @@ --- title: Incident Response Team +aliases: +- /service_management/incident_management/response_team/ further_reading: -- link: "/service_management/incident_management/incident_settings/responder_types" +- link: "/incident_response/incident_management/incident_settings/responder_types" tag: "Documentation" text: "Customize responder types in Incident Settings" --- @@ -45,4 +47,4 @@ When you assign a responder type, the assignee is notified about it in Slack. {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/incident_management/incident_settings/responder_types +[1]: /incident_response/incident_management/incident_settings/responder_types diff --git a/content/en/service_management/incident_management/zoom_integration.md b/content/en/incident_response/incident_management/zoom_integration.md similarity index 91% rename from content/en/service_management/incident_management/zoom_integration.md rename to content/en/incident_response/incident_management/zoom_integration.md index 1d06ded10d0..eb1001fab4a 100644 --- a/content/en/service_management/incident_management/zoom_integration.md +++ b/content/en/incident_response/incident_management/zoom_integration.md @@ -1,6 +1,8 @@ --- title: Zoom Integration description: Connect Zoom to Datadog to help your team collaborate +aliases: +- /service_management/incident_management/zoom_integration/ private: true --- @@ -14,7 +16,7 @@ By connecting Zoom and Datadog, you can quickly create Zoom meetings to collabor To install the Datadog for Zoom app: -1. In Datadog, find the Incidents Settings page under **Service Management**. +1. In Datadog, find the [**Incidents Settings**][3] page. 2. Go to **Integrations** and enable the **Automatically create a meeting in Zoom for every incident** toggle. This setting replaces the **Add Video Call** button with a **Start Zoom Call** button for one-click Zoom meeting creation from Datadog's incident overview page. 3. When you click the **Start Zoom Call** button, you are prompted to add the Datadog Zoom App. Be sure to allow it to view and manage information on Zoom's behalf. @@ -46,3 +48,4 @@ Need help? Contact [Datadog support][1]. [1]: /help/ [2]: https://developers.zoom.us/docs/integrations/oauth-scopes/ +[3]: https://app.datadoghq.com/incidents/settings \ No newline at end of file diff --git a/content/en/service_management/on-call/_index.md b/content/en/incident_response/on-call/_index.md similarity index 83% rename from content/en/service_management/on-call/_index.md rename to content/en/incident_response/on-call/_index.md index d51a383ab4b..9ce7d996740 100644 --- a/content/en/service_management/on-call/_index.md +++ b/content/en/incident_response/on-call/_index.md @@ -1,5 +1,7 @@ --- title: On-Call +aliases: +- /service_management/on-call/ further_reading: - link: 'https://www.datadoghq.com/blog/datadog-on-call/' tag: 'Blog' @@ -83,11 +85,11 @@ To restrict access to an On-Call resource: To get started with On-Call, [onboard an On-Call Team][1] and ensure that all Team members configure their [On-Call profile settings][2] to receive notifications. {{< whatsnext desc="This section includes the following topics:">}} - {{< nextlink href="/service_management/on-call/teams">}}Onboard a Team: Create a new On-Call Team, add an existing Datadog Team to On-Call, or import a team from PagerDuty.{{< /nextlink >}} - {{< nextlink href="/service_management/on-call/triggering_pages">}}Trigger a Page: Page a team through monitors, incidents, security signals, etc.; or manually send a Page through Datadog, Slack, Microsoft Teams, or the Datadog API. {{< /nextlink >}} - {{< nextlink href="/service_management/on-call/escalation_policies">}}Escalation Policies: Define steps for how a Page is sent to different schedules. {{< /nextlink >}} - {{< nextlink href="/service_management/on-call/schedules">}}Schedules: Define timetables for Team members' on-call rotations.{{< /nextlink >}} - {{< nextlink href="/service_management/on-call/profile_settings">}}Profile Settings: Configure your contact methods and notification preferences to ensure you receive timely and effective Pages.{{< /nextlink >}} + {{< nextlink href="/incident_response/on-call/teams">}}Onboard a Team: Create a new On-Call Team, add an existing Datadog Team to On-Call, or import a team from PagerDuty.{{< /nextlink >}} + {{< nextlink href="/incident_response/on-call/triggering_pages">}}Trigger a Page: Page a team through monitors, incidents, security signals, etc.; or manually send a Page through Datadog, Slack, Microsoft Teams, or the Datadog API. {{< /nextlink >}} + {{< nextlink href="/incident_response/on-call/escalation_policies">}}Escalation Policies: Define steps for how a Page is sent to different schedules. {{< /nextlink >}} + {{< nextlink href="/incident_response/on-call/schedules">}}Schedules: Define timetables for Team members' on-call rotations.{{< /nextlink >}} + {{< nextlink href="/incident_response/on-call/profile_settings">}}Profile Settings: Configure your contact methods and notification preferences to ensure you receive timely and effective Pages.{{< /nextlink >}} {{< /whatsnext >}} ## Billing @@ -98,8 +100,8 @@ On-Call is a seat-based SKU. To learn more about how On-Call is billed and how t {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/on-call/teams -[2]: /service_management/on-call/profile_settings +[1]: /incident_response/on-call/teams +[2]: /incident_response/on-call/profile_settings [3]: /account_management/rbac/granular_access/ [4]: /account_management/rbac/#role-based-access-control [5]: https://www.datadoghq.com/pricing/?product=incident-response#products diff --git a/content/en/service_management/on-call/automations.md b/content/en/incident_response/on-call/automations.md similarity index 96% rename from content/en/service_management/on-call/automations.md rename to content/en/incident_response/on-call/automations.md index 9c9e826117d..8927ed9a417 100644 --- a/content/en/service_management/on-call/automations.md +++ b/content/en/incident_response/on-call/automations.md @@ -1,7 +1,9 @@ --- title: Automations +aliases: +- /service_management/on-call/automations/ further_reading: -- link: '/service_management/on-call/' +- link: '/incident_response/on-call/' tag: 'Documentation' text: 'Datadog On-Call' - link: "https://docs.datadoghq.com/service_management/workflows/" diff --git a/content/en/service_management/on-call/cross_org_paging.md b/content/en/incident_response/on-call/cross_org_paging.md similarity index 98% rename from content/en/service_management/on-call/cross_org_paging.md rename to content/en/incident_response/on-call/cross_org_paging.md index 0dee89771c5..12b51d7ed9b 100644 --- a/content/en/service_management/on-call/cross_org_paging.md +++ b/content/en/incident_response/on-call/cross_org_paging.md @@ -1,8 +1,10 @@ --- title: Cross-org Paging +aliases: +- /service_management/on-call/cross_org_paging/ private: true further_reading: -- link: '/service_management/on-call/' +- link: '/incident_response/on-call/' tag: 'Documentation' text: 'Datadog On-Call' --- diff --git a/content/en/service_management/on-call/escalation_policies.md b/content/en/incident_response/on-call/escalation_policies.md similarity index 97% rename from content/en/service_management/on-call/escalation_policies.md rename to content/en/incident_response/on-call/escalation_policies.md index 6242f8988be..a8b593ddbfd 100644 --- a/content/en/service_management/on-call/escalation_policies.md +++ b/content/en/incident_response/on-call/escalation_policies.md @@ -1,7 +1,9 @@ --- title: Escalation Policies +aliases: +- /service_management/on-call/escalation_policies/ further_reading: -- link: '/service_management/on-call/' +- link: '/incident_response/on-call/' tag: 'Documentation' text: 'Datadog On-Call' --- @@ -92,6 +94,6 @@ Common use cases for paging an entire Team are: - Maximum number of notify targets (individuals, teams, or schedules) per escalation step: 10 - Minimum time before escalation to the next step: one minute -[1]: /service_management/on-call/teams +[1]: /incident_response/on-call/teams [2]: https://app.datadoghq.com/on-call/escalation-policies [3]: https://app.datadoghq.com/on-call/escalation-policies/create diff --git a/content/en/incident_response/on-call/guides/_index.md b/content/en/incident_response/on-call/guides/_index.md new file mode 100644 index 00000000000..98bc8321c0d --- /dev/null +++ b/content/en/incident_response/on-call/guides/_index.md @@ -0,0 +1,14 @@ +--- +title: On-Call Guides +aliases: +- /service_management/on-call/guides/ +private: false +disable_toc: true +--- + +{{< whatsnext desc="General guides:">}} + {{< nextlink href="/incident_response/on-call/guides/configure-mobile-device-for-on-call" >}}Set up your mobile device for Datadog On-Call{{< /nextlink >}} + {{< nextlink href="/incident_response/on-call/guides/migrating-from-your-current-providers" >}}Migrate from your current on-call provider{{< /nextlink >}} + {{< nextlink href="/incident_response/on-call/guides/migrate-your-pagerduty-resources-to-on-call" >}}Migrate PagerDuty resources to Datadog On-Call{{< /nextlink >}} + {{< nextlink href="/incident_response/on-call/guides/offboarding-teams-and-users" >}}Offboard teams and users from Datadog On-Call{{< /nextlink >}} +{{< /whatsnext >}} diff --git a/content/en/service_management/on-call/guides/configure-mobile-device-for-on-call.md b/content/en/incident_response/on-call/guides/configure-mobile-device-for-on-call.md similarity index 98% rename from content/en/service_management/on-call/guides/configure-mobile-device-for-on-call.md rename to content/en/incident_response/on-call/guides/configure-mobile-device-for-on-call.md index 94793cc7ce6..edbee220f07 100644 --- a/content/en/service_management/on-call/guides/configure-mobile-device-for-on-call.md +++ b/content/en/incident_response/on-call/guides/configure-mobile-device-for-on-call.md @@ -1,7 +1,9 @@ --- title: Set Up Your Mobile Device for Datadog On-Call +aliases: +- /service_management/on-call/guides/configure-mobile-device-for-on-call/ further_reading: -- link: "https://docs.datadoghq.com/service_management/on-call/" +- link: "/incident_response/on-call/" tag: "Documentation" text: "On-Call Documentation" --- diff --git a/content/en/service_management/on-call/guides/migrate-your-pagerduty-resources-to-on-call.md b/content/en/incident_response/on-call/guides/migrate-your-pagerduty-resources-to-on-call.md similarity index 96% rename from content/en/service_management/on-call/guides/migrate-your-pagerduty-resources-to-on-call.md rename to content/en/incident_response/on-call/guides/migrate-your-pagerduty-resources-to-on-call.md index ef92948ce94..69d17a4fe22 100644 --- a/content/en/service_management/on-call/guides/migrate-your-pagerduty-resources-to-on-call.md +++ b/content/en/incident_response/on-call/guides/migrate-your-pagerduty-resources-to-on-call.md @@ -1,7 +1,9 @@ --- title: Migrate PagerDuty resources to Datadog On-Call +aliases: +- /service_management/on-call/guides/migrate-your-pagerduty-resources-to-on-call/ further_reading: -- link: "/service_management/on-call/" +- link: "/incident_response/on-call/" tag: "Documentation" text: "On-Call Documentation" - link: "/integrations/pagerduty/" diff --git a/content/en/service_management/on-call/guides/migrating-from-your-current-providers.md b/content/en/incident_response/on-call/guides/migrating-from-your-current-providers.md similarity index 94% rename from content/en/service_management/on-call/guides/migrating-from-your-current-providers.md rename to content/en/incident_response/on-call/guides/migrating-from-your-current-providers.md index d32994800c6..1e705cf1158 100644 --- a/content/en/service_management/on-call/guides/migrating-from-your-current-providers.md +++ b/content/en/incident_response/on-call/guides/migrating-from-your-current-providers.md @@ -1,10 +1,12 @@ --- title: Migrating from your current on-call provider +aliases: +- /service_management/on-call/guides/migrating-from-your-current-providers/ further_reading: -- link: "/service_management/on-call/" +- link: "/incident_response/on-call/" tag: "Documentation" text: "On-Call" -- link: "/service_management/incident_management/" +- link: "/incident_response/incident_management/" tag: "Documentation" text: "Incident Management" --- @@ -70,7 +72,7 @@ Before you start configuring Datadog On-Call, review the concept of [Teams][4]. After reviewing the team model and mapping your existing assets, you're ready to configure Datadog On-Call to reflect your desired structure. -
If you're migrating from PagerDuty, Datadog provides a dedicated migration tool that can help you selectively import schedules and escalation policies. Use it during setup to reduce manual effort and avoid migrating unused configurations.
+
If you're migrating from PagerDuty, Datadog provides a dedicated migration tool that can help you selectively import schedules and escalation policies. Use it during setup to reduce manual effort and avoid migrating unused configurations.
During setup, be sure to: @@ -146,9 +148,9 @@ With your core migration to Datadog On-Call complete, shift focus to long-term o [1]: https://app.datadoghq.com/on-call/ [2]: /integrations/ [3]: /monitors/notify/#bulk-editing-monitor--handles -[4]: /service_management/on-call/teams/ -[6]: /service_management/incident_management -[7]: /service_management/on-call/schedules/ +[4]: /incident_response/on-call/teams/ +[6]: /incident_response/incident_management +[7]: /incident_response/on-call/schedules/ [8]: https://app.datadoghq.com/on-call/analytics [9]: https://app.datadoghq.com/release-notes?category=Incident%20Response [10]: https://chat.datadoghq.com/ diff --git a/content/en/service_management/on-call/guides/offboarding-teams-and-users.md b/content/en/incident_response/on-call/guides/offboarding-teams-and-users.md similarity index 90% rename from content/en/service_management/on-call/guides/offboarding-teams-and-users.md rename to content/en/incident_response/on-call/guides/offboarding-teams-and-users.md index 69ab67cede9..99bd7a1581e 100644 --- a/content/en/service_management/on-call/guides/offboarding-teams-and-users.md +++ b/content/en/incident_response/on-call/guides/offboarding-teams-and-users.md @@ -1,13 +1,15 @@ --- title: Offboarding teams and users from Datadog On-Call +aliases: +- /service_management/on-call/guides/offboarding-teams-and-users/ further_reading: -- link: "/service_management/on-call/" +- link: "/incident_response/on-call/" tag: "Documentation" text: "On-Call" -- link: "/service_management/on-call/teams/" +- link: "/incident_response/on-call/teams/" tag: "Documentation" text: "Teams" -- link: "/service_management/on-call/schedules/" +- link: "/incident_response/on-call/schedules/" tag: "Documentation" text: "Schedules" --- @@ -69,8 +71,8 @@ As an admin, you can also manage this yourself by navigating to **On-Call > Sett **Note**, Notification Preferences make a user pageable and therefore billable. Having only contact methods (for example, push notifications) defined is a non-billable action and won't incur charges. -[1]: /service_management/on-call/ -[2]: /service_management/on-call/teams/ -[3]: /service_management/on-call/schedules/ -[4]: /service_management/on-call/escalation_policies/ +[1]: /incident_response/on-call/ +[2]: /incident_response/on-call/teams/ +[3]: /incident_response/on-call/schedules/ +[4]: /incident_response/on-call/escalation_policies/ [5]: /account_management/rbac/ diff --git a/content/en/service_management/on-call/profile_settings.md b/content/en/incident_response/on-call/profile_settings.md similarity index 94% rename from content/en/service_management/on-call/profile_settings.md rename to content/en/incident_response/on-call/profile_settings.md index c7f1a4a4fbb..5f139ad02e1 100644 --- a/content/en/service_management/on-call/profile_settings.md +++ b/content/en/incident_response/on-call/profile_settings.md @@ -1,7 +1,9 @@ --- title: Profile Settings +aliases: +- /service_management/on-call/profile_settings/ further_reading: -- link: '/service_management/on-call/' +- link: '/incident_response/on-call/' tag: 'Documentation' text: 'Datadog On-Call' --- @@ -68,6 +70,6 @@ Under **Other Notifications**, you can opt to receive a **Shift reminder** befor [1]: https://app.datadoghq.com/on-call/profile [2]: /service_management/mobile/?tab=ios [3]: /mobile -[4]: /service_management/on-call/guides/configure-mobile-device-for-on-call -[5]: /service_management/on-call/routing_rules -[6]: /service_management/on-call/escalation_policies +[4]: /incident_response/on-call/guides/configure-mobile-device-for-on-call +[5]: /incident_response/on-call/routing_rules +[6]: /incident_response/on-call/escalation_policies diff --git a/content/en/service_management/on-call/routing_rules.md b/content/en/incident_response/on-call/routing_rules.md similarity index 96% rename from content/en/service_management/on-call/routing_rules.md rename to content/en/incident_response/on-call/routing_rules.md index dd510a593f9..eb9c2e79ee6 100644 --- a/content/en/service_management/on-call/routing_rules.md +++ b/content/en/incident_response/on-call/routing_rules.md @@ -1,11 +1,12 @@ --- title: Routing Rules further_reading: -- link: '/service_management/on-call/' +- link: '/incident_response/on-call/' tag: 'Documentation' text: 'Datadog On-Call' aliases: - /service_management/on-call/processing_rules/ + - /service_management/on-call/routing_rules/ --- ## Overview @@ -64,6 +65,6 @@ Routing rules use [Datadog query syntax][3] and support multiple `if/else` condi {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/on-call/teams +[1]: /incident_response/on-call/teams [2]: https://app.datadoghq.com/on-call/teams [3]: /tracing/trace_explorer/query_syntax/ diff --git a/content/en/service_management/on-call/schedules.md b/content/en/incident_response/on-call/schedules.md similarity index 98% rename from content/en/service_management/on-call/schedules.md rename to content/en/incident_response/on-call/schedules.md index d518a311950..549d8689aea 100644 --- a/content/en/service_management/on-call/schedules.md +++ b/content/en/incident_response/on-call/schedules.md @@ -1,7 +1,9 @@ --- title: Schedules +aliases: +- /service_management/on-call/schedules/ further_reading: -- link: '/service_management/on-call/' +- link: '/incident_response/on-call/' tag: 'Documentation' text: 'Datadog On-Call' --- @@ -119,4 +121,4 @@ When team members leave your organisation, they are not automatically removed fr [3]: https://support.google.com/calendar/answer/37100?hl=en&co=GENIE.Platform%3DDesktop [4]: https://support.microsoft.com/en-us/office/import-or-subscribe-to-a-calendar-in-outlook-com-or-outlook-on-the-web-cff1429c-5af6-41ec-a5b4-74f2c278e98c [5]: https://support.apple.com/en-us/102301 -[6]: /service_management/on-call/profile_settings/ +[6]: /incident_response/on-call/profile_settings/ diff --git a/content/en/service_management/on-call/teams.md b/content/en/incident_response/on-call/teams.md similarity index 90% rename from content/en/service_management/on-call/teams.md rename to content/en/incident_response/on-call/teams.md index 963bd7833b0..c8d623700e7 100644 --- a/content/en/service_management/on-call/teams.md +++ b/content/en/incident_response/on-call/teams.md @@ -1,7 +1,9 @@ --- title: Onboard a Team +aliases: +- /service_management/on-call/teams/ further_reading: -- link: '/service_management/on-call/' +- link: '/incident_response/on-call/' tag: 'Documentation' text: 'Datadog On-Call' --- @@ -48,10 +50,10 @@ Ensure that your On-Call Team members have set up their [Profile Settings][8]. {{< partial name="whats-next/whats-next.html" >}} [1]: /account_management/teams/ -[2]: /service_management/on-call/ +[2]: /incident_response/on-call/ [3]: https://app.datadoghq.com/organization-settings/teams [4]: https://app.datadoghq.com/on-call/ -[5]: /service_management/on-call/escalation_policies -[6]: /service_management/on-call/schedules -[7]: /service_management/on-call/pages -[8]: /service_management/on-call/profile_settings \ No newline at end of file +[5]: /incident_response/on-call/escalation_policies +[6]: /incident_response/on-call/schedules +[7]: /incident_response/on-call/pages +[8]: /incident_response/on-call/profile_settings \ No newline at end of file diff --git a/content/en/service_management/on-call/triggering_pages/_index.md b/content/en/incident_response/on-call/triggering_pages/_index.md similarity index 92% rename from content/en/service_management/on-call/triggering_pages/_index.md rename to content/en/incident_response/on-call/triggering_pages/_index.md index 1c888726d12..851474573b5 100644 --- a/content/en/service_management/on-call/triggering_pages/_index.md +++ b/content/en/incident_response/on-call/triggering_pages/_index.md @@ -2,8 +2,9 @@ title: Trigger a Page aliases: - /service_management/on-call/pages +- /service_management/on-call/triggering_pages/ further_reading: -- link: '/service_management/on-call/' +- link: '/incident_response/on-call/' tag: 'Documentation' text: 'Datadog On-Call' --- @@ -81,8 +82,8 @@ To send Pages to Slack, see [Routing Rules][4]. {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/on-call/teams +[1]: /incident_response/on-call/teams [2]: https://app.datadoghq.com/on-call/teams -[3]: /service_management/on-call/triggering_pages/live_call_routing -[4]: /service_management/on-call/routing_rules/#send-pages-to-slack-or-microsoft-teams -[5]: /service_management/incident_management/notification/#trigger-a-page-from-an-incident +[3]: /incident_response/on-call/triggering_pages/live_call_routing +[4]: /incident_response/on-call/routing_rules/#send-pages-to-slack-or-microsoft-teams +[5]: /incident_response/incident_management/notification/#trigger-a-page-from-an-incident diff --git a/content/en/service_management/on-call/triggering_pages/live_call_routing.md b/content/en/incident_response/on-call/triggering_pages/live_call_routing.md similarity index 97% rename from content/en/service_management/on-call/triggering_pages/live_call_routing.md rename to content/en/incident_response/on-call/triggering_pages/live_call_routing.md index 83f10573055..a265d0efbe5 100644 --- a/content/en/service_management/on-call/triggering_pages/live_call_routing.md +++ b/content/en/incident_response/on-call/triggering_pages/live_call_routing.md @@ -1,7 +1,9 @@ --- title: Live Call Routing +aliases: +- /service_management/on-call/triggering_pages/live_call_routing/ further_reading: -- link: '/service_management/On-Call/' +- link: '/incident_response/On-Call/' tag: 'Documentation' text: 'Datadog On-Call' --- diff --git a/content/en/service_management/status_pages/_index.md b/content/en/incident_response/status_pages/_index.md similarity index 97% rename from content/en/service_management/status_pages/_index.md rename to content/en/incident_response/status_pages/_index.md index a7455d2cd3d..e0e94180ddd 100644 --- a/content/en/service_management/status_pages/_index.md +++ b/content/en/incident_response/status_pages/_index.md @@ -1,16 +1,18 @@ --- title: Status Pages +aliases: +- /service_management/status_pages/ further_reading: - link: https://www.datadoghq.com/blog/status-pages tag: Blog text: Keep stakeholders informed with Datadog Status Pages -- link: "service_management/incident_management/" +- link: "/incident_response/incident_management/" tag: "Documentation" text: "Learn more about Incident Management" -- link: "service_management/on-call/" +- link: "/incident_response/on-call/" tag: "Documentation" text: "Learn more about On-Call Scheduling" -- link: "service_management/incident_management/integrations/status_pages" +- link: "/incident_response/incident_management/integrations/status_pages" tag: "Documentation" text: "Integrate Datadog Status Pages with Incident Management" - link: "https://www.datadoghq.com/blog/status-pages/" @@ -65,7 +67,7 @@ To create, update, or publish Status Pages, you must have `status_pages_settings ## Create a status page -1. In Datadog, navigate to [**Service Management > Status Pages**][2]. +1. In Datadog, navigate to [**Status Pages**][2]. 1. Click **Create Status Page** and follow the onboarding flow: | Field | Description | diff --git a/content/en/integrations/guide/events-from-sns-emails.md b/content/en/integrations/guide/events-from-sns-emails.md index 8980be28887..b51dc6fa988 100644 --- a/content/en/integrations/guide/events-from-sns-emails.md +++ b/content/en/integrations/guide/events-from-sns-emails.md @@ -38,7 +38,7 @@ Configure alerting based on the emails from your SNS topic with an [event monito {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/events/guides/email/ +[1]: /events/guides/email/ [2]: https://app.datadoghq.com/event/explorer [3]: /monitors/types/event/ [4]: /events/explorer/ diff --git a/content/en/integrations/guide/servicenow-itom-itsm-setup.md b/content/en/integrations/guide/servicenow-itom-itsm-setup.md index 5ae4d69aff2..5e02f866ef6 100644 --- a/content/en/integrations/guide/servicenow-itom-itsm-setup.md +++ b/content/en/integrations/guide/servicenow-itom-itsm-setup.md @@ -399,10 +399,10 @@ Need additional help? Contact [Datadog support][10]. [3]: /integrations/servicenow/#configure-the-servicenow-tile-in-datadog [4]: https://app.datadoghq.com/integrations?integrationId=servicenow [5]: https://app.datadoghq.com/cases/settings -[6]: /service_management/case_management/notifications_integrations/#servicenow +[6]: /incident_response/case_management/notifications_integrations/#servicenow [7]: /account_management/org_settings/service_accounts/#create-or-revoke-application-keys [8]: https://docs.servicenow.com/en-US/bundle/sandiego-it-service-management/page/product/incident-management/task/def-prio-lookup-rules.html [9]: https://app.datadoghq.com/incidents/settings?section=integrations [10]: /help/ [11]: /monitors/configuration/?tab=thresholdalert#multi-alert -[12]: /service_management/incident_management/integrations/servicenow +[12]: /incident_response/incident_management/integrations/servicenow diff --git a/content/en/internal_developer_portal/eng_reports/_index.md b/content/en/internal_developer_portal/eng_reports/_index.md index c0d69e7e402..8c4cd6ec434 100644 --- a/content/en/internal_developer_portal/eng_reports/_index.md +++ b/content/en/internal_developer_portal/eng_reports/_index.md @@ -1,10 +1,10 @@ --- title: Engineering Report further_reading: -- link: "/service_management/service_level_objectives/" +- link: "/service_level_objectives/" tag: "Documentation" text: "Service Level Objectives" -- link: "service_management/incident_management/" +- link: "/incident_response/incident_management/" tag: "Documentation" text: "Incident Management" - link: "software_catalog/scorecards/" diff --git a/content/en/internal_developer_portal/eng_reports/reliability_overview.md b/content/en/internal_developer_portal/eng_reports/reliability_overview.md index 9ee5b7d59c5..f2322797cac 100644 --- a/content/en/internal_developer_portal/eng_reports/reliability_overview.md +++ b/content/en/internal_developer_portal/eng_reports/reliability_overview.md @@ -3,10 +3,10 @@ title: Reliability Overview aliases: - /software_catalog/eng_reports/reliability_overview/ further_reading: -- link: "/service_management/service_level_objectives/" +- link: "/service_level_objectives/" tag: "Documentation" text: "Service Level Objectives" -- link: "service_management/incident_management/" +- link: "/incident_response/incident_management/" tag: "Documentation" text: "Incident Management" - link: "dashboards/" diff --git a/content/en/internal_developer_portal/overview_pages.md b/content/en/internal_developer_portal/overview_pages.md index de426d8adf0..2c270a922f6 100644 --- a/content/en/internal_developer_portal/overview_pages.md +++ b/content/en/internal_developer_portal/overview_pages.md @@ -9,10 +9,10 @@ further_reading: - link: "monitors/" tag: "Documentation" text: "Datadog Monitors" -- link: "service_management/incident_management/" +- link: "/incident_response/incident_management/" tag: "Documentation" text: "Incident Management" -- link: "service_management/service_level_objectives/" +- link: "/service_level_objectives/" tag: "Documentation" text: "Service Level Objectives" - link: "error_tracking" @@ -110,11 +110,11 @@ Here are some example customizations you can make with the cloned dashboard: [1]: /actions/app_builder [2]: /actions/app_builder/embedded_apps/ -[3]: /service_management/incident_management/ +[3]: /incident_response/incident_management/ [4]: /error_tracking/ [5]: /watchdog/ [6]: /monitors/ -[7]: /service_management/service_level_objectives/ +[7]: /service_level_objectives/ [8]: /account_management/teams/ [9]: /actions/app_builder/#apps-created-by-datadog [10]: /actions/connections diff --git a/content/en/internal_developer_portal/scorecards/scorecard_configuration.md b/content/en/internal_developer_portal/scorecards/scorecard_configuration.md index 05856ae29de..51310776f91 100644 --- a/content/en/internal_developer_portal/scorecards/scorecard_configuration.md +++ b/content/en/internal_developer_portal/scorecards/scorecard_configuration.md @@ -122,7 +122,7 @@ You can set scopes for both out-of-the-box and custom rules. When you add a scop {{< partial name="whats-next/whats-next.html" >}} [1]: https://app.datadoghq.com/services/scorecard -[2]: /service_management/service_level_objectives/ +[2]: /service_level_objectives/ [3]: https://app.datadoghq.com/monitors/templates [4]: /tracing/services/deployment_tracking/ [5]: /tracing/other_telemetry/connect_logs_and_traces/ diff --git a/content/en/internal_developer_portal/software_catalog/set_up/ownership.md b/content/en/internal_developer_portal/software_catalog/set_up/ownership.md index 628746133c6..42e73ff47ea 100644 --- a/content/en/internal_developer_portal/software_catalog/set_up/ownership.md +++ b/content/en/internal_developer_portal/software_catalog/set_up/ownership.md @@ -35,7 +35,7 @@ After creating a Team, you can add reference links, configure notifications, and To add or update an entity's owner in Datadog: -1. Go to **Service Management** > **Software Catalog**, and open the entity. +1. Go to **Software Catalog**, and open the entity. 2. Click **Edit in UI** on the entity page. 3. In the **Ownership** section, set the **Owner** and optionally add **Additional owners**. - Search by team name or paste a handle (for example, `team:example-team`). diff --git a/content/en/internal_developer_portal/use_cases/incident_response.md b/content/en/internal_developer_portal/use_cases/incident_response.md index ea6921be28a..89a12652848 100644 --- a/content/en/internal_developer_portal/use_cases/incident_response.md +++ b/content/en/internal_developer_portal/use_cases/incident_response.md @@ -9,7 +9,7 @@ aliases: - /service_catalog/use_cases/upstream_downstream_dependencies - /software_catalog/use_cases/incident_response further_reading: - - link: "/service_management/incident_management/" + - link: "/incident_response/incident_management/" tag: "Documentation" text: "Incident Management" - link: "/integrations/pagerduty/" @@ -43,5 +43,5 @@ To view incident statuses for upstream and downstream dependencies, click a serv {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/incident_management/ +[1]: /incident_response/incident_management/ [2]: /integrations/pagerduty/ diff --git a/content/en/llm_observability/evaluations/custom_llm_as_a_judge_evaluations.md b/content/en/llm_observability/evaluations/custom_llm_as_a_judge_evaluations.md index c309e18b684..c631400b4ab 100644 --- a/content/en/llm_observability/evaluations/custom_llm_as_a_judge_evaluations.md +++ b/content/en/llm_observability/evaluations/custom_llm_as_a_judge_evaluations.md @@ -279,7 +279,7 @@ You can: [1]: https://app.datadoghq.com/llm/evaluations [2]: /llm_observability/evaluations/managed_evaluations#connect-your-llm-provider-account -[3]: /service_management/events/explorer/facets/ +[3]: /events/explorer/facets/ [4]: /monitors/ [5]: https://arxiv.org/abs/2504.00050 [6]: /llm_observability/evaluations/evaluation_compatibility diff --git a/content/en/logs/guide/best-practices-for-log-management.md b/content/en/logs/guide/best-practices-for-log-management.md index 8db6bd63dc7..0b6f1f4f9c7 100644 --- a/content/en/logs/guide/best-practices-for-log-management.md +++ b/content/en/logs/guide/best-practices-for-log-management.md @@ -224,7 +224,7 @@ If you want to see user activities, such as who changed the retention of an inde [14]: https://app.datadoghq.com/logs [15]: /logs/explorer/search/ [16]: /logs/indexes/#set-daily-quota -[17]: /service_management/events/explorer/facets +[17]: /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]: /logs/log_configuration/indexes/#exclusion-filters diff --git a/content/en/logs/log_configuration/archives.md b/content/en/logs/log_configuration/archives.md index 0a8317b295c..ca2a8532695 100644 --- a/content/en/logs/log_configuration/archives.md +++ b/content/en/logs/log_configuration/archives.md @@ -438,4 +438,4 @@ This directory structure simplifies the process of querying your historical log [12]: /account_management/rbac/permissions#logs_read_index_data [13]: /account_management/rbac/permissions#logs_read_data [14]: /logs/explorer/live_tail/ -[15]: /service_management/events/explorer/ +[15]: /events/explorer/ diff --git a/content/en/metrics/explorer.md b/content/en/metrics/explorer.md index e4e6c1580d3..c8803461a27 100644 --- a/content/en/metrics/explorer.md +++ b/content/en/metrics/explorer.md @@ -100,7 +100,7 @@ For more information, see the [Quick Graphs][7] documentation. [5]: /metrics/introduction/#space-aggregation [6]: /dashboards/querying/#advanced-graphing [7]: /dashboards/guide/quick-graphs/ -[8]: /service_management/incident_management/ +[8]: /incident_response/incident_management/ [9]: /monitors/ [10]: /dashboards/ [11]: /account_management/rbac/permissions/#access-management diff --git a/content/en/metrics/overview.md b/content/en/metrics/overview.md index c336ac31cd6..419a4060e11 100644 --- a/content/en/metrics/overview.md +++ b/content/en/metrics/overview.md @@ -139,7 +139,7 @@ Use the search bar in this section to view the latest data and configuration opt [15]: /tracing/trace_pipeline/generate_metrics/ [16]: /real_user_monitoring/platform/generate_metrics/ [17]: /infrastructure/process/increase_process_retention/#generate-a-process-based-metric -[18]: /service_management/events/guides/usage/#custom-metrics +[18]: /events/guides/usage/#custom-metrics [19]: /metrics/metrics-without-limits/ [20]: /metrics/distributions/ [21]: /metrics/custom_metrics/historical_metrics/ diff --git a/content/en/mobile/_index.md b/content/en/mobile/_index.md index 1c65e701145..f6f6a3a7512 100644 --- a/content/en/mobile/_index.md +++ b/content/en/mobile/_index.md @@ -343,8 +343,8 @@ For help with troubleshooting, [contact Datadog support][13]. You can also send [17]: https://docs.datadoghq.com/software_catalog/manage/ [18]: https://docs.datadoghq.com/notebooks/ [19]: https://docs.datadoghq.com/notebooks/#notebook-tags -[20]: https://docs.datadoghq.com/service_management/on-call/ -[21]: /service_management/on-call/guides/configure-mobile-device-for-on-call/?tab=ios +[20]: https://docs.datadoghq.com/incident_response/on-call/ +[21]: /incident_response/on-call/guides/configure-mobile-device-for-on-call/?tab=ios [22]: https://docs.datadoghq.com/logs/explorer/analytics/patterns/ [23]: https://docs.datadoghq.com/logs/explorer/search_syntax/ [24]: /dashboards/configure/#configuration-actions diff --git a/content/en/mobile/guide/configure-mobile-device-for-on-call.md b/content/en/mobile/guide/configure-mobile-device-for-on-call.md index a11510e79f2..fc8adc404b7 100644 --- a/content/en/mobile/guide/configure-mobile-device-for-on-call.md +++ b/content/en/mobile/guide/configure-mobile-device-for-on-call.md @@ -2,7 +2,7 @@ title: Set Up Your Mobile Device for Datadog On-Call description: "Configure your mobile device for reliable on-call notifications with critical alerts, Do Not Disturb bypass, and telephony contact setup." further_reading: -- link: "https://docs.datadoghq.com/service_management/on-call/" +- link: "https://docs.datadoghq.com/incident_response/on-call/" tag: "Documentation" text: "On-Call Documentation" - link: "https://docs.datadoghq.com/service_management/mobile/" @@ -213,4 +213,4 @@ For help with troubleshooting, [contact Datadog support][2]. You can also send a [2]: /help/ [3]: https://chat.datadoghq.com/ [4]: https://datadoghq.slack.com/archives/C0114D5EHNG -[5]: /service_management/on-call/ +[5]: /incident_response/on-call/ diff --git a/content/en/mobile/guide/setup_mobile_device.md b/content/en/mobile/guide/setup_mobile_device.md index 40509800360..e505a0320ce 100644 --- a/content/en/mobile/guide/setup_mobile_device.md +++ b/content/en/mobile/guide/setup_mobile_device.md @@ -95,7 +95,7 @@ Enable push notifications to ensure timely response to alerts from On-Call, inci 2. Enable the **Allow notifications** toggle. Datadog highly recommends you also enable **Sound and vibration** and **Show content on Lock screen**. {{< img src="service_management/mobile/android_notification.png" style="width:80%; background:none; border:none; box-shadow:none;" alt="Android notifications settings">}} -[4]: https://docs.datadoghq.com/service_management/on-call/guides/configure-mobile-device-for-on-call/?tab=ios +[4]: /incident_response/on-call/guides/configure-mobile-device-for-on-call/?tab=ios {{% /tab %}} diff --git a/content/en/mobile/push_notification.md b/content/en/mobile/push_notification.md index bf6cbd67285..d4f52f2140c 100644 --- a/content/en/mobile/push_notification.md +++ b/content/en/mobile/push_notification.md @@ -2,13 +2,13 @@ title: Set Up Push Notifications on Mobile App description: "Configure push notifications on iOS and Android for on-call alerts, incidents, and workflow updates with critical alert settings." further_reading: -- link: "https://docs.datadoghq.com/service_management/on-call/" +- link: "/incident_response/on-call/" tag: "Documentation" text: "On-Call Documentation" -- link: "https://docs.datadoghq.com/service_management/incident_management/notification/" +- link: "/incident_response/incident_management/notification/" tag: "Documentation" text: "Incident Notification Rules Documentation" -- link: "https://docs.datadoghq.com/getting_started/workflow_automation/" +- link: "/getting_started/workflow_automation/" tag: "Documentation" text: "Workflow Automation Documentation" --- @@ -169,6 +169,6 @@ Create [workflow automations][3] that send mobile push notifications. {{< partial name="whats-next/whats-next.html" >}} [1]:https://app.datadoghq.com/incidents/settings?_gl=1*334tvl*_gcl_aw*R0NMLjE3NDUwMDYwODQuQ2p3S0NBand0ZGlfQmhBQ0Vpd0E5N3k4QkxnWmU4cTdmazJtUlJoQ3o1OTZXcTNmRWJIQTk1Rzg4dnAtUmZtUHBQUGx0OVNVSjRlSk9Sb0Nwek1RQXZEX0J3RQ..*_gcl_au*MTAxODMyNDk1My4xNzQwNDk1NzA3LjExNzUxOTU1MTUuMTc0NjQ5NTU3OS4xNzQ2NDk1NTc5*_ga*MjExMzI1MjUyOS4xNzQ1ODU2NjMx*_ga_KN80RDFSQK*czE3NDY0OTQzMzYkbzU4JGcxJHQxNzQ2NDk5MzA0JGowJGwwJGg5NTQ2NTk0Ng..*_fplc*Q2V5WVJmNnRSV2R0RmljTDZyWmg3ZEVZMFZPeDNlTFhLZkxnenFCOXBvTUslMkZTWWk0a3JzVEw1cDU5YlZzTW55TE5YazY5bjdhJTJGOXpySzJ0TFMxTEozZms0WTVlOWVibEN5ZFBNNm1XYmJJQll0R0d4YnlralJ2eU1CS1NoUSUzRCUzRA..#Rules -[2]:https://docs.datadoghq.com/service_management/incident_management/incident_settings/notification_rules/ +[2] /incident_response/incident_management/incident_settings/notification_rules/ [3]:https://docs.datadoghq.com/getting_started/workflow_automation/ -[4]:/service_management/on-call/guides/configure-mobile-device-for-on-call +[4]: /incident_response/on-call/guides/configure-mobile-device-for-on-call diff --git a/content/en/mobile/widgets.md b/content/en/mobile/widgets.md index 0fd357b78ea..1d9bc9a768a 100644 --- a/content/en/mobile/widgets.md +++ b/content/en/mobile/widgets.md @@ -379,4 +379,4 @@ Lock screen widgets for On-Call, Monitors, SLOs, Incidents, and Dashboards are s [2]: /dashboards/widgets/slo/#setup [3]: /monitors/ [4]: /dashboards/ -[5]: /service_management/on-call/ +[5]: /incident_response/on-call/ diff --git a/content/en/monitors/downtimes/_index.md b/content/en/monitors/downtimes/_index.md index 7f71b76d672..d52645cd9cb 100644 --- a/content/en/monitors/downtimes/_index.md +++ b/content/en/monitors/downtimes/_index.md @@ -193,7 +193,7 @@ Datadog can proactively mute monitors related to the manual shutdown of certain [7]: /monitors/notify/#overview [8]: /integrations/#cat-notification [9]: /monitors/status/ -[10]: /service_management/events/explorer +[10]: /events/explorer [11]: /api/latest/downtimes/#cancel-a-downtime [12]: /account_management/#preferences [13]: /integrations/amazon_ec2/#ec2-automuting diff --git a/content/en/monitors/guide/integrate-monitors-with-statuspage.md b/content/en/monitors/guide/integrate-monitors-with-statuspage.md index d6cf4892660..36c54931dad 100644 --- a/content/en/monitors/guide/integrate-monitors-with-statuspage.md +++ b/content/en/monitors/guide/integrate-monitors-with-statuspage.md @@ -59,7 +59,7 @@ To create a [metric monitor][8] that triggers on Statuspage alerts: [1]: https://www.atlassian.com/software/statuspage [2]: /integrations/statuspage -[3]: /service_management/events/explorer/ +[3]: /events/explorer/ [4]: https://app.datadoghq.com/integrations [5]: https://app.datadoghq.com/event/explorer [6]: /dashboards/guide/custom_time_frames/ diff --git a/content/en/monitors/notify/_index.md b/content/en/monitors/notify/_index.md index c6849a95da9..4dcca83e01e 100644 --- a/content/en/monitors/notify/_index.md +++ b/content/en/monitors/notify/_index.md @@ -217,7 +217,7 @@ Message variables auto-populate with a randomly selected group based on the scop {{< partial name="whats-next/whats-next.html" >}} [1]: /monitors/configuration -[2]: /service_management/case_management/create_case/#automatic-case-creation +[2]: /incident_response/case_management/create_case/#automatic-case-creation [3]: /monitors/notify/variables/?tabs=is_alert#attribute-and-tag-variables [4]: http://daringfireball.net/projects/markdown/syntax [5]: /monitors/notify/variables/ @@ -228,8 +228,8 @@ Message variables auto-populate with a randomly selected group based on the scop [10]: /service_management/workflows/trigger/#add-the-workflow-to-your-monitor [11]: /service_management/workflows/build/ [12]: https://app.datadoghq.com/incidents/settings?section=global-settings -[13]: /service_management/incident_management/incident_settings/property_fields -[14]: /service_management/incident_management/notification +[13]: /incident_response/incident_management/incident_settings/property_fields +[14]: /incident_response/incident_management/notification [15]: /monitors/notify/variables/?tab=is_renotify#examples [16]: /monitors/settings/#tag-policies [17]: /account_management/teams/ diff --git a/content/en/monitors/status/events.md b/content/en/monitors/status/events.md index 0626f8e17ee..781d2cd41fc 100644 --- a/content/en/monitors/status/events.md +++ b/content/en/monitors/status/events.md @@ -65,8 +65,8 @@ For each event, access troubleshooting information to help responders quickly un {{< partial name="whats-next/whats-next.html" >}} [1]: /monitors/downtimes/?tab=bymonitorname -[2]: /service_management/incident_management/ -[3]: /service_management/case_management/ +[2]: /incident_response/incident_management/ +[3]: /incident_response/case_management/ [4]: /service_management/workflows/trigger/#trigger-a-workflow-from-a-monitor [5]: /monitors/status/status_page/#header [6]: /change_tracking diff --git a/content/en/monitors/status/status_legacy.md b/content/en/monitors/status/status_legacy.md index 2c9261f014e..1bb326d9fdd 100644 --- a/content/en/monitors/status/status_legacy.md +++ b/content/en/monitors/status/status_legacy.md @@ -176,7 +176,7 @@ You can obtain a JSON export of any monitor from the monitor's status page. Clic [1]: /monitors/configuration/ [2]: /monitors/downtimes/ -[3]: /service_management/incident_management/#from-a-monitor +[3]: /incident_response/incident_management/#from-a-monitor [4]: /monitors/types/ [5]: /api/v1/monitors/ [6]: /dashboards/querying/ diff --git a/content/en/monitors/types/event.md b/content/en/monitors/types/event.md index 150cc6b51ca..15e052919d5 100644 --- a/content/en/monitors/types/event.md +++ b/content/en/monitors/types/event.md @@ -5,7 +5,7 @@ aliases : - /monitors/monitor_types/event - /monitors/create/types/event/ further_reading: -- link: "/service_management/events/" +- link: "/events/" tag: "Documentation" text: "Event Management Overview" - link: "/monitors/notify/" @@ -104,7 +104,7 @@ Configure the alert grouping strategy: {{< partial name="whats-next/whats-next.html" >}} [1]: https://app.datadoghq.com/monitors/create/event -[2]: /service_management/events/explorer/searching +[2]: /events/explorer/searching [3]: /help/ [4]: /monitors/configuration/#advanced-alert-conditions [5]: /monitors/notify/ diff --git a/content/en/monitors/types/slo.md b/content/en/monitors/types/slo.md index 3551e113c68..2161f603349 100644 --- a/content/en/monitors/types/slo.md +++ b/content/en/monitors/types/slo.md @@ -4,10 +4,10 @@ description: "Create SLO alerts to monitor error budget consumption and burn rat aliases : - /monitors/create/types/slo/ further_reading: -- link: "/service_management/service_level_objectives/burn_rate" +- link: "/service_level_objectives/burn_rate" tag: "Documentation" text: "Burn Rate Alerts" -- link: "/service_management/service_level_objectives/error_budget" +- link: "/service_level_objectives/error_budget" tag: "Documentation" text: "Error Budget Alerts" --- @@ -53,9 +53,9 @@ In addition to the [standard template variables][6] available across all monitor {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/service_level_objectives/ +[1]: /service_level_objectives/ [2]: https://app.datadoghq.com/monitors/create/slo -[3]: /service_management/service_level_objectives/error_budget/ -[4]: /service_management/service_level_objectives/burn_rate/ +[3]: /service_level_objectives/error_budget/ +[4]: /service_level_objectives/burn_rate/ [5]: /monitors/notify/#overview [6]: /monitors/notify/variables/?tab=is_alert#template-variables diff --git a/content/en/network_monitoring/cloud_network_monitoring/network_health.md b/content/en/network_monitoring/cloud_network_monitoring/network_health.md index 9aa0b7d7a40..3360e42abdb 100644 --- a/content/en/network_monitoring/cloud_network_monitoring/network_health.md +++ b/content/en/network_monitoring/cloud_network_monitoring/network_health.md @@ -116,7 +116,7 @@ Use the filters at the top of the page to narrow the scope of displayed issues. [1]: /network_monitoring/cloud_network_monitoring/setup [2]: /actions/workflows/build/ -[3]: /service_management/case_management/create_case -[4]: /service_management/incident_management/declare/ +[3]: /incident_response/case_management/create_case +[4]: /incident_response/incident_management/declare/ [5]: /watchdog/insights [6]: /integrations/amazon-web-services/#resource-collection \ No newline at end of file diff --git a/content/en/observability_pipelines/monitoring_and_troubleshooting/monitoring_pipelines.md b/content/en/observability_pipelines/monitoring_and_troubleshooting/monitoring_pipelines.md index aa10f96e37f..7a8fe90a788 100644 --- a/content/en/observability_pipelines/monitoring_and_troubleshooting/monitoring_pipelines.md +++ b/content/en/observability_pipelines/monitoring_and_troubleshooting/monitoring_pipelines.md @@ -69,7 +69,7 @@ To see available out-of-the-box monitors: {{< partial name="whats-next/whats-next.html" >}} [1]: https://app.datadoghq.com//observability-pipelines/ -[2]: /service_management/incident_management/ +[2]: /incident_response/incident_management/ [3]: /monitors/types/metric/ [4]: /notebooks/ [5]: /observability_pipelines/monitoring_and_troubleshooting/metrics/ diff --git a/content/en/partners/getting_started/data-intake.md b/content/en/partners/getting_started/data-intake.md index 33ec60affb8..c2b5598c069 100644 --- a/content/en/partners/getting_started/data-intake.md +++ b/content/en/partners/getting_started/data-intake.md @@ -182,7 +182,7 @@ Now that you have data flowing into Datadog, it's time to focus on [delivering v [11]: /api/latest/events [12]: /api/latest/tracing/ [13]: /developers/custom_checks/ -[14]: /service_management/events/guides/dogstatsd/ +[14]: /events/guides/dogstatsd/ [15]: /metrics/custom_metrics/ [16]: /developers/community/libraries/#api-and-dogstatsd-client-libraries [17]: /api/latest/ diff --git a/content/en/partners/getting_started/delivering-value.md b/content/en/partners/getting_started/delivering-value.md index 7813ed28c54..aa5b12a462c 100644 --- a/content/en/partners/getting_started/delivering-value.md +++ b/content/en/partners/getting_started/delivering-value.md @@ -188,7 +188,7 @@ Find out how to monitor individual client and aggregate usage of the Datadog pla [43]: /api/latest/embeddable-graphs/ [44]: /dashboards/guide/embeddable-graphs-with-template-variables/ [45]: https://www.datadoghq.com/blog/establishing-service-level-objectives/ -[46]: /service_management/service_level_objectives/guide/slo-checklist +[46]: /service_level_objectives/guide/slo-checklist [47]: https://www.datadoghq.com/blog/define-and-manage-slos/ [48]: https://www.datadoghq.com/blog/slo-monitoring-tracking/ [49]: /api/latest/service-level-objectives/ diff --git a/content/en/real_user_monitoring/platform/generate_metrics.md b/content/en/real_user_monitoring/platform/generate_metrics.md index 9c24a10fd05..0a0bb6af75f 100644 --- a/content/en/real_user_monitoring/platform/generate_metrics.md +++ b/content/en/real_user_monitoring/platform/generate_metrics.md @@ -122,5 +122,5 @@ You can use RUM-based custom metrics for the following actions: [12]: /dashboards/querying/#configuring-a-graph [13]: /monitors/types/anomaly/ [14]: /monitors/types/forecasts/ -[15]: /service_management/service_level_objectives/metric/ +[15]: /service_level_objectives/metric/ [16]: /real_user_monitoring/rum_without_limits/ diff --git a/content/en/reference_tables/_index.md b/content/en/reference_tables/_index.md index 78d9110a09b..cd3a3a3e5ee 100644 --- a/content/en/reference_tables/_index.md +++ b/content/en/reference_tables/_index.md @@ -15,7 +15,7 @@ further_reading: - link: "/sheets/#lookup" tag: "Documentation" text: "Sheets lookup" -- link: "/service_management/events/pipelines_and_processors/lookup_processor/" +- link: "/events/pipelines_and_processors/lookup_processor/" tag: "Documentation" text: "Lookup processor for Events" - link: "/cloud_cost_management/tag_pipelines/#map-multiple-tags" diff --git a/content/en/security/application_security/security_signals/_index.md b/content/en/security/application_security/security_signals/_index.md index 52c54bca284..8465f73f341 100644 --- a/content/en/security/application_security/security_signals/_index.md +++ b/content/en/security/application_security/security_signals/_index.md @@ -151,9 +151,9 @@ To see all of the saved views, click **Views** next to the **Signals Explorer** [1]: https://app.datadoghq.com/services?lens=Security [2]: https://app.datadoghq.com/security/appsec/signals?query=%40workflow.rule.type%3A%22Application%20Security%22&column=time&order=desc&viz=stream&start=1694726477747&end=1695331277747&paused=false -[4]: /service_management/incident_management/ +[4]: /incident_response/incident_management/ [5]: /service_management/workflows/ -[6]: /service_management/case_management/ +[6]: /incident_response/case_management/ [7]: https://app.datadoghq.com/security/appsec? [8]: /security/notifications/rules/ [9]: /account_management/rbac/permissions/#cloud-security-platform diff --git a/content/en/security/cloud_siem/triage_and_investigate/investigate_security_signals.md b/content/en/security/cloud_siem/triage_and_investigate/investigate_security_signals.md index 20062058504..5d8a6206fc7 100644 --- a/content/en/security/cloud_siem/triage_and_investigate/investigate_security_signals.md +++ b/content/en/security/cloud_siem/triage_and_investigate/investigate_security_signals.md @@ -210,8 +210,8 @@ You can also launch this query directly from the signal panel: [3]: /account_management/rbac/ [4]: /logs/explorer/saved_views/ [5]: https://app.datadoghq.com/security/siem/home -[6]: /service_management/case_management/ -[7]: /service_management/incident_management/ +[6]: /incident_response/case_management/ +[7]: /incident_response/incident_management/ [8]: /service_management/workflows/trigger/#trigger-a-workflow-from-a-security-signal [9]: /security/cloud_security_management/workflows/ [10]: /security/threat_intelligence diff --git a/content/en/security/sensitive_data_scanner/guide/investigate_sensitive_data_findings.md b/content/en/security/sensitive_data_scanner/guide/investigate_sensitive_data_findings.md index bb0e443f3d2..07763dd0c27 100644 --- a/content/en/security/sensitive_data_scanner/guide/investigate_sensitive_data_findings.md +++ b/content/en/security/sensitive_data_scanner/guide/investigate_sensitive_data_findings.md @@ -62,8 +62,8 @@ Additionally, you can also: {{< img src="sensitive_data_scanner/investigate_sensitive_data_issues/case_mgmt_02_01_2024.png" alt="The case page showing information about the security finding, the assignee and creator of the case, and a timeline of events" style="width:60%;">}} -[1]: /service_management/case_management/ -[2]: /service_management/incident_management/ +[1]: /incident_response/case_management/ +[2]: /incident_response/incident_management/ [3]: /account_management/audit_trail {{% /tab %}} diff --git a/content/en/security/threats/investigate_agent_events.md b/content/en/security/threats/investigate_agent_events.md index 345853a1510..77d55468653 100644 --- a/content/en/security/threats/investigate_agent_events.md +++ b/content/en/security/threats/investigate_agent_events.md @@ -66,7 +66,7 @@ To triage an event: [11]: /security/workload_protection/security_signals [12]: /security/default_rules/#cat-cloud-security-management [13]: https://app.datadoghq.com/security/agent-events -[14]: /service_management/events/explorer/ +[14]: /events/explorer/ [15]: /infrastructure/process/ [16]: /metrics/ [17]: https://app.datadoghq.com/process diff --git a/content/en/security/threats/security_signals.md b/content/en/security/threats/security_signals.md index 3c75a63100f..8f8ba465471 100644 --- a/content/en/security/threats/security_signals.md +++ b/content/en/security/threats/security_signals.md @@ -75,8 +75,8 @@ Use [Workflow Automation][8] to manually trigger a workflow for a security signa [2]: /account_management/audit_trail/events/#cloud-security-platform-events [3]: /account_management/rbac/permissions/#cloud-security-platform [4]: https://app.datadoghq.com/security/workload-protection/signals -[5]: /service_management/incident_management/ -[6]: /service_management/case_management/ +[5]: /incident_response/incident_management/ +[6]: /incident_response/case_management/ [7]: /security/cloud_security_management/workflows [8]: /service_management/workflows [9]: /security/workload_protection/ diff --git a/content/en/security/ticketing_integrations.md b/content/en/security/ticketing_integrations.md index 71595958096..37bea285d72 100644 --- a/content/en/security/ticketing_integrations.md +++ b/content/en/security/ticketing_integrations.md @@ -133,13 +133,13 @@ There are several case management facets under **Triage**, including: You can query attributes and create dashboards using these facets. -[1]: /service_management/case_management/ +[1]: /incident_response/case_management/ [2]: /integrations/jira/ -[3]: /service_management/case_management/notifications_integrations/#third-party-tickets +[3]: /incident_response/case_management/notifications_integrations/#third-party-tickets [4]: https://app.datadoghq.com/security/siem/signals?column=time&order=desc&viz=stream [5]: https://app.datadoghq.com/security/appsec/vm/library [6]: https://app.datadoghq.com/security/appsec/signals?query=%40workflow.rule.type%3A%22Application%20Security%22&viz=stream [7]: https://app.datadoghq.com/security/workload-protection/signals?query=%40workflow.rule.type%3A%22Workload%20Security%22 [8]: /integrations/jira/#configure-a-jira-webhook -[9]: /service_management/case_management/projects/ +[9]: /incident_response/case_management/projects/ [10]: /security/ticketing_integrations/#prerequisites diff --git a/content/en/security/workload_protection/investigate_agent_events.md b/content/en/security/workload_protection/investigate_agent_events.md index 42a18c53b1c..9310d6d46ad 100644 --- a/content/en/security/workload_protection/investigate_agent_events.md +++ b/content/en/security/workload_protection/investigate_agent_events.md @@ -64,7 +64,7 @@ To triage an event: [11]: /security/workload_protection/security_signals [12]: /security/default_rules/#cat-cloud-security-management [13]: https://app.datadoghq.com/security/agent-events -[14]: /service_management/events/explorer/ +[14]: /events/explorer/ [15]: /infrastructure/process/ [16]: /metrics/ [17]: https://app.datadoghq.com/process diff --git a/content/en/security/workload_protection/security_signals.md b/content/en/security/workload_protection/security_signals.md index 38626f302a0..9dfce4e43c0 100644 --- a/content/en/security/workload_protection/security_signals.md +++ b/content/en/security/workload_protection/security_signals.md @@ -77,8 +77,8 @@ Use [Workflow Automation][8] to manually trigger a workflow for a security signa [2]: /account_management/audit_trail/events/#cloud-security-platform-events [3]: /account_management/rbac/permissions/#cloud-security-platform [4]: https://app.datadoghq.com/security/workload-protection/signals -[5]: /service_management/incident_management/ -[6]: /service_management/case_management/ +[5]: /incident_response/incident_management/ +[6]: /incident_response/case_management/ [7]: /security/cloud_security_management/workflows [8]: /service_management/workflows [9]: /security/workload_protection/ diff --git a/content/en/service_management/service_level_objectives/_index.md b/content/en/service_level_objectives/_index.md similarity index 97% rename from content/en/service_management/service_level_objectives/_index.md rename to content/en/service_level_objectives/_index.md index 1934648777f..53f44dd659f 100644 --- a/content/en/service_management/service_level_objectives/_index.md +++ b/content/en/service_level_objectives/_index.md @@ -6,6 +6,7 @@ aliases: - /monitors/slos/ - /monitors/service_level_objectives/ - /service_management/service_level_objectives/ootb_dashboard +- /service_management/service_level_objectives/ further_reading: - link: "https://www.datadoghq.com/blog/slo-monitoring-tracking/" tag: "Blog" @@ -374,15 +375,15 @@ The SLO statuses are calculated based on the SLO type: {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/service_level_objectives/guide/slo_types_comparison/ +[1]: /service_level_objectives/guide/slo_types_comparison/ [2]: https://app.datadoghq.com/slo -[3]: /service_management/service_level_objectives/metric/ -[4]: /service_management/service_level_objectives/monitor/ -[5]: /service_management/service_level_objectives/time_slice/ +[3]: /service_level_objectives/metric/ +[4]: /service_level_objectives/monitor/ +[5]: /service_level_objectives/time_slice/ [6]: /monitors/types/metric/?tab=threshold#alert-grouping -[7]: /service_management/service_level_objectives/metric/#define-queries -[8]: /service_management/service_level_objectives/monitor/#set-your-slo-targets -[9]: /service_management/service_level_objectives/metric/#set-your-slo-targets +[7]: /service_level_objectives/metric/#define-queries +[8]: /service_level_objectives/monitor/#set-your-slo-targets +[9]: /service_level_objectives/metric/#set-your-slo-targets [10]: /account_management/rbac/ [11]: /account_management/rbac/permissions/#service-level-objectives/ [12]: /account_management/rbac/permissions/#monitors @@ -390,7 +391,7 @@ The SLO statuses are calculated based on the SLO type: [14]: /mobile [15]: https://apps.apple.com/app/datadog/id1391380318 [16]: https://play.google.com/store/apps/details?id=com.datadog.app -[17]: /service_management/service_level_objectives/#saved-views +[17]: /service_level_objectives/#saved-views [18]: /account_management/teams/#associate-resources-with-team-handles [19]: /api/latest/events/ [20]: /dashboards/guide/slo_data_source/ @@ -400,5 +401,5 @@ The SLO statuses are calculated based on the SLO type: [24]: https://icalendar.org/iCalendar-RFC-5545/3-8-5-3-recurrence-rule.html [25]: /api/latest/service-level-objective-corrections/ [26]: https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/slo_correction -[27]: /service_management/events/explorer/ +[27]: /events/explorer/ [28]: /monitors/types/event/ diff --git a/content/en/service_management/service_level_objectives/burn_rate.md b/content/en/service_level_objectives/burn_rate.md similarity index 98% rename from content/en/service_management/service_level_objectives/burn_rate.md rename to content/en/service_level_objectives/burn_rate.md index 0039ef3540c..158a2834561 100644 --- a/content/en/service_management/service_level_objectives/burn_rate.md +++ b/content/en/service_level_objectives/burn_rate.md @@ -3,6 +3,7 @@ title: Burn Rate Alerts description: "Use Monitors to alert off of the burn rate of an SLO" aliases: - /monitors/service_level_objectives/burn_rate/ +- /service_management/service_level_objectives/burn_rate/ further_reading: - link: "https://www.datadoghq.com/blog/burn-rate-is-better-error-rate/" tag: "Blog" @@ -169,12 +170,12 @@ resource "datadog_monitor" "metric-based-slo" { ``` -[1]: /service_management/service_level_objectives/metric/ -[2]: /service_management/service_level_objectives/monitor/ +[1]: /service_level_objectives/metric/ +[2]: /service_level_objectives/monitor/ [3]: https://sre.google/workbook/alerting-on-slos/ [4]: https://app.datadoghq.com/slo [5]: /api/v1/monitors/#create-a-monitor [6]: https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/monitor -[7]: /service_management/service_level_objectives/time_slice +[7]: /service_level_objectives/time_slice [8]: /monitors/configuration/#set-alert-aggregation diff --git a/content/en/service_management/service_level_objectives/error_budget.md b/content/en/service_level_objectives/error_budget.md similarity index 92% rename from content/en/service_management/service_level_objectives/error_budget.md rename to content/en/service_level_objectives/error_budget.md index b930ee3cef7..84a4702c54e 100644 --- a/content/en/service_management/service_level_objectives/error_budget.md +++ b/content/en/service_level_objectives/error_budget.md @@ -3,8 +3,9 @@ title: Error Budget Alerts description: "Use Monitors to alert off of the error budget consumption of an SLO" aliases: - /monitors/service_level_objectives/error_budget/ +- /service_management/service_level_objectives/error_budget/ further_reading: -- link: "/service_management/service_level_objectives/" +- link: "/service_level_objectives/" tag: "Documentation" text: "Overview of Service Level Objectives" --- @@ -76,12 +77,12 @@ resource "datadog_monitor" "metric-based-slo" { {{< partial name="whats-next/whats-next.html" >}} -[1]: /service_management/service_level_objectives/metric/ -[2]: /service_management/service_level_objectives/monitor/ -[3]: /service_management/service_level_objectives/#key-terminology +[1]: /service_level_objectives/metric/ +[2]: /service_level_objectives/monitor/ +[3]: /service_level_objectives/#key-terminology [4]: https://app.datadoghq.com/slo [5]: /monitors/notify/ [6]: /api/v1/monitors/#create-a-monitor [7]: https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/monitor -[8]: /service_management/service_level_objectives/time_slice +[8]: /service_level_objectives/time_slice [9]: /monitors/configuration/#set-alert-aggregation diff --git a/content/en/service_management/service_level_objectives/guide/_index.md b/content/en/service_level_objectives/guide/_index.md similarity index 66% rename from content/en/service_management/service_level_objectives/guide/_index.md rename to content/en/service_level_objectives/guide/_index.md index 230aab1f285..8274c8dbcad 100644 --- a/content/en/service_management/service_level_objectives/guide/_index.md +++ b/content/en/service_level_objectives/guide/_index.md @@ -1,12 +1,14 @@ --- title: SLO Guides +aliases: +- /service_management/service_level_objectives/guide/ private: true disable_toc: true --- {{< whatsnext desc="General guides:">}} - {{< nextlink href="/service_management/service_level_objectives/guide/slo-checklist" >}}SLO Checklist{{< /nextlink >}} - {{< nextlink href="/service_management/service_level_objectives/guide/slo_types_comparison" >}}SLO Type Comparison{{< /nextlink >}} + {{< nextlink href="/service_level_objectives/guide/slo-checklist" >}}SLO Checklist{{< /nextlink >}} + {{< nextlink href="/service_level_objectives/guide/slo_types_comparison" >}}SLO Type Comparison{{< /nextlink >}} {{< /whatsnext >}} {{< whatsnext desc="Dashboard guides:">}} diff --git a/content/en/service_management/service_level_objectives/guide/slo-checklist.md b/content/en/service_level_objectives/guide/slo-checklist.md similarity index 95% rename from content/en/service_management/service_level_objectives/guide/slo-checklist.md rename to content/en/service_level_objectives/guide/slo-checklist.md index f9716df7880..421b459533b 100644 --- a/content/en/service_management/service_level_objectives/guide/slo-checklist.md +++ b/content/en/service_level_objectives/guide/slo-checklist.md @@ -3,6 +3,7 @@ title: SLO Checklist aliases: - /monitors/guide/slo-checklist/ +- /service_management/service_level_objectives/guide/slo-checklist/ further_reading: - link: 'https://www.datadoghq.com/blog/slo-monitoring-tracking/' tag: 'Blog' @@ -10,7 +11,7 @@ further_reading: - link: 'https://learn.datadoghq.com/courses/intro-to-slo' tag: 'Learning Center' text: 'Introduction to Service Level Objectives' -- link: "/service_management/service_level_objectives/guide/slo_types_comparison/" +- link: "/service_level_objectives/guide/slo_types_comparison/" tag: "Documentation" text: "Comparison of Datadog SLO Types" - link: "https://www.datadoghq.com/blog/define-and-manage-slos/" @@ -129,5 +130,5 @@ _Example: the latency of all user requests should be less than 250 ms 99% of the [4]: /integrations [5]: /tracing/trace_pipeline/generate_metrics/ [6]: /logs/logs_to_metrics/ -[7]: /service_management/service_level_objectives/#searching-and-viewing-slos -[8]: /service_management/service_level_objectives/guide/slo_types_comparison \ No newline at end of file +[7]: /service_level_objectives/#searching-and-viewing-slos +[8]: /service_level_objectives/guide/slo_types_comparison \ No newline at end of file diff --git a/content/en/service_management/service_level_objectives/guide/slo_types_comparison.md b/content/en/service_level_objectives/guide/slo_types_comparison.md similarity index 96% rename from content/en/service_management/service_level_objectives/guide/slo_types_comparison.md rename to content/en/service_level_objectives/guide/slo_types_comparison.md index 99a5a562aaf..097aa058dde 100644 --- a/content/en/service_management/service_level_objectives/guide/slo_types_comparison.md +++ b/content/en/service_level_objectives/guide/slo_types_comparison.md @@ -1,17 +1,18 @@ --- title: SLO Type Comparison - +aliases: +- /service_management/service_level_objectives/guide/slo_types_comparison/ further_reading: -- link: "/service_management/service_level_objectives/" +- link: "/service_level_objectives/" tag: "Documentation" text: "Overview of Service Level Objectives" -- link: "/service_management/service_level_objectives/metric/" +- link: "/service_level_objectives/metric/" tag: "Documentation" text: "Metric-based SLOs" -- link: "/service_management/service_level_objectives/monitor/" +- link: "/service_level_objectives/monitor/" tag: "Documentation" text: "Monitor-based SLOs" -- link: "/service_management/service_level_objectives/time_slice/" +- link: "/service_level_objectives/time_slice/" tag: "Documentation" text: "Time Slice SLOs" - link: "https://www.datadoghq.com/blog/define-and-manage-slos/" @@ -61,7 +62,7 @@ When creating SLOs, you can choose from the following types: [4]: https://docs.datadoghq.com/service_management/service_level_objectives/#slo-widgets [5]: https://docs.datadoghq.com/dashboards/guide/slo_data_source/ [6]: https://docs.datadoghq.com/service_management/service_level_objectives/monitor/#missing-data -[7]: /service_management/service_level_objectives/time_slice/#uptime-calculations +[7]: /service_level_objectives/time_slice/#uptime-calculations [8]: https://docs.datadoghq.com/api/latest/service-level-objectives/ [9]: https://docs.datadoghq.com/dashboards/widgets/slo/ [10]: https://docs.datadoghq.com/dashboards/widgets/slo_list/ diff --git a/content/en/service_management/service_level_objectives/metric.md b/content/en/service_level_objectives/metric.md similarity index 97% rename from content/en/service_management/service_level_objectives/metric.md rename to content/en/service_level_objectives/metric.md index 9d36476e5ad..d38771be602 100644 --- a/content/en/service_management/service_level_objectives/metric.md +++ b/content/en/service_level_objectives/metric.md @@ -4,11 +4,12 @@ description: "Use metrics to define a Service Level Objective" aliases: - /monitors/service_level_objectives/event/ - /monitors/service_level_objectives/metric/ +- /service_management/service_level_objectives/metric/ further_reading: - link: "/metrics/" tag: "Documentation" text: "More information about metrics" -- link: "/service_management/service_level_objectives/" +- link: "/service_level_objectives/" tag: "Documentation" text: "SLO overview, configuration, and calculation" - link: "https://www.datadoghq.com/blog/define-and-manage-slos/" @@ -67,9 +68,9 @@ While the SLO remains above the target percentage, the SLO's status will be disp [1]: https://docs.datadoghq.com/tracing/generate_metrics/ [2]: https://docs.datadoghq.com/real_user_monitoring/platform/generate_metrics [3]: https://docs.datadoghq.com/logs/log_configuration/logs_to_metrics/#overview -[4]: /service_management/service_level_objectives +[4]: /service_level_objectives [5]: https://app.datadoghq.com/slo [6]: https://app.datadoghq.com/slo/new/metric [7]: /metrics/distributions/#threshold-queries -[8]: /service_management/service_level_objectives/monitor/ +[8]: /service_level_objectives/monitor/ [9]: https://docs.datadoghq.com/dashboards/querying/#advanced-graphing diff --git a/content/en/service_management/service_level_objectives/monitor.md b/content/en/service_level_objectives/monitor.md similarity index 98% rename from content/en/service_management/service_level_objectives/monitor.md rename to content/en/service_level_objectives/monitor.md index 27efa8fd5f4..b214af6dbf2 100644 --- a/content/en/service_management/service_level_objectives/monitor.md +++ b/content/en/service_level_objectives/monitor.md @@ -3,6 +3,7 @@ title: Monitor-based SLOs description: "Use Monitors to define the Service Level Objective" aliases: - /monitors/service_level_objectives/monitor/ +- /service_management/service_level_objectives/monitor/ further_reading: - link: "/monitors/" tag: "Documentation" @@ -129,7 +130,7 @@ If you pause a Synthetic test, the SLO removes the time period with missing data [1]: https://app.datadoghq.com/monitors/create [2]: https://app.datadoghq.com/slo -[3]: /service_management/service_level_objectives/metric/ +[3]: /service_level_objectives/metric/ [4]: /synthetics/api_tests/?tab=httptest#alert-conditions -[5]: /service_management/service_level_objectives/#slo-status-corrections +[5]: /service_level_objectives/#slo-status-corrections [6]: /monitors/configuration/#no-data diff --git a/content/en/service_management/service_level_objectives/time_slice.md b/content/en/service_level_objectives/time_slice.md similarity index 98% rename from content/en/service_management/service_level_objectives/time_slice.md rename to content/en/service_level_objectives/time_slice.md index 2cfe0c10267..d9393746ddd 100644 --- a/content/en/service_management/service_level_objectives/time_slice.md +++ b/content/en/service_level_objectives/time_slice.md @@ -1,7 +1,9 @@ --- title: Time Slice SLOs +aliases: +- /service_management/service_level_objectives/time_slice/ further_reading: -- link: "service_management/service_level_objectives/" +- link: "/service_level_objectives/" tag: "Documentation" text: "Overview of Service Level Objectives" - link: "https://www.datadoghq.com/blog/define-and-manage-slos/" @@ -18,7 +20,7 @@ further_reading: Time Slice SLOs allow you to measure reliability using a custom definition of uptime. You define uptime as a condition over a metric timeseries. For example, you can create a latency SLO by defining uptime as whenever p95 latency is less than 1 second. -Time Slice SLOs are a convenient alternative to Monitor-based SLOs. You can create an uptime SLO without going through a monitor, so you don't have to create and maintain both a monitor and an SLO. +Time Slice SLOs are a convenient alternative to Monitor-based SLOs. You can create an uptime SLO without going through a monitor, so you don't have to create and maintain both a monitor and an SLO. ## Create a Time Slice SLO @@ -31,7 +33,7 @@ You can create a Time Slice SLO through the following ways: {{< img src="service_management/service_level_objectives/time_slice/time-slice-creation.png" alt="Configuration options to create a Time Slice SLO" style="width:90%;" >}} -1. Navigate to [**Service Management > SLOs**][1]. +1. Navigate to [**SLOs**][1]. 2. Click **+ New SLO** to open up the Create SLO page. 3. Select **By Time Slices** to define your SLO measurement. 4. Define your uptime condition by choosing a metric query, comparator and threshold. For example, to define uptime as whenever p95 latency is less than 1s. Alternatively, you can [import the uptime from a monitor](#import-from-a-monitor). diff --git a/content/en/service_management/events/explorer/_index.md b/content/en/service_management/events/explorer/_index.md deleted file mode 100644 index f75a934c7f7..00000000000 --- a/content/en/service_management/events/explorer/_index.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Events Explorer -aliases: -- /events/stream/ -- /events/explorer/ -further_reading: -- link: "/api/latest/events/" - tag: "Documentation" - text: "Datadog Events API" -- link: "https://www.datadoghq.com/blog/datadog-events/" - tag: "Blog" - 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 >}} - -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. - -{{< whatsnext desc="Features of the Events Explorer:" >}} - {{< nextlink href="/service_management/events/explorer/searching" >}}Searching{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/navigate" >}}Navigate the Explorer{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/customization" >}}Customization{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/facets" >}}Facets{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/attributes" >}}Attributes{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/notifications" >}}Send notifications{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/analytics" >}}Analytics{{< /nextlink >}} - {{< nextlink href="/service_management/events/explorer/saved_views" >}}Saved views{{< /nextlink >}} -{{< /whatsnext >}} - -## Further reading - -{{< partial name="whats-next/whats-next.html" >}} diff --git a/content/en/service_management/on-call/guides/_index.md b/content/en/service_management/on-call/guides/_index.md deleted file mode 100644 index 2d19ea7680c..00000000000 --- a/content/en/service_management/on-call/guides/_index.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: On-Call Guides -private: false -disable_toc: true ---- - -{{< whatsnext desc="General guides:">}} - {{< nextlink href="/service_management/on-call/guides/configure-mobile-device-for-on-call" >}}Set up your mobile device for Datadog On-Call{{< /nextlink >}} - {{< nextlink href="/service_management/on-call/guides/migrating-from-your-current-providers" >}}Migrate from your current on-call provider{{< /nextlink >}} - {{< nextlink href="/service_management/on-call/guides/migrate-your-pagerduty-resources-to-on-call" >}}Migrate PagerDuty resources to Datadog On-Call{{< /nextlink >}} - {{< nextlink href="/service_management/on-call/guides/offboarding-teams-and-users" >}}Offboard teams and users from Datadog On-Call{{< /nextlink >}} -{{< /whatsnext >}} diff --git a/content/en/synthetics/explore/_index.md b/content/en/synthetics/explore/_index.md index 4f642f32a7f..c7e2f7df943 100644 --- a/content/en/synthetics/explore/_index.md +++ b/content/en/synthetics/explore/_index.md @@ -16,7 +16,7 @@ further_reading: - link: "/synthetics/explore/results_explorer" tag: "Documentation" text: "Learn about the Synthetic Monitoring & Testing Results Explorer" -- link: "/service_management/events/explorer" +- link: "/events/explorer" tag: "Documentation" text: "Learn about the Events Explorer" --- diff --git a/content/en/synthetics/mobile_app_testing/mobile_app_tests/results.md b/content/en/synthetics/mobile_app_testing/mobile_app_tests/results.md index 29d5fe6d246..dd18d4616ed 100644 --- a/content/en/synthetics/mobile_app_testing/mobile_app_tests/results.md +++ b/content/en/synthetics/mobile_app_testing/mobile_app_tests/results.md @@ -8,7 +8,7 @@ further_reading: - link: "/synthetics/mobile_app_testing/" tag: "Documentation" text: "Learn about Synthetic mobile tests" -- link: "/service_management/events/explorer" +- link: "/events/explorer" tag: "Documentation" text: "Learn about the Events Explorer" --- diff --git a/content/en/tests/developer_workflows.md b/content/en/tests/developer_workflows.md index 0aa70fe8701..9e68b79356c 100644 --- a/content/en/tests/developer_workflows.md +++ b/content/en/tests/developer_workflows.md @@ -16,7 +16,7 @@ further_reading: - link: "/integrations/guide/source-code-integration" tag: "Documentation" text: "Learn about the Source Code Integration" -- link: "/service_management/case_management" +- link: "/incident_response/case_management" tag: "Documentation" text: "Learn about Case Management" --- @@ -171,8 +171,8 @@ IDE plugins and extensions are required to view your test in your IDE. [4]: /integrations/github/ [5]: /continuous_integration/tests/ [6]: https://app.datadoghq.com/integrations/github -[7]: /service_management/case_management/settings/#jira -[8]: /service_management/case_management/view_and_manage#take-action +[7]: /incident_response/case_management/settings/#jira +[8]: /incident_response/case_management/view_and_manage#take-action [9]: https://app.datadoghq.com/cases [10]: /integrations/github/#link-a-repository-in-your-organization-or-personal-account [11]: https://app.datadoghq.com/ci/test-repositories diff --git a/content/en/tests/flaky_management/_index.md b/content/en/tests/flaky_management/_index.md index 65557b42937..c544eed7473 100644 --- a/content/en/tests/flaky_management/_index.md +++ b/content/en/tests/flaky_management/_index.md @@ -196,7 +196,7 @@ To use Flaky Tests Management features, you must use Datadog's native instrument [1]: https://app.datadoghq.com/ci/test/flaky [2]: https://app.datadoghq.com/source-code/repositories [3]: /tests/explorer -[4]: /service_management/case_management +[4]: /incident_response/case_management [5]: /integrations/slack/?tab=datadogforslack [6]: /tests/setup/dotnet/ [7]: /tests/setup/go/ diff --git a/content/en/tracing/services/service_page.md b/content/en/tracing/services/service_page.md index 4be2e6ff66c..6142cbc9919 100644 --- a/content/en/tracing/services/service_page.md +++ b/content/en/tracing/services/service_page.md @@ -272,8 +272,8 @@ Visualize the cost associate with your service's infrastructure used in the Cost [2]: /tracing/services/resource_page/ [3]: /monitors/types/apm/ [4]: /tracing/error_tracking/ -[5]: /service_management/service_level_objectives/ -[6]: /service_management/incident_management/ +[5]: /service_level_objectives/ +[6]: /incident_response/incident_management/ [7]: /watchdog/ [8]: /tracing/metrics/metrics_namespace/ [10]: /dashboards/ diff --git a/content/en/universal_service_monitoring/_index.md b/content/en/universal_service_monitoring/_index.md index fb26d713edf..effe8eb645d 100644 --- a/content/en/universal_service_monitoring/_index.md +++ b/content/en/universal_service_monitoring/_index.md @@ -81,5 +81,5 @@ After enabling Universal Service Monitoring, you can: [3]: /tracing/software_catalog/ [4]: /monitors/types/apm/?tab=apmmetrics [5]: /dashboards/ -[6]: /service_management/service_level_objectives/metric/ +[6]: /service_level_objectives/metric/ [7]: /universal_service_monitoring/setup/ \ No newline at end of file diff --git a/content/en/universal_service_monitoring/guide/using_usm_metrics.md b/content/en/universal_service_monitoring/guide/using_usm_metrics.md index c730bfb71c5..3c04bf0cfac 100644 --- a/content/en/universal_service_monitoring/guide/using_usm_metrics.md +++ b/content/en/universal_service_monitoring/guide/using_usm_metrics.md @@ -86,7 +86,7 @@ To create an SLO from the Software Catalog: Optionally, to create an SLO manually using USM metrics: -1. Navigate to [**Service Management > SLOs**][15] and click [**New SLO**][13]. +1. Navigate to [**SLOs**][15] and click [**New SLO**][13]. 2. Select **Metric Based** and create two queries in the **Good events (numerator)** section: * Query A: Enter a USM metric such as `universal.http.server`, filter to a specific service by adding primary `service` and `env` tags in the `from` field, and select `count` in the `as` field. @@ -120,7 +120,7 @@ For more information, see the [Dashboards documentation][16]. [1]: /universal_service_monitoring [2]: /tracing/software_catalog [3]: /tracing/services/deployment_tracking/ -[4]: /service_management/service_level_objectives +[4]: /service_level_objectives [5]: /tracing/guide/setting_primary_tags_to_scope/?tab=helm#add-a-second-primary-tag-in-datadog [6]: /tracing/metrics/metrics_namespace [7]: /tracing/guide/ddsketch_trace_metrics/ @@ -133,4 +133,4 @@ For more information, see the [Dashboards documentation][16]. [14]: /api/latest/service-level-objectives/ [15]: https://app.datadoghq.com/slo/manage [16]: /dashboards -[17]: /service_management/service_level_objectives/ +[17]: /service_level_objectives/ diff --git a/content/en/watchdog/faulty_deployment_detection.md b/content/en/watchdog/faulty_deployment_detection.md index 250dea2e273..5ae2b938d60 100644 --- a/content/en/watchdog/faulty_deployment_detection.md +++ b/content/en/watchdog/faulty_deployment_detection.md @@ -40,5 +40,5 @@ Watchdog attempts to determine if the new deployment is a plausible cause of the - The error rate in the new version was not significantly higher than in preceding versions. - This error pattern is common during deployments of the service, even when the new code version is not faulty. -[2]: /service_management/events/explorer +[2]: /events/explorer [3]: https://app.datadoghq.com/monitors/create