EnvVars

class EnvVars : IEnvVars

Types

Link copied to clipboard
object Companion

Functions

Link copied to clipboard
open fun getProfileWriter(): Writer

Properties

Link copied to clipboard
open override val debug: Boolean = false
Link copied to clipboard
open override val disableAuth: Boolean
Link copied to clipboard
open override val emptyProfilesDatasetIds: List<String>
Link copied to clipboard
open override val expectedApiKey: String
Link copied to clipboard
open override val fileSystemWriterRoot: String
Link copied to clipboard
open override val ignoredKeys: Set<String>
Link copied to clipboard
open override val kafkaConfig: KafkaConfig?
Link copied to clipboard
open override val orgId: String
Link copied to clipboard
open override val port: Int
Link copied to clipboard
open override val profileStorageMode: WriteLayer
Link copied to clipboard
open override val profileWritePeriod: ProfileWritePeriod

This controls how often profiles are written out. If this is set to hourly and the whylogsPeriod is set to daily then profiles will still be bucked into days, but they'll be written out every hour. By default, this will match the whylogsPeriod.

Link copied to clipboard
open override val requestQueueingEnabled: Boolean
Link copied to clipboard
open override val requestQueueingMode: WriteLayer
Link copied to clipboard
open override val requestQueueProcessingIncrement: PopSize
Link copied to clipboard
open override val s3Bucket: String
Link copied to clipboard
open override val s3Prefix: String
Link copied to clipboard
open override val whylabsApiEndpoint: String
Link copied to clipboard
open override val whylabsApiKey: String
Link copied to clipboard
open override val whylogsPeriod: ChronoUnit

The period to group profiles into. If this is hourly then you'll end up with hourly profiles. This should probably be set to the same time period as the model that it's uploading to in WhyLabs.

Link copied to clipboard
open override val writer: WriterTypes