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
Copy file name to clipboardExpand all lines: docs/deploy-coe-with-Kafka.md
+48-4Lines changed: 48 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ The following diagram illustrates a Citrix ADC as an Ingress Gateway with Citrix
20
20
21
21
**Note**: In this example scenario, the YAML file is used to deploy Citrix ADC Observability Exporter in the Kubernetes *defauIt* namespace. If you want to deploy in a private Kubernetes namespace other than *default*, edit the YAML file to specify the namespace.
22
22
23
-
The following is a sample application deployment procdure.
23
+
The following is a sample application deployment procedure.
24
24
25
25
**Note**: If you have a pre-deployed web application, skip the step 1 and 2.
26
26
@@ -88,6 +88,7 @@ To edit the YAML file for the required changes, perform the following steps:
88
88
"KAFKA": {
89
89
"ServerUrl": "X.X.X.X:9092", #Specify the Kafka broker IP
90
90
"KafkaTopic": "HTTP", #Specify the desired kafka topic
91
+
"DataFormat": "AVRO",
91
92
"RecordType": {
92
93
"HTTP": "all",
93
94
"TCP": "all",
@@ -112,8 +113,10 @@ To edit the YAML file for the required changes, perform the following steps:
112
113
}
113
114
}
114
115
```
116
+
117
+
**Note:** To export transactions in the JSON format, see [exporting transaction in JSON format to Kafka](#support-for-exporting-transactions-in-the-json-format-from-citrix-adc-observability-exporter-to-kafka).
115
118
116
-
2. Specify the host name and IP or FQDN address of the Kafka nodes. Use the following YAML definition for a three node Kafka cluster:
119
+
2. Specify the host name and IP or FQDN address of the Kafka nodes. Use the following YAML definition for a three node Kafka cluster:
117
120
118
121
```yml
119
122
apiVersion: apps/v1
@@ -218,7 +221,7 @@ To verify the Citrix ADC Observability Exporter deployment, perform the followin
218
221
219
222

220
223
221
-
3. Use Kafka Consumer to view the transaction data. Access kafka Consumer from [PythonKafkaConsumer](https://kafka-python.readthedocs.io/en/master/apidoc/KafkaConsumer.html).
224
+
3. Use Kafka Consumer to view the transaction data. Access Kafka Consumer from [PythonKafkaConsumer](https://kafka-python.readthedocs.io/en/master/apidoc/KafkaConsumer.html).
222
225
223
226
The following image shows sample data from Kafka Consumer.
224
227
@@ -274,4 +277,45 @@ set analyticsprofile ns_analytics_time_series_profile -collectors metrichost_SVC
274
277
```
275
278
276
279
For information on troubleshooting related to Citrix ADC Observability Exporter, see [Citrix ADC CPX troubleshooting](https://docs.citrix.com/en-us/citrix-adc-cpx/current-release/cpx-troubleshooting.html).
277
-
280
+
281
+
## Support for exporting transactions in the JSON format from Citrix ADC Observability Exporter to Kafka
282
+
283
+
You can now export transactions from Citrix ADC Observability Exporter to Kafka in the JSON format apart from the AVRO format.
284
+
A new parameter `DataFormat` is introduced in the Kafka deployment ConfigMap to support transactions in the JSON format.
285
+
This parameter can accept AVRO and JSON values. For allowing JSON based transactions, set the value of
286
+
`DataFormat` as JSON in the
287
+
[coe-kafka.yaml](https://raw.githubusercontent.com/citrix/citrix-observability-exporter/master/examples/kafka/coe-kafka.yaml) file. The default value is AVRO.
288
+
289
+
The following example shows the YAML file with the data format configured as JSON.
290
+
291
+
```yml
292
+
apiVersion: v1
293
+
kind: ConfigMap
294
+
metadata:
295
+
name: coe-config-kafka
296
+
data:
297
+
lstreamd_default.conf: |
298
+
{
299
+
"Endpoints": {
300
+
"KAFKA": {
301
+
"DataFormat": "JSON",
302
+
"ServerUrl": "X.X.X.X:9092", #Specify the Kafka broker IP
303
+
"KafkaTopic": "HTTP", #Specify the desired kafka topic
0 commit comments