You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding YAML examples, fixing standards for table layouts for output plugins form range N and O. Fixes#1926. (#1930)
* Adding YAML examples and fixing table layout. Part of isssue #1926.
Signed-off-by: Eric D. Schabell <[email protected]>
* Adding YAML examples to NULL output plugin doc. Part of isssue #1926.
Signed-off-by: Eric D. Schabell <[email protected]>
* Adding YAML examples and fixing table layout for Observe output plugin. Part of isssue #1926.
Signed-off-by: Eric D. Schabell <[email protected]>
* Adding back missing original OpenObserve output plugin doc, adding YAML examples, and fixing table layout. Part of isssue #1926.
Signed-off-by: Eric D. Schabell <[email protected]>
* Adding YAML examples and fixing table layouts for OpenSearch output plugin doc. Part of isssue #1926.
Signed-off-by: Eric D. Schabell <[email protected]>
* Adding YAML examples and fixing table layouts for OpenTelemetry output plugin doc. Part of isssue #1926.
Signed-off-by: Eric D. Schabell <[email protected]>
* Adding YAML examples and fixing table layouts for Oracle Log Analytics output plugin doc. Part of isssue #1926.
Signed-off-by: Eric D. Schabell <[email protected]>
---------
Signed-off-by: Eric D. Schabell <[email protected]>
<p>From a configuration perspective either an <code>api_key</code> or an <code>license_key</code> is
49
-
required. New Relic suggest to use primary the <code>api_key</code>.</p>
50
-
</th>
51
-
<th style="text-align:left"></th>
52
-
</tr>
53
-
</thead>
54
-
<tbody></tbody>
55
-
</table>
56
-
57
-
<table>
58
-
<thead>
59
-
<tr>
60
-
<th style="text-align:left">license_key</th>
61
-
<th style="text-align:left">
62
-
<p>Optional authentication parameter for data ingestion.
63
-
<br />
64
-
</p>
65
-
<p>Note that New Relic suggest to use the <code>api_key</code> instead. You
66
-
can read more about the License Key <a href="https://docs.newrelic.com/docs/accounts/install-new-relic/account-setup/license-key">here</a>.</p>
67
-
</th>
68
-
<th style="text-align:left"></th>
69
-
</tr>
70
-
</thead>
71
-
<tbody></tbody>
72
-
</table>
73
-
74
-
| compress | Set the compression mechanism for the payload. This option allows two values: `gzip`\(enabled by default\) or `false` to disable compression. | gzip |
75
-
| workers | The number of [workers](../../administration/multithreading.md#outputs) to perform flush operations for this output. |`0`|
76
-
| :--- | :--- | :--- |
77
-
78
-
79
-
The following configuration example, will emit a dummy example record and ingest it on New Relic. Copy and paste the following content in a file called `newrelic.conf`:
| base_uri | Full address of New Relic API end-point. By default the value points to the US end-point. If you want to use the EU end-point you can set this key to the following value:<br> - <ahref="https://log-api.eu.newrelic.com/log/v1">https://log-api.eu.newrelic.com/log/v1</a> | <ahref="https://log-api.newrelic.com/log/v1">https://log-api.newrelic.com/log/v1</a> |
16
+
| api_key | Your key for data ingestion. The API key is also called the ingestion key, you can get more details on how to generated in the official documentation <ahref="https://docs.newrelic.com/docs/apis/get-started/intro-apis/types-new-relic-api-keys#event-insert-key">here</a>. From a configuration perspective either an `api_key` or a `license_key` is required. New Relic suggests to use primarily the `api_key`. ||
17
+
| license_key | Optional authentication parameter for data ingestion. Note that New Relic suggest to use the `api_key` instead. You can read more about the License Key <ahref="https://docs.newrelic.com/docs/accounts/install-new-relic/account-setup/license-key">here</a>. ||
18
+
| compress | Set the compression mechanism for the payload. This option allows two values: `gzip`\(enabled by default\) or `false` to disable compression. | gzip |
19
+
| workers | The number of [workers](../../administration/multithreading.md#outputs) to perform flush operations for this output. | 0 |
20
+
21
+
The following configuration example, will emit a dummy example record and ingest it on New Relic. In your main configuration file append the following:
Copy file name to clipboardExpand all lines: pipeline/outputs/observe.md
+42-15Lines changed: 42 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,28 +2,53 @@
2
2
3
3
Observe employs the **http** output plugin, allowing you to flush your records [into Observe](https://docs.observeinc.com/en/latest/content/data-ingestion/forwarders/fluentbit.html).
4
4
5
-
For now the functionality is pretty basic and it issues a POST request with the data records in [MessagePack](http://msgpack.org) (or JSON) format.
5
+
For now the functionality is pretty basic, and it issues a POST request with the data records in [MessagePack](http://msgpack.org) (or JSON) format.
6
6
7
7
The following are the specific HTTP parameters to employ:
| host | IP address or hostname of Observe's data collection endpoint. $(OBSERVE_CUSTOMER) is your [Customer ID](https://docs.observeinc.com/en/latest/content/common-topics/HelpfulHints.html?highlight=customer%20id#customer-id)| OBSERVE_CUSTOMER.collect.observeinc.com |
14
-
| port | TCP port of to employ when sending to Observe | 443|
15
-
| tls | Specify to use tls | on|
16
-
| uri | Specify the HTTP URI for the Observe's data ingest | /v1/http/fluentbit|
17
-
| format | The data format to be used in the HTTP request body | msgpack|
18
-
| header | The specific header that provides the Observe token needed to authorize sending data [into a datastream](https://docs.observeinc.com/en/latest/content/data-ingestion/datastreams.html?highlight=ingest%20token#create-a-datastream).| Authorization Bearer ${OBSERVE_TOKEN} |
19
-
| header | The specific header to instructs Observe how to decode incoming payloads | X-Observe-Decoder fluent|
20
-
| compress | Set payload compression mechanism. Option available is 'gzip' | gzip|
21
-
| tls.ca_file |**For use with Windows**: provide path to root cert ||
22
-
| workers | The number of [workers](../../administration/multithreading.md#outputs) to perform flush operations for this output. |`0`|
| host | IP address or hostname of Observe's data collection endpoint. $(OBSERVE_CUSTOMER) is your [Customer ID](https://docs.observeinc.com/en/latest/content/common-topics/HelpfulHints.html?highlight=customer%20id#customer-id)| OBSERVE_CUSTOMER.collect.observeinc.com|
14
+
| port | TCP port of to employ when sending to Observe | 443|
15
+
| tls | Specify to use tls | on|
16
+
| uri | Specify the HTTP URI for the Observe's data ingest | /v1/http/fluentbit|
17
+
| format | The data format to be used in the HTTP request body | msgpack|
18
+
| header | The specific header that provides the Observe token needed to authorize sending data [into a data stream](https://docs.observeinc.com/en/latest/content/data-ingestion/datastreams.html?highlight=ingest%20token#create-a-datastream). | Authorization Bearer ${OBSERVE_TOKEN} |
19
+
| header | The specific header to instructs Observe how to decode incoming payloads | X-Observe-Decoder fluent|
20
+
| compress | Set payload compression mechanism. Option available is 'gzip' | gzip|
21
+
| tls.ca_file |**For use with Windows**: provide path to root cert ||
22
+
| workers | The number of [workers](../../administration/multithreading.md#outputs) to perform flush operations for this output. | 0 |
23
23
24
24
### Configuration File
25
25
26
-
In your main configuration file, append the following _Input_ & _Output_ sections:
26
+
In your main configuration file append the following:
0 commit comments