--- title: Bits Detection description: >- Learn how Bits Detection autonomously identifies critical services and manages monitor coverage as your system evolves. breadcrumbs: Docs > Bits AI > Bits Detection --- # Bits Detection {% callout %} # Important note for users on the following Datadog sites: app.ddog-gov.com, us2.ddog-gov.com {% alert level="danger" %} This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site.md). ({% placeholder "user-datadog-site-name" /%}). {% /alert %} {% /callout %} {% callout %} # Important note for users on the following Datadog sites: app.datadoghq.com, us3.datadoghq.com, us5.datadoghq.com, app.datadoghq.eu, ap1.datadoghq.com, ap2.datadoghq.com {% callout %} Bits Detection is in Preview. Contact your Datadog representative to request access. {% /callout %} {% /callout %} ## Overview{% #overview %} Monitoring coverage drifts over time. As engineers add endpoints, move dependencies, and change user flows, monitors keep reflecting the system as it was. A service can appear healthy at the top level while one critical path is failing. Bits Detection identifies which endpoints need coverage, sets detection logic from observed production behavior, and keeps coverage current without your team manually creating, tuning, and maintaining every monitor. When Bits Detection flags an issue, it points to the affected endpoint and related telemetry as the starting point for triage. It is the first step in the Bits AI workflow, which continues through investigation with [Bits Investigation](https://docs.datadoghq.com/bits_ai/bits_investigation.md) to root cause analysis and remediation. ## Enable Bits Detection{% #enable-bits-detection %} {% alert level="danger" %} Bits Detection is in Preview. Contact your Datadog representative to request access. {% /alert %} After you enable Bits Detection, it initializes monitoring for the 100 most critical services in your environment, based on service telemetry, dependencies, ownership metadata, recent changes, and user impact signals. Coverage is supported for APM-instrumented HTTP and gRPC services, prioritizing monitoring at the edge of your application. To request coverage for additional resource types, contact [Datadog Support](https://docs.datadoghq.com/help). Your team's existing monitors stay in place. Bits Detection works alongside them, adding adaptive coverage for the parts of your system that change too quickly to model by hand. To enable Bits Detection for additional services: 1. In Datadog, go to [APM > Services](https://www.app.datadoghq.com/apm/services) and select a service. 1. Open the service's monitoring overview from the monitor status bar or the Bits Detection card. 1. Follow the prompt to enable Bits Detection monitoring for the service. 1. Review the managed coverage after initialization completes. You receive an email when your new health posture is ready. ## Use Bits Detection{% #use-bits-detection %} Bits Detection manages monitoring in three stages: - **Identify critical resources**: Bits Detection evaluates supported services and resources to determine which endpoints, dependencies, or flows are likely to be important to your users and business. - **Detect meaningful degradations**: Bits Detection creates and tunes managed monitors for critical resources. - **Adapt as services change**: Bits Detection keeps monitoring aligned with production by reassessing resource criticality, monitoring coverage, and alerting behavior as your services evolve. Use the sections below to review coverage, configure alert routing, and provide feedback to help Bits adapt over time. ### Review Bits Detection monitoring{% #review-bits-detection-monitoring %} Use the Service Page or Monitor List to review how Bits Detection is monitoring your system. **Service Page** To open the Bits Detection view for a service, go to [APM > Services](https://www.app.datadoghq.com/apm/services), select a service, and open the monitoring overview from the monitor status bar or the Bits Detection card. {% image source="https://docs.dd-static.net/images/bits_ai/bits_detection/service_page_bits_detection_card.9c8c30ec018b5b532ecc4f0b4b0fb1a7.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/bits_ai/bits_detection/service_page_bits_detection_card.9c8c30ec018b5b532ecc4f0b4b0fb1a7.png?auto=format&fit=max&w=850&dpr=2 2x" alt="The Bits Detection card on the APM Services page showing monitoring status and critical endpoints for a service." /%} The Service Page shows Bits Detection monitors for the service, including their current status and alerting history, alongside the endpoints Bits considers critical. Bits prioritizes endpoints most likely to affect customers directly—such as checkout, signup, or authentication paths—and each endpoint includes a criticality justification explaining why it was selected. From the Service Page, you can: - Review Bits Detection health status for the service. - Open an active alert. - View details for a managed detection type. - Review the critical endpoints covered by Bits Detection. - Mark an endpoint as not critical. - Manage alert notification rules. **Monitor List** To view Bits Detection monitors, go to [Monitors > List](https://app.datadoghq.com/monitors/manage?bits_monitors=true) and select the Bits Managed filter. The summary banner shows the number of managed monitors in each status. Expand a service row to view its managed monitors. {% image source="https://docs.dd-static.net/images/bits_ai/bits_detection/monitor_list_bits_managed.33e79e05f6abd643a8b5ba23250fd530.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/bits_ai/bits_detection/monitor_list_bits_managed.33e79e05f6abd643a8b5ba23250fd530.png?auto=format&fit=max&w=850&dpr=2 2x" alt="The Monitor List filtered to Bits Managed monitors, showing services grouped by managed monitor status." /%} The Monitor List groups Bits Detection monitors by service. For each service, you can review the status, priority, monitor name, and tags for each managed monitor. Bits Detection monitors are labeled with a sparkle icon so you can distinguish them from monitors your teams create and maintain. ### Manage Bits Detection notifications{% #manage-bits-detection-notifications %} Bits Detection monitors are tuned to production behavior, not static thresholds. Use alert notification rules to route alerts to the right teams. To set up a rule, go to the [service monitoring overview](https://www.app.datadoghq.com/apm/services) and click Set Up Alert Notification Rules. 1. In Match notifications with specific tags, review the query. Datadog pre-fills the rule with tags for the selected service and Bits Detection-managed monitors. You can filter further. 1. In Choose routing conditions and recipients, select Manual Routing or Dynamic Routing. 1. Add the recipients that should receive matching monitor notifications. 1. Name the rule. 1. Define permissions for the rule. 1. Click Create Rule. The notification rule applies to monitors that match the tag query. The side panel shows how many monitors match the rule and lists examples of matching monitors. ### Help Bits learn{% #help-bits-learn %} Use feedback to tune Bits Detection for your environment. You can flag alerts as useful or noisy, and update which endpoints are considered critical from the Service Page. **Provide feedback on an alert** 1. Open the Bits Detection alert. 1. In the feedback prompt, click Yes if Bits should have alerted you, or click No, Because… if it should not have. 1. If you clicked No, Because…, select a reason. 1. Click Send Feedback. **Provide feedback on resource criticality** Bits Detection uses criticality to determine which resources should have managed monitoring coverage. From the [service monitoring overview](https://www.app.datadoghq.com/apm/services), click Mark as Not Critical next to an endpoint that should not have critical coverage, or Add a New Endpoint to mark one as critical. ## Further reading{% #further-reading %} - [Autonomously monitor for impactful degradations with Bits Detection](https://www.datadoghq.com/blog/bits-detection/)