package pulse.config.common.v1

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message AwsSqsRetryOffloadQueue

retry.proto:15

Offload queue that uses AWS SQS

Used in: RetryOffloadQueue

message BearerTokenConfig

common.proto:38

Specify a bearer token. This is currently specified in the x-bitdrift-api-key header.

Used in: HttpFileSourceConfig, outflow.v1.HttpRemoteWriteAuthConfig

message EnvInlineOrFile

common.proto:64

Wraps data that can be specified inline, via the environment, or within a file.

message EnvOrInline

common.proto:51

Wraps data that can be specified inline or come via environment.

Used in: bootstrap.v1.KubernetesBootstrapConfig, bootstrap.v1.MetaStats, EnvInlineOrFile, inflow.v1.KubernetesPrometheusConfig.HttpServiceDiscovery, outflow.v1.RequestHeader

message FileSourceConfig

file_watcher.proto:45

Configuration for an individual file source.

Used in: processor.v1.DropProcessorConfig, processor.v1.ElisionConfig.BlocklistConfig

message HttpFileSourceConfig

file_watcher.proto:23

HTTP file source configuration.

Used in: FileSourceConfig

message LocalFileSourceConfig

file_watcher.proto:16

Local file source configuration.

Used in: FileSourceConfig

message LoopbackForTestOffloadQueue

retry.proto:21

Offload queue for local integration testing only.

Used in: RetryOffloadQueue

(message has no fields)

message RetryOffloadQueue

retry.proto:25

Configuration for the retry offload queue: the ability to offload metrics to durable storage to be retried later.

Used in: RetryPolicy

message RetryPolicy

retry.proto:50

Retry policy configuration.

Used in: outflow.v1.OtlpClientConfig, outflow.v1.PromRemoteWriteClientConfig, processor.v1.InternodeConfig.RequestPolicy

message RuntimeConfig

common.proto:92

A file that is watched on the filesystem, typically within a K8s config map. Note that `dir` watches for *renames* in this directory only without recursion. This limits watched changes and is required for Kubernetes `ConfigMap` deployments. A Kubernetes `ConfigMap` deployment might work as follows: 1. Mount `ConfigMap` to `/config_map/foo`. 2. Set `dir` to `/config_map/foo`. 3. Set `file` to `/config_map/foo/foo.yaml`. Internally Kubernetes will create the following structure: 1. `/config_map/foo/real_data/foo.yaml`. 2. `/config_map/foo/..data` -> `/config_map/foo/real_data`. 3. `/config_map/foo/foo.yaml` -> `/config_map/foo/..data/foo.yaml`. Further data swaps will only rename the `..data` symlink.

Used in: bootstrap.v1.Config, bootstrap.v1.MergedConfig, LocalFileSourceConfig

message WireProtocol

common.proto:14

Wire protocol type.

Used in: inflow.v1.MetricGeneratorConfig, inflow.v1.TcpServerConfig, inflow.v1.UdpServerConfig, inflow.v1.UnixServerConfig, outflow.v1.CommonWireClientConfig

message WireProtocol.Carbon

common.proto:15

Used in: WireProtocol

(message has no fields)

message WireProtocol.StatsD

common.proto:17

Used in: WireProtocol