Package stores holds logic for generic access to various configuration sources (e.g.

Package types holds things that are used in a lot of other packages that are prone to creating circular dependencies when put elsewhere.

CallConfigure will call the Configure method on an observer or monitor with a `conf` object, typed to the correct type.

DecodeOtherConfig will pull out the OtherConfig values from both ObserverConfig and MonitorConfig and decode them to a struct that is provided in the `out` arg.

FillInConfigTemplate takes a config template value that a monitor/observer provided and fills it in dynamically from the provided conf.

LoadConfigFromContent transforms yaml to a Config struct.

ServiceEndpointsFromConfig returns the manually defined service endpoints in a monitor config.

ValidateCustomConfig for module-specific config ahead of time for a specific module configuration.

EnvReplacer replaces .

CollectdConfig high-level configurations.

Config is the top level config struct that everything goes under.

LogConfig contains configuration related to logging.

MetricFilter describes a set of subtractive filters applied to datapoints right before they are sent.

MonitorConfig configures a given monitor instance.

ObserverConfig holds the configuration for an observer.

StoreConfig holds configuration related to config stores (e.g.

WriterConfig holds configuration for the datapoint writer.

CustomConfigurable should be implemented by config structs that have the concept of generic other config that is initially deserialized into a map[string]interface{} to be later transformed to another form.

MonitorCustomConfig represents monitor-specific configuration that doesn't appear in the MonitorConfig struct.

Validatable should be implemented by config structs that want to provide validation when the config is loaded.