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
You can forward logs to an external Kafka broker in addition to, or instead of, the default Elasticsearch log store.
10
+
You can forward logs to an external Kafka broker in addition to, or instead of, the default log store.
5
11
6
12
To configure log forwarding to an external Kafka instance, you must create a `ClusterLogForwarder` custom resource (CR) with an output to that instance, and a pipeline that uses the output. You can include a specific Kafka topic in the output or use the default. The Kafka output can use a TCP (insecure) or TLS (secure TCP) connection.
7
13
@@ -75,11 +81,11 @@ spec:
75
81
** Optional: String. One or more labels to add to the logs.
76
82
<14> Optional: Specify `default` to forward logs to the internal Elasticsearch instance.
77
83
78
-
. Optional: To forward a single output to multiple Kafka brokers, specify an array of Kafka brokers as shown in this example:
84
+
. Optional: To forward a single output to multiple Kafka brokers, specify an array of Kafka brokers as shown in the following example:
79
85
+
80
86
[source,yaml]
81
87
----
82
-
...
88
+
# ...
83
89
spec:
84
90
outputs:
85
91
- name: app-logs
@@ -91,15 +97,15 @@ spec:
91
97
- tls://kafka-broker1.example.com:9093/
92
98
- tls://kafka-broker2.example.com:9093/
93
99
topic: app-topic <3>
94
-
...
100
+
# ...
95
101
----
96
102
<1> Specify a `kafka` key that has a `brokers` and `topic` key.
97
103
<2> Use the `brokers` key to specify an array of one or more brokers.
98
-
<3> Use the `topic` key to specify the target topic that will receive the logs.
104
+
<3> Use the `topic` key to specify the target topic that receives the logs.
99
105
100
-
. Create the CR object:
106
+
. Apply the `ClusterLogForwarder` CR by running the following command:
0 commit comments