Configure your Datadog account to forward all the logs ingested to a cloud storage system. Keeping your logs in a storage-optimized archive for longer periods of time enables you to meet compliance requirements, and to keep auditability for ad hoc investigations within budget. Once your logs are archived for the long term, you have access to them should you ever need to investigate something unexpected—or that might have happened a long time ago.
This guide shows you how to set up an archive for forwarding ingested logs to your own cloud-hosted storage bucket.
Note: only Datadog users with admin status can create, modify, or delete log archive configurations.
Go into your AWS console and create an S3 bucket to send your archives to. Be careful not to make your bucket publicly readable.
Next, grant Datadog permissions to write log archives to your S3 bucket with role delegation:
Set up the AWS integration for the AWS account that holds your S3 bucket. This involves creating a role that Datadog can use to integrate with AWS Cloudwatch.
Add the following two permission statements to the IAM policies of your Datadog role. Edit the bucket names and, if desired, specify the paths that contain your log archives. The GetObject and ListBucket permissions allow for Rehydrating from Archives. The PutObject permission is sufficient for uploading archives.
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "DatadogUploadAndRehydrateLogArchives",
"Effect": "Allow",
"Action": ["s3:PutObject", "s3:GetObject"],
"Resource": [
"arn:aws:s3:::<MY_BUCKET_NAME_1_/_MY_OPTIONAL_BUCKET_PATH_1>/*",
"arn:aws:s3:::<MY_BUCKET_NAME_2_/_MY_OPTIONAL_BUCKET_PATH_2>/*"
]
},
{
"Sid": "DatadogRehydrateLogArchivesListBucket",
"Effect": "Allow",
"Action": "s3:ListBucket",
"Resource": [
"arn:aws:s3:::<MY_BUCKET_NAME_1>",
"arn:aws:s3:::<MY_BUCKET_NAME_2>"
]
}
]
}Go to your Archives page in Datadog and select the Add a new archive option at the bottom. Only Datadog users with admin status can complete this and the following step.
Select the appropriate AWS account + role combination for your S3 bucket. Input your bucket name. Optionally input a prefix directory for all the content of your log archives. Save your archive, and you are finished.
To add server side encryption to your S3 log archives, go to the Properties tab in your S3 bucket and select Default Encryption. Select the AES-256 option and Save.
Next, grant your Datadog GCP Service Account sufficient permissions to write your archives to your bucket. If you’re creating a new Service Account, this can be done from the GCP Credentials page. If you’re updating an existing Service Account, this can be done from the GCP IAM Admin page). Add the roles under Storage called Storage Object Creator (for generating archives) and Storage Object Viewer (for rehydrating from archives).
Go to your Archives page in Datadog, and select the Add a new archive option at the bottom. Only Datadog users with admin status can complete this and the following step.
Select the GCS archive type, and the GCS Service Account that has permissions to write on your storage bucket. Input your bucket name. Optional: input a prefix directory for all the content of your log archives. Then save your archive.
Once your archive settings are successfully configured in your Datadog account, your processing pipelines begin to enrich all the logs that Datadog ingests. These logs are subsequently forwarded to your archive.
However, after creating or updating your archive configurations, it can take several minutes before the next archive upload is attempted, so you should check back on your storage bucket in 15 minutes to make sure the archives are successfully being uploaded from your Datadog account.
The log archives that Datadog forwards to your storage bucket are in compressed JSON format (.json.gz). Under whatever prefix you indicate (or / if there is none), the archives are stored in a directory structure that indicates on what date and at what time the archive files were generated, like so:
/my/bucket/prefix/dt=20180515/hour=14/archive_143201.1234.7dq1a9mnSya3bFotoErfxl.json.gz
This directory structure simplifies the process of querying your historical log archives based on their date.
Within the zipped JSON file, each event’s content is formatted as follows:
{
"_id": "123456789abcdefg",
"date": "2018-05-15T14:31:16.003Z",
"host": "i-12345abced6789efg",
"source": "source_name",
"service": "service_name",
"status": "status_level",
"message": " ... log message content ... ",
"attributes": { ... log attributes content ... }
}Note: Archives only include log content, which consists of the message, custom attributes, and reserved attributes of your log events. The log tags (metadata that connects your log data to related metrics and traces) are not included.
Admins can route specific logs to an archive by adding a query in the archive’s filter field. Logs enter the first archive whose filter they match on, so it is important to order your archives carefully.
For example, if you create a first archive filtered to the env:prod tag and a second archive without any filter (the equivalent of *), all your production logs would go to one storage bucket/path, and the rest would go to the other.
Logs enter the first archive whose filter they match on.
Next, learn how to access your archived log content from Datadog:
お役に立つドキュメント、リンクや記事:
*Logging without Limits is a trademark of Datadog, Inc.
On this page
