Confirm an archive is configured: Logs > Configuration > Archives should show an active archive pointing to an S3 bucket with the required IAM permissions (s3:GetObject, s3:ListBucket, s3:PutObject for the Datadog account)
Navigate to Logs > Configuration > Rehydrating from Archives and click New Historical View
Select the archive to rehydrate from, specify the start and end time window for the logs you need, and optionally add a query filter to rehydrate only matching logs rather than the full time window
Choose an index retention period for the rehydrated logs (they will be available in Log Explorer for this duration) and give the historical view a descriptive name
Click Rehydrate and monitor the progress bar; rehydration scans compressed log files in S3 and can take minutes to hours depending on the volume and the S3 storage class
Once complete, query the historical view in Log Explorer by selecting it from the index dropdown to search and analyze the restored logs
Known gotchas
If the archive uses S3 Glacier or S3 Glacier Deep Archive as a storage class, logs must be restored to S3 Standard-IA first via an S3 Lifecycle restore request before Datadog can rehydrate them; this adds hours or days to the process
Rehydrated logs count against your indexed log quota for the retention period you select; choose the shortest retention that meets your investigation needs to control cost
The IAM role used by Datadog to read the S3 archive must have permissions on the specific S3 key prefix where the archive stores data; prefix mismatches result in silent empty rehydration
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp