SVP of Product, Datadog
Agents generate far more activity to record than people do.
That means keeping complete telemetry, including an audit trail of what agents did.
Agentic AI assistants such as Bits AI agents investigate across your logs, so gaps in history become gaps in answers.
Teams usually choose between retaining complete logs and keeping data where policy requires. Datadog BYOC queries the data in place, on a data foundation where AIStor implements the complete S3 API.
Agents, cloud services, serverless, forwarders and more send logs to Datadog BYOC.
The Observability Pipelines Worker and BYOC engine index and query your logs on Kubernetes.
Holds the indexed log data, read and written over the S3 API.
Log Explorer, dashboards, monitors and alerts send queries in and receive only results out.
Datadog owns the engine and the experience. AIStor owns the data foundation underneath. Together they keep every log in your environment and searchable in Datadog.
Agents, cloud services and forwarders send logs to Datadog’s BYOC deployment, which runs in your own environment.
Datadog BYOC writes to AIStor over the S3 API and searches the data in place, on high-performance storage you own.
Teams investigate in the Datadog UI they already use. Only query results travel to Datadog.