Skip to content

Commit e2cb6e9

Browse files
l0k0msl0k0ms
committed
adding info for EU
1 parent 6c6f208 commit e2cb6e9

File tree

1 file changed

+25
-22
lines changed

1 file changed

+25
-22
lines changed

‎content/en/logs/log_collection/_index.md

Lines changed: 25 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ Choose your environment below to get dedicated log collection instructions:
6262

6363
## Serverless Log collection
6464

65-
Datadog can collect logs from AWS Lambda.
65+
Datadog can collect logs from AWS Lambda.
6666

6767

6868
## Cloud Providers Log collection
@@ -167,37 +167,40 @@ Endpoints that can be used to send logs to Datadog:
167167
{{% tab "US Site" %}}
168168

169169

170-
| Endpoints for SSL encrypted connections | Port | Description |
171-
|-----------------------------------------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
172-
| `agent-intake.logs.datadoghq.com` | `10516` | Used by the Agent to send logs in protobuf format over an SSL-encrypted TCP connection. |
173-
| `agent-http-intake.logs.datadoghq.com` | `443` | Used by the Agent to send logs in protobuf format over HTTPS (useful in enterprise environments with web proxies that don't allow outbound TCP traffic). [See more information on set up here](https://docs.datadoghq.com/agent/logs/?tab=tailexistingfiles#send-logs-over-https). |
174-
| `intake.logs.datadoghq.com` | `10516` | Used by custom forwarders to send logs in raw, Syslog, or JSON format over an SSL-encrypted TCP connection. |
175-
| `lambda-intake.logs.datadoghq.com` | `10516` | Used by Lambda functions to send logs in raw, Syslog, or JSON format over an SSL-encrypted TCP connection. |
176-
| `lambda-http-intake.logs.datadoghq.com` | `443` | Used by Lambda functions to send logs in raw, Syslog, or JSON format over HTTPS. |
177-
| `functions-intake.logs.datadoghq.com` | `10516` | Used by Azure functions to send logs in raw, Syslog, or JSON format over an SSL-encrypted TCP connection. **Note**: This endpoint may be useful with other cloud providers. |
170+
| Endpoints for SSL encrypted connections | Port | Description |
171+
|-----------------------------------------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
172+
| `agent-intake.logs.datadoghq.com` | `10516` | Used by the Agent to send logs in protobuf format over an SSL-encrypted TCP connection. |
173+
| `agent-http-intake.logs.datadoghq.com` | `443` | Used by the Agent to send logs in protobuf format over HTTPS. See the [How to send logs over HTTP documentation][1]. |
174+
| `intake.logs.datadoghq.com` | `10516` | Used by custom forwarders to send logs in raw, Syslog, or JSON format over an SSL-encrypted TCP connection. |
175+
| `lambda-intake.logs.datadoghq.com` | `10516` | Used by Lambda functions to send logs in raw, Syslog, or JSON format over an SSL-encrypted TCP connection. |
176+
| `lambda-http-intake.logs.datadoghq.com` | `443` | Used by Lambda functions to send logs in raw, Syslog, or JSON format over HTTPS. |
177+
| `functions-intake.logs.datadoghq.com` | `10516` | Used by Azure functions to send logs in raw, Syslog, or JSON format over an SSL-encrypted TCP connection. **Note**: This endpoint may be useful with other cloud providers. |
178178

179179

180180
| Endpoint for unencrypted connections | Port | Description |
181181
|--------------------------------------|---------|----------------------------------------------------------------------------------------------------------|
182182
| `intake.logs.datadoghq.com` | `10514` | Used by custom forwarders to send logs in raw, Syslog, or JSON format over an unecrypted TCP connection. |
183183

184+
[1]: https://docs.datadoghq.com/agent/logs/?tab=tailexistingfiles#send-logs-over-https
184185
{{% /tab %}}
185186
{{% tab "EU Site" %}}
186187

187-
| Endpoints for SSL encrypted connections | Port | Description |
188-
|-----------------------------------------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
189-
| `agent-intake.logs.datadoghq.eu` | `443` | Used by the Agent to send logs in protobuf format over an SSL-encrypted TCP connection. |
190-
| `tcp-intake.logs.datadoghq.eu` | `443` | Used by custom forwarders to send logs in raw, Syslog, or JSON format over an SSL-encrypted TCP connection. |
191-
| `lambda-intake.logs.datadoghq.eu` | `443` | Used by Lambda functions to send logs in raw, Syslog, or JSON format over an SSL-encrypted TCP connection. |
192-
| `lambda-http-intake.logs.datadoghq.eu` | `443` | Used by Lambda functions to send logs in raw, Syslog, or JSON format over HTTPS. |
193-
| `functions-intake.logs.datadoghq.eu` | `443` | Used by Azure functions to send logs in raw, Syslog, or JSON format over an SSL-encrypted TCP connection. **Note**: This endpoint may be useful with other cloud providers. |
188+
| Endpoints for SSL encrypted connections | Port | Description |
189+
|-----------------------------------------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
190+
| `agent-intake.logs.datadoghq.eu` | `443` | Used by the Agent to send logs in protobuf format over an SSL-encrypted TCP connection. |
191+
| `agent-http-intake.logs.datadoghq.eu` | `443` | Used by the Agent to send logs in protobuf format over HTTPS. See the [How to send logs over HTTP documentation][1]. |
192+
| `tcp-intake.logs.datadoghq.eu` | `443` | Used by custom forwarders to send logs in raw, Syslog, or JSON format over an SSL-encrypted TCP connection. |
193+
| `lambda-intake.logs.datadoghq.eu` | `443` | Used by Lambda functions to send logs in raw, Syslog, or JSON format over an SSL-encrypted TCP connection. |
194+
| `lambda-http-intake.logs.datadoghq.eu` | `443` | Used by Lambda functions to send logs in raw, Syslog, or JSON format over HTTPS. |
195+
| `functions-intake.logs.datadoghq.eu` | `443` | Used by Azure functions to send logs in raw, Syslog, or JSON format over an SSL-encrypted TCP connection. **Note**: This endpoint may be useful with other cloud providers. |
194196

195197

196198
| Endpoint for unencrypted connections | Port | Description |
197199
|--------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------|
198200
| `tcp-intake.logs.datadoghq.eu` | `1883` | Used by custom forwarders to send logs in raw, Syslog, or JSON format format over an unecrypted TCP connection. |
199201

200202

203+
[1]: https://docs.datadoghq.com/agent/logs/?tab=tailexistingfiles#send-logs-over-https
201204
{{% /tab %}}
202205
{{< /tabs >}}
203206

@@ -208,13 +211,13 @@ To send logs over HTTPs, refer to the [Datadog Log HTTP API documentation][22].
208211

209212
Here are some key attributes you should pay attention to when setting up your project:
210213

211-
| Attribute | Description |
212-
|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
213-
| `host` | The name of the originating host as defined in metrics. We automatically retrieve corresponding host tags from the matching host in Datadog and apply them to your logs. The Agent sets this value automatically. |
214+
| Attribute | Description |
215+
|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
216+
| `host` | The name of the originating host as defined in metrics. We automatically retrieve corresponding host tags from the matching host in Datadog and apply them to your logs. The Agent sets this value automatically. |
214217
| `source` | This corresponds to the integration name: the technology from which the log originated. When it matches an integration name, Datadog automatically installs the corresponding parsers and facets. For example: `nginx`, `postgresql`, etc. |
215-
| `status` | This corresponds to the level/severity of a log. It is used to define [patterns][23] and has a dedicated layout in the Datadog Log UI.|
216-
| `service` | The name of the application or service generating the log events. It is used to switch from Logs to APM, so make sure you define the same value when you use both products. |
217-
| `message` | By default, Datadog ingests the value of the `message` attribute as the body of the log entry. That value is then highlighted and displayed in the Logstream, where it is indexed for full text search. |
218+
| `status` | This corresponds to the level/severity of a log. It is used to define [patterns][23] and has a dedicated layout in the Datadog Log UI. |
219+
| `service` | The name of the application or service generating the log events. It is used to switch from Logs to APM, so make sure you define the same value when you use both products. |
220+
| `message` | By default, Datadog ingests the value of the `message` attribute as the body of the log entry. That value is then highlighted and displayed in the Logstream, where it is indexed for full text search. |
218221

219222
Your logs are collected and centralized into the [Log Explorer][24] view. You can also search, enrich, and alert on your logs.
220223

0 commit comments

Comments
 (0)