The namespace used otherwise will be defaulted to eventstoredb.

default_namespace

endpoints

Configures an HTTP(S) proxy for Vector to use. By default, the globally configured proxy is used.

proxy

enabled

http

https

A list of hosts to avoid proxying. Allowed patterns here include:

Pattern | Example match
:-------|:-------------
Domain names | `example.com` matches requests to `example.com`
Wildcard domains | `.example.com` matches requests to `example.com` and its subdomains
IP addresses | `127.0.0.1` matches requests to 127.0.0.1
[CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) blocks | `192.168.0.0./16` matches requests to any IP addresses in this range
Splat | `*` matches all hosts

no_proxy

The interval between scrapes, in seconds.

scrape_interval_secs

The component type. This is a required field for all components and tells Vector which component to use.

type

The global URL to proxy HTTPS requests through.

If another HTTPS proxy is set in the configuration file or at a component level,
this one will be overriden.

The lowercase variant has priority over the uppercase one.

HTTPS_PROXY

The global URL to proxy HTTP requests through.

If another HTTP proxy is set in the configuration file or at a component level,
this one will be overridden.

The lowercase variant has priority over the uppercase one.

HTTP_PROXY

List of hosts to avoid proxying globally.

Allowed patterns here include:
	- Domain names. For example, `example.com` will match requests to to `example.com`
	- Wildcard domains. For example, `.example.com` will match requests to `example.com` and its subdomains
	- IP addresses. For example, `127.0.0.1` will match requests to 127.0.0.1
	- CIDR blocks. For example, `192.168.0.0./16` will match requests to any IP addresses in this range
	- `*` will match all hosts

If another no_proxy value is set in the configuration file or at a component level, this one will be overridden.

The lowercase variant has priority over the uppercase one.

NO_PROXY

http_proxy

https_proxy

EventStoreDB

EventStoreDB Stats client

Enriches data with useful EventStoreDB Stats client context.

By default, the `eventstoredb_metrics` source augments events with helpful
context keys.

context

Context

This component is stateless, meaning its behavior is consistent across each input.

state

State

eventstoredb_metrics

disk_free_bytes

The accumulated number of bytes read in from disk.

disk_read_bytes_total

disk_read_ops_total

disk_total_bytes

disk_used_bytes

disk_write_ops_total

The accumulated number of bytes written out to disk.

disk_written_bytes_total

The number of bytes of main memory not used.

memory_free_bytes

The number of bytes of main memory used by the EventStoreDB node.

process_memory_used_bytes

The number of events accepted by this component either from tagged
origin like file and uri, or cumulatively from other origins.

events_in_total

The total number of events emitted by this component.

events_out_total

The total number of HTTP request errors for this component.

http_request_errors_total

The total number of errors parsing metrics for this component.

parse_errors_total

The number of bytes processed by the component.

processed_bytes_total

A ratio from 0 to 1 of the load on a component. A value of 0 would indicate a completely idle component that is simply waiting for input. A value of 1 would indicate a that is never idle. This value is updated every 5 seconds.

EventStoreDB Metrics

Configuration Options

Required Options

type(required)

Advanced Options

endpoints(optional)

scrape_interval_secs(optional)

proxy(optional)

default_namespace(optional)

How it Works

State

Context