By Dan Ambrose
Published 18th October 2022
Your Datadog region is determined by the site you use to access your Datadog account, refer to the table below to find your region.
| Region | Site |
|---|---|
| EU1 | datadoghq.eu |
| US1 | datadoghq.com |
| US3 | us3.datadoghq.com |
| US5 | us5.datadoghq.com |
| US1-FED | ddog-gov.com |
Navigate to your organisation settings in Datadog, then select API keys via the UI or go to https://<your-Datadog-site>/organization-settings/api-keys.
Create an API key with a name of your choice. Your key will be accessible after creation.
Follow this link or navigate to the log sinks page in your team or user account settings and add a log sink.
Enter a recognisable name for the sink and select Datadog as the sink type.
Select your Datadog region and verify the auto-generated site is correct, matching the region table.
Enter your API key and choose project targets if required. You can select specific projects to forward logs from, and only containers running in the selected projects will have their logs forwarded.
Finally click add log sink to create your Datadog integration .
Before your log sink is created, Northflank tries to send a log line to your Datadog setup to verify the credentials are correct.
On the Datadog app, click on the logs section in the sidecar to bring up the Log Explorer. You should see the validating log sink credentials log line from Northflank.
Workload logs should start arriving in Datadog, segmented by project/nfType/pod-slug as they are produced. Find out more about the Datadog Log Explorer in the Datadog docs.
Clicking on a log line will show an expanded view, with more details on the log line’s origins.
If you want to modify your sink after creation, navigate to the log sink list and click on the sink to view its details.
You can update the project targets and sink data as well as pause/resume the sink.
Have questions or feedback? Contact us. We also have dedicated support plans for business customers available.