From 2e15ac11b46fe824198ed543d62d22d2a956fa7a Mon Sep 17 00:00:00 2001 From: syedhassaanahmed Date: Thu, 8 Jun 2023 20:14:35 +0200 Subject: [PATCH] Fix KafkaConnectionProperties example --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1ca6d1d..30b22d4 100644 --- a/README.md +++ b/README.md @@ -44,7 +44,7 @@ The amount of devices, their names and telemetry generated can be customized usi |-|-| |IotHubConnectionString|Iot Hub connection string. "Device" our "Iot Hub owner" scopes are good. Example: HostName=your-iothub-name.azure-devices.net;SharedAccessKeyName=device;SharedAccessKey=your-iothub-key| |EventHubConnectionString|Event Hub connection string. SAS Policy "Send" is required. For EventHub no device registration is required. Example: Endpoint=sb://your-eventhub-namespace.servicebus.windows.net/;SharedAccessKeyName=send;SharedAccessKey=your-send-sas-primary-key;EntityPath=your-eventhub-name.| -|KafkaConnectionProperties|Kafka connection properties as a JSON string. Example: `{"bootstrap.servers=kafka"}`.| +|KafkaConnectionProperties|Kafka connection properties as a JSON string. Example: `{"bootstrap.servers": "kafka"}`.| |KafkaTopic|Kafka topic name.| |DeviceList|comma separated list of device identifiers (default = ""). Use it to generate telemetry for specific devices instead of numeric generated identifiers. If the parameter has a value the following parameters are ignored: DevicePrefix, DeviceIndex and DeviceCount are ignored| |DevicePrefix|device identifier prefix (default = "sim")|