In addition to accessing service logs in the console,
you can configure DoubleCloud to export them to external log management providers,
such as Datadog or an S3-compatible storage solution.
With log export, you can:
Centrally collect and process logs from DoubleCloud and other services you use.
Integrate logs from DoubleCloud with the rest of your observability infrastructure.
Provide standardized logs to your teams.
Store docs for longer than the retention period specified in your cluster or transfer configuration.
Datadog site: URL of the Datadog site.
Make sure to select the correct URL as Datadog sites are independent
and data isn't shared across them by default.
Amazon S3 or S3-compatible endpoint
DoubleCloud can export logs to both Amazon S3 and other S3-compatible storage solutions.
Bucket: Name of the S3 bucket to export logs to.
Folder name: Folder where logs will be exported.
Can include the date as a template variable in the Go date format, such as 2006/01/02/some_folder.
Access key ID.
Secret access key.
Region: Region where the bucket is located.
Endpoint: Endpoint of the S3-compatible service. Leave blank if you're using AWS.
Allow connections without SSL:
Select if you're connecting to an S3-compatible service that doesn't use SSL/TLS.
Skip verifying SSL certificate: Select if the bucket allows self-signed certificates.
Coralogix
Domain: Coralogix domain. Make sure to specify the
correct site
for your team hostname.
API key: API key of the Datadog-compatible service.
Endpoint: Endpoint of the Datadog-compatible service.
Click Save.
In the new dialog window, select sources—the clusters and transfers whose logs you want to export.
You can skip this step and select sources later.
Tip
If you're looking to export logs from one DoubleCloud project to several destinations,
configure export to Datadog or S3 and then forward logs to several destinations from there.