Skip to content

Commit 5697311

Browse files
committed
Adding YAML exampels and sandardizing shell usage for Datadog output plugin. Part of issue #1899.
Signed-off-by: Eric D. Schabell <[email protected]>
1 parent d907719 commit 5697311

File tree

1 file changed

+27
-1
lines changed

1 file changed

+27
-1
lines changed

pipeline/outputs/datadog.md

Lines changed: 27 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,30 @@ Before you begin, you need a [Datadog account](https://app.datadoghq.com/signup)
3333

3434
Get started quickly with this configuration file:
3535

36+
{% tabs %}
37+
{% tab title="fluent-bit.yaml" %}
38+
39+
```yaml
40+
pipeline:
41+
42+
outputs:
43+
- name: datadog
44+
match: '*'
45+
host: http-intake.logs.datadoghq.com
46+
tls: on
47+
compress: gzip
48+
apikey: <my-datadog-api-key>
49+
dd_service: <my-app-service>
50+
dd_source: <my-app-source>
51+
dd_tags: team:logs,foo:bar
52+
dd_hostname: myhost
53+
3654
```
55+
56+
{% endtab %}
57+
{% tab title="fluent-bit.conf" %}
58+
59+
```text
3760
[OUTPUT]
3861
Name datadog
3962
Match *
@@ -47,8 +70,11 @@ Get started quickly with this configuration file:
4770
dd_hostname myhost
4871
```
4972

73+
{% endtab %}
74+
{% endtabs %}
75+
5076
## Troubleshooting
5177

5278
### 403 Forbidden
5379

54-
If you get a `403 Forbidden` error response, double check that you have a valid [Datadog API key](https://docs.datadoghq.com/account_management/api-app-keys/) and that you have [activated Datadog Logs Management](https://app.datadoghq.com/logs/activation).
80+
If you get a `403 Forbidden` error response, double check that you have a valid [Datadog API key](https://docs.datadoghq.com/account_management/api-app-keys/) and that you have [activated Datadog Logs Management](https://app.datadoghq.com/logs/activation).

0 commit comments

Comments
 (0)