External directory reference
The area names below were checked against the official Datadog documentation directory on 2026-09-06. They are used only to organize research questions. This table makes no equivalence, integration, licensing or availability claim.
| Datadog docs area | HertzBeat current evidence boundary | Roadmap document |
|---|---|---|
| Applications / APM | Service RED and Trace investigation | Proposal |
| Observability Pipelines | Controlled OTLP intake | Proposal |
| Fleet Automation | Collector configuration and intake readiness | Proposal |
| Software Catalog | Service entities and existing associations | Proposal |
| Incident Response | Alert firing, recovery and notifications | Proposal |
| Workflow Automation | Read-only AI Gateway tools | Proposal |
| Data Observability | Database operational metrics | Proposal |
| Digital Experience | Website/API monitoring | Proposal |
| Software Delivery | Observed service-investigation evidence | Proposal |
| Cloud Cost Management | Utilization monitoring, not billing | Proposal |
| AI | Controlled AI investigation and model-service monitoring | Proposal |
| Security | Authorization and redaction boundaries | Proposal |
| Platform Capabilities | Shared assets and existing roles | Proposal |
| API / Integrations | Controlled queries and application guides | Proposal |
Open-source private deployment note
A similarly named area can require a different data model, authorization boundary and operational budget. HertzBeat's alpha remains a privately deployable application with the documented store and tool dependencies; the directory does not authorize external cloud resources or add a second permissions system. Resource identity and topology proposals remain separate investigations.
Use the roadmap index to read the non-goals and required evidence. Current features are described in the operator manuals, not inferred from another product's navigation.