This optional interface will serve Prometheus metrics from /metrics. It will be disabled if the field observability_interface is not provided in configuration.yaml. The following metrics are included by default, others are transform specific.
| Name | Labels | Data type | Description |
|---|---|---|---|
shotover_transform_total_count |
transform |
counter | Counts the amount of times the transform is used |
shotover_transform_failures_count |
transform |
counter | Counts the amount of times the transform fails |
shotover_transform_latency_seconds |
transform |
histogram | The latency for a message batch to go through the transform |
shotover_chain_total_count |
chain |
counter | Counts the amount of times chain is used |
shotover_chain_failures_count |
chain |
counter | Counts the amount of times chain fails |
shotover_chain_latency_seconds |
chain |
histogram | The latency for running chain |
shotover_chain_requests_batch_size |
chain |
histogram | The number of requests in each request batch passing through chain. |
shotover_chain_responses_batch_size |
chain |
histogram | The number of responses in each response batch passing through chain. |
shotover_available_connections_count |
source |
gauge | How many more connections can be opened to source before new connections will be rejected. |
connections_opened |
source |
counter | Counts the total number of connections that clients have opened against this source. |
shotover_connections_accept_failures_count |
source |
counter | Counts failures while accepting incoming listener connections for this source. If this increases continuously, Shotover is retrying accepts with backoff. |
shotover_listener_create_failures_count |
source |
counter | Counts runtime failures while creating a listener for this source. If this increases continuously, Shotover is retrying listener creation with backoff. |
shotover_source_to_sink_latency_seconds |
sink |
histogram | The milliseconds between reading a request from a source TCP connection and writing it to a sink TCP connection |
shotover_sink_to_source_latency_seconds |
source |
histogram | The milliseconds between reading a response from a sink TCP connection and writing it to a source TCP connection |
A single value, which can only be incremented, not decremented. Starts out with an initial value of zero.
Measures the distribution of values for a set of measurements and starts with no initial values.
Every 20 seconds one of the 3 chunks of historical values are cleared. This means that values are held onto for around 60 seconds.
A single value that can increment or decrement over time. Starts out with an initial value of zero.
You can configure log levels and filters at /filter. This can be done by a POST HTTP request to the /filter endpoint with the env_filter string set as the POST data. For example:
curl -X PUT -d 'info, shotover_proxy=info, shotover::connection_span::info` http://127.0.0.1:9001/filterSome examples of how you can tweak this filter:
- configure the first
infoto set the log level for dependencies - configure
shotover=infoto set the log level for shotover itself - set
shotover::connection_span=infotoshotover::connection_span=debugto attach connection info to most log events, this is disabled by default due to a minor performance hit.
For more control over filtering you should understand The tracing filter format.