chore: Update SecOps batch log count limit config flag documentation (#…

…2127)

exporter/chronicleexporter/config.go

@@ -88,7 +88,8 @@ type Config struct {
 
 	// BatchLogCountLimitGRPC is the maximum number of logs that can be sent in a single batch to Chronicle via the GRPC protocol
 	// This field is defaulted to 1000, as that is the default Chronicle backend limit.
-	// All batched logs beyond the backend limit will be dropped. Any batches with more logs than this limit will be split into multiple batches
+	// All batched logs beyond the backend limit will not be able to be queryable via the Raw Logs Search, but will be queryable via UDM Search.
+	// Any batches with more logs than this limit will be split into multiple batches
 	BatchLogCountLimitGRPC int `mapstructure:"batch_log_count_limit_grpc"`
 
 	// BatchRequestSizeLimitGRPC is the maximum batch request size, in bytes, that can be sent to Chronicle via the GRPC protocol
@@ -98,7 +99,8 @@ type Config struct {
 
 	// BatchLogCountLimitHTTP is the maximum number of logs that can be sent in a single batch to Chronicle via the HTTP protocol
 	// This field is defaulted to 1000, as that is the default Chronicle backend limit.
-	// All batched logs beyond the backend limit will be dropped. Any batches with more logs than this limit will be split into multiple batches
+	// All batched logs beyond the backend limit will not be able to be queryable via the Raw Logs Search, but will be queryable via UDM Search.
+	// Any batches with more logs than this limit will be split into multiple batches
 	BatchLogCountLimitHTTP int `mapstructure:"batch_log_count_limit_http"`
 
 	// BatchRequestSizeLimitHTTP is the maximum batch request size, in bytes, that can be sent to Chronicle via the HTTP protocol