DataCollectorArgs

data class DataCollectorArgs(val collections: Output<Map<String, CollectionArgs>>, val requestLogging: Output<RequestLoggingArgs>? = null, val rollingRate: Output<Either<String, RollingRateType>>? = null) : ConvertibleToJava<DataCollectorArgs>

Constructors

Link copied to clipboard
constructor(collections: Output<Map<String, CollectionArgs>>, requestLogging: Output<RequestLoggingArgs>? = null, rollingRate: Output<Either<String, RollingRateType>>? = null)

Properties

Link copied to clipboard

Required The collection configuration. Each collection has it own configuration to collect model data and the name of collection can be arbitrary string. Model data collector can be used for either payload logging or custom logging or both of them. Collection request and response are reserved for payload logging, others are for custom logging.

Link copied to clipboard
val requestLogging: Output<RequestLoggingArgs>? = null

The request logging configuration for mdc, it includes advanced logging settings for all collections. It's optional.

Link copied to clipboard
val rollingRate: Output<Either<String, RollingRateType>>? = null

When model data is collected to blob storage, we need to roll the data to different path to avoid logging all of them in a single blob file. If the rolling rate is hour, all data will be collected in the blob path /yyyy/MM/dd/HH/. If it's day, all data will be collected in blob path /yyyy/MM/dd/. The other benefit of rolling path is that model monitoring ui is able to select a time range of data very quickly.

Functions

Link copied to clipboard
open override fun toJava(): DataCollectorArgs