diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml index 899959f118f..55645746230 100644 --- a/config/_default/menus/main.en.yaml +++ b/config/_default/menus/main.en.yaml @@ -1779,86 +1779,91 @@ menu: parent: monitor_types identifier: monitor_types_database_monitoring weight: 410 + - name: Dataset + url: monitors/types/dataset/ + parent: monitor_types + identifier: monitor_types_dataset + weight: 411 - name: Error Tracking url: monitors/types/error_tracking/ parent: monitor_types identifier: monitor_types_error_tracking - weight: 411 + weight: 412 - name: Event url: monitors/types/event/ parent: monitor_types identifier: monitor_types_event - weight: 412 + weight: 413 - name: Forecast url: monitors/types/forecasts/ parent: monitor_types identifier: monitor_types_forecasts - weight: 413 + weight: 414 - name: Integration url: monitors/types/integration/ parent: monitor_types identifier: monitor_types_integration - weight: 414 + weight: 415 - name: Live Process url: monitors/types/process/ parent: monitor_types identifier: monitor_types_process - weight: 415 + weight: 416 - name: Logs url: monitors/types/log/ parent: monitor_types identifier: monitor_types_log - weight: 416 + weight: 417 - name: Network url: monitors/types/network/ parent: monitor_types identifier: monitor_types_network - weight: 417 + weight: 418 - name: Cloud Network Monitoring url: monitors/types/cloud_network_monitoring/ parent: monitor_types identifier: monitor_types_cnm - weight: 418 + weight: 419 - name: NetFlow url: monitors/types/netflow/ parent: monitor_types identifier: monitor_types_netflow - weight: 419 + weight: 420 - name: Outlier url: monitors/types/outlier/ parent: monitor_types identifier: monitor_types_outlier - weight: 420 + weight: 421 - name: Process Check url: monitors/types/process_check/ parent: monitor_types identifier: monitor_types_process_check - weight: 421 + weight: 422 - name: Real User Monitoring url: monitors/types/real_user_monitoring/ parent: monitor_types identifier: monitor_types_rum - weight: 422 + weight: 423 - name: Service Check url: monitors/types/service_check/ parent: monitor_types identifier: monitor_types_service_check - weight: 423 + weight: 424 - name: SLO Alerts url: monitors/types/slo/ parent: monitor_types identifier: monitor_types_slo - weight: 424 + weight: 425 - name: Synthetic Monitoring url: monitors/types/synthetic_monitoring/ parent: monitor_types identifier: monitor_types_syn - weight: 425 + weight: 426 - name: Watchdog url: monitors/types/watchdog/ parent: monitor_types identifier: monitor_types_watchdog - weight: 426 + weight: 427 - name: Notifications url: monitors/notify/ parent: alerting diff --git a/content/en/monitors/types/dataset.md b/content/en/monitors/types/dataset.md new file mode 100644 index 00000000000..3eb91773f90 --- /dev/null +++ b/content/en/monitors/types/dataset.md @@ -0,0 +1,71 @@ +--- +title: Dataset Monitor +description: "Alert on advanced log analysis with Dataset monitors that support querying multiple data sources, chaining data transformations, and running complex SQL queries." +further_reading: +- link: "/notebooks/advanced_analysis/" + tag: "Documentation" + text: "Notebooks Advanced Analysis" +- link: "/monitors/configuration/" + tag: "Documentation" + text: "Learn how to configure monitors" +- link: "/monitors/notify/" + tag: "Documentation" + text: "Configure your monitor notifications" +--- + +## Overview + +
Datasets that include Flex Logs are not supported.
+ +Dataset monitors enable you to alert on advanced log analysis by leveraging all Notebooks advanced analysis features. With Dataset monitors, you can: + +- Query multiple data sources +- Chain data transformations +- Run complex SQL queries +- Create sophisticated analysis workflows + +Dataset monitors offer full Notebook analysis features, letting you alert on complex data patterns not easily detected with standard monitors. + +## Monitor creation + +You can create a Dataset monitor in two ways: + +### From the Monitors page + +To create a [Dataset monitor][1] in Datadog, use the main navigation: **Monitors > New Monitor > Dataset**. + +### From a Notebook + +To create a Dataset monitor directly from a Notebook: + +1. Open a Notebook with an Analysis cell containing your desired query. +2. In the Analysis cell, click the dropdown arrow next to **Save to Dashboard**. +3. Select **Create monitor**. + +This allows you to seamlessly convert your exploratory analysis into an alerting monitor. + +## Define the query + +Dataset monitors use the same query interface as Notebook Analysis cells. + +1. **Select your dataset**: [To confirm] Select from available Notebook Analysis cells. +2. **Filter your dataset**: [To confirm] Filter your results by column. +3. **Preview results**: View the output of your query before setting alert conditions. + +{{< img src="/monitors/monitor_types/dataset/dataset_monitor_config.png" alt="Dataset monitor configuration example" style="width:100%;" >}} + +## Set alert conditions + +Configure monitors to trigger if the query value crosses a threshold, and customize advanced alert options for recovery thresholds and evaluation delays. For more information, see [Configure Monitors][2]. + +## Notifications + +For detailed instructions on alert messaging, see [Notifications][3]. + +## Further reading + +{{< partial name="whats-next/whats-next.html" >}} + +[1]: https://app.datadoghq.com/monitors/create/dataset +[2]: /monitors/configuration/ +[3]: /monitors/notify/ diff --git a/static/images/monitors/monitor_types/dataset/dataset_monitor_config.png b/static/images/monitors/monitor_types/dataset/dataset_monitor_config.png new file mode 100644 index 00000000000..bd1503b8bf8 Binary files /dev/null and b/static/images/monitors/monitor_types/dataset/dataset_monitor_config.png differ