Skip to content

Commit f419eab

Browse files
eschabelleschabell
authored
Merge pull request #1900 from eschabell/erics-c-and-d-outputs-yaml
Added YAML examples for the output plugins listed in description. Fixes #1899.
2 parents bb409fa + 0e9af42 commit f419eab

File tree

4 files changed

+139
-68
lines changed

4 files changed

+139
-68
lines changed

‎pipeline/outputs/counter.md

Lines changed: 30 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -14,41 +14,53 @@ You can run the plugin from the command line or through the configuration file:
1414

1515
From the command line you can let Fluent Bit count up a data with the following options:
1616

17-
```bash
17+
```shell
1818
fluent-bit -i cpu -o counter
1919
```
2020

2121
### Configuration File
2222

23-
In your main configuration file append the following Input & Output sections:
23+
In your main configuration file append the following:
2424

25-
```python
25+
{% tabs %}
26+
{% tab title="fluent-bit.yaml" %}
27+
28+
```yaml
29+
pipeline:
30+
inputs:
31+
- name: cpu
32+
tag: cpu
33+
34+
outputs:
35+
- name: counter
36+
match: '*'
37+
```
38+
39+
{% endtab %}
40+
{% tab title="fluent-bit.conf" %}
41+
42+
```text
2643
[INPUT]
27-
Name cpu
28-
Tag cpu
44+
Name cpu
45+
Tag cpu
2946

3047
[OUTPUT]
31-
Name counter
32-
Match *
48+
Name counter
49+
Match *
3350
```
3451

52+
{% endtab %}
53+
{% endtabs %}
54+
3555
## Testing
3656

3757
Once Fluent Bit is running, you will see the reports in the output interface similar to this:
3858

39-
```bash
40-
$ bin/fluent-bit -i cpu -o counter -f 1
41-
Fluent Bit v1.x.x
42-
* Copyright (C) 2019-2020 The Fluent Bit Authors
43-
* Copyright (C) 2015-2018 Treasure Data
44-
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
45-
* https://fluentbit.io
46-
47-
[2017/07/19 11:19:02] [ info] [engine] started
59+
```shell
60+
...
4861
1500484743,1 (total = 1)
4962
1500484744,1 (total = 2)
5063
1500484745,1 (total = 3)
5164
1500484746,1 (total = 4)
5265
1500484747,1 (total = 5)
53-
```
54-
66+
```

‎pipeline/outputs/dash0.md

Lines changed: 26 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -27,35 +27,39 @@ For more details about the properties available and general configuration, see [
2727
To get started with sending logs to Dash0:
2828

2929
1. Get an [Auth Token](https://www.dash0.com/documentation/dash0/key-concepts/auth-tokens) from **Settings** > **Auth Tokens**.
30-
1. In your main Fluent Bit configuration file, append the following `Output` section:
30+
1. In your main Fluent Bit configuration file append the following:
3131

3232
{% tabs %}
33-
{% tab title="fluent-bit.conf" %}
34-
```text
35-
[OUTPUT]
36-
Name opentelemetry
37-
Match *
38-
Host ingress.eu-west-1.aws.dash0.com
39-
Port 443
40-
Header Authorization Bearer {your-Auth-token-here}
41-
Metrics_uri /v1/metrics
42-
Logs_uri /v1/logs
43-
Traces_uri /v1/traces
33+
{% tab title="fluent-bit.yaml" %}
34+
35+
```yaml
36+
pipeline:
37+
38+
outputs:
39+
- name: opentelemetry
40+
match: '*'
41+
host: ingress.eu-west-1.aws.dash0.com
42+
port: 443
43+
header: Authorization Bearer {your-Auth-token-here}
44+
metrics_uri: /v1/metrics
45+
logs_uri: /v1/logs
46+
traces_uri: /v1/traces
4447
```
4548
{% endtab %}
49+
{% tab title="fluent-bit.conf" %}
4650
47-
{% tab title="fluent-bit.yaml" %}
48-
```yaml
51+
```text
4952
[OUTPUT]
50-
Name: opentelemetry
51-
Match: *
52-
Host: ingress.eu-west-1.aws.dash0.com
53-
Port: 443
54-
Header: Authorization Bearer {your-Auth-token-here}
55-
Metrics_uri: /v1/metrics
56-
Logs_uri: /v1/logs
57-
Traces_uri: /v1/traces
53+
Name opentelemetry
54+
Match *
55+
Host ingress.eu-west-1.aws.dash0.com
56+
Port 443
57+
Header Authorization Bearer {your-Auth-token-here}
58+
Metrics_uri /v1/metrics
59+
Logs_uri /v1/logs
60+
Traces_uri /v1/traces
5861
```
62+
5963
{% endtab %}
6064
{% endtabs %}
6165

‎pipeline/outputs/datadog.md

Lines changed: 36 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -33,22 +33,47 @@ 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
3653
```
54+
55+
{% endtab %}
56+
{% tab title="fluent-bit.conf" %}
57+
58+
```text
3759
[OUTPUT]
38-
Name datadog
39-
Match *
40-
Host http-intake.logs.datadoghq.com
41-
TLS on
42-
compress gzip
43-
apikey <my-datadog-api-key>
44-
dd_service <my-app-service>
45-
dd_source <my-app-source>
46-
dd_tags team:logs,foo:bar
47-
dd_hostname myhost
60+
Name datadog
61+
Match *
62+
Host http-intake.logs.datadoghq.com
63+
TLS on
64+
compress gzip
65+
apikey <my-datadog-api-key>
66+
dd_service <my-app-service>
67+
dd_source <my-app-source>
68+
dd_tags team:logs,foo:bar
69+
dd_hostname myhost
4870
```
4971

72+
{% endtab %}
73+
{% endtabs %}
74+
5075
## Troubleshooting
5176

5277
### 403 Forbidden
5378

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).
79+
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).

‎pipeline/outputs/dynatrace.md

Lines changed: 47 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -32,23 +32,53 @@ To get started with sending logs to Dynatrace:
3232
token with the `logs.ingest` (Ingest Logs) scope.
3333
1. Determine your Dynatrace
3434
[environment ID](https://docs.dynatrace.com/docs/shortlink/monitoring-environment#environment-id).
35-
1. In your main Fluent Bit configuration file, append the following `Output` section:
36-
37-
```text
38-
[OUTPUT]
39-
name http
40-
match *
41-
header Content-Type application/json; charset=utf-8
42-
header Authorization Api-Token {your-API-token-here}
43-
allow_duplicated_headers false
44-
host {your-environment-id}.live.dynatrace.com
45-
Port 443
46-
URI /api/v2/logs/ingest
47-
Format json
48-
json_date_format iso8601
49-
json_date_key timestamp
50-
tls On
51-
tls.verify On
35+
1. In your main Fluent Bit configuration file, append the following `Output` section:
36+
37+
{% tabs %}
38+
{% tab title="fluent-bit.yaml" %}
39+
40+
```yaml
41+
pipeline:
42+
43+
outputs:
44+
- name: http
45+
match: '*'
46+
header:
47+
- 'Content-Type application/json; charset=utf-8'
48+
- 'Authorization Api-Token {your-API-token-here}'
49+
allow_duplicated_headers: false
50+
host: {your-environment-id}.live.dynatrace.com
51+
port: 443
52+
uri: /api/v2/logs/ingest
53+
format: json
54+
json_date_format: iso8601
55+
json_date_key: timestamp
56+
tls: on
57+
tls.verify: on
58+
```
59+
60+
{% endtab %}
61+
{% tab title="fluent-bit.conf" %}
62+
63+
```text
64+
[OUTPUT]
65+
name http
66+
match *
67+
header Content-Type application/json; charset=utf-8
68+
header Authorization Api-Token {your-API-token-here}
69+
allow_duplicated_headers false
70+
host {your-environment-id}.live.dynatrace.com
71+
Port 443
72+
URI /api/v2/logs/ingest
73+
Format json
74+
json_date_format iso8601
75+
json_date_key timestamp
76+
tls On
77+
tls.verify On
78+
```
79+
80+
{% endtab %}
81+
{% endtabs %}
5282

5383
## References
5484

0 commit comments

Comments
 (0)