Get desktop application:
View/edit binary Protocol Buffers messages
Offload queue that uses AWS SQS
Used in:
The queue name to lookup and use.
Specify a bearer token. This is currently specified in the x-bitdrift-api-key header.
Used in: ,
The token specified inline.
The file to load the token from.
Wraps data that can be specified inline, via the environment, or within a file.
The data will be pulled from the environment or inline.
The data will be pulled from the specified file path.
Wraps data that can be specified inline or come via environment.
Used in: , , , ,
The data will be pulled from this environment variable.
The data is specified by this value.
Configuration for an individual file source.
Used in: ,
A local file source.
A remote HTTP based file source.
HTTP file source configuration.
Used in:
The URL to fetch. The first fetch does not supply an if-none-match header and expects a 200 response with the file contents as well as an etag. Future requests will return the etag in the if-none-match header and expect a 304 response if the contents have not changed.
How often the file will be checked for changes. Defaults to 60s.
Whether an authentication token will be provided in the x-bitdrift-api-key header.
Fetch request timeout. If not set defaults to 15s.
If configured, the fetched file will be cached to this path. Furthermore, on startup, if the remote server cannot be contacted, the file cache contents will be used as long as the integrity is verified.
Local file source configuration.
Used in:
The path to the file. This file will be watched for changes and reloaded as needed. Atomic file swaps should be used to make sure file reads are consistent.
Offload queue for local integration testing only.
Used in:
(message has no fields)
Configuration for the retry offload queue: the ability to offload metrics to durable storage to be retried later.
Used in:
The maximum number of send attempts. If not set, retries are unbounded and only governed by the window defined below.
The base backoff time for each request. The backoff is multiplied by the current send attempt. Defaults to 20s.
The total duration each request will be attempted, across all retries. Defaults to 20m.
Configure AWS SQS for offloading.
Configure local loopback. This is for integration testing.
Retry policy configuration.
Used in: , ,
Controls the number of retries that are allowed concurrently. The "budget" is defined as a % where the number of retries is a % of the number of active requests. The default if not specified is 0.1 (10%). Valid values are > 0.0 and <= 1.0. For example, with a budget of 10%, if there are 10 active requests, 1 retry will be allowed. If there are 20, 2 will be allowed, and so on.
Sets the maximum number of retry attempts. Default is unlimited and governed only by the request timeout and expontential backoff policy
Configuration for the retry offload queue.
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: , ,
Directory to watch for updates. See above. This needs to be the directory that owns whatever symlink is being atomically swapped.
File to watch for updates. This is the actual full file path.
Wire protocol type.
Used in: , , , ,
Used in:
(message has no fields)
Used in:
Whether to attempt parsing lyft/statsrelay style tags of the form: foo.__bar=baz:3.0|c This will produce the ("bar", "baz") tag. This is currently only supported for inflow. It will be ignored on outflow.
Sanitize tag names and values by replacing ':', '.', and '=' with '_'. This matches statsrelay behavior.