Skip to main content

Snowbridge monitoring configuration

Snowbridge comes with configurable logging, pprof profiling, statsD statistics and Sentry integrations to ensure that you know what's going on.

Logging

Use the log_level parameter to specify the log level.

hclassets/docs/configuration/monitoring/log-level-example.hcl
loading...

Sentry Configuration

hclassets/docs/configuration/monitoring/sentry-example.hcl
loading...

StatsD stats receiver configuration

hclassets/docs/configuration/monitoring/statsd-example.hcl
loading...

End-to-end latency configuration

Snowplow Enriched data only:

hclassets/docs/configuration/metrics/e2e-latency-example.hcl
loading...

Metric definitions

Snowbridge sends the following metrics to statsd:

MetricDefinitions
target_successEvents successfully sent to the target.
target_failedEvents which failed to reach the target, and will be handled by the retry config. Retries which fail are also counted.
message_filteredEvents filtered out via transformation.
failure_target_successEvents we could not send to the target, which are not retryable, successfully sent to the failure target.
failure_target_failedEvents we could not send to the target, which are not retryable, which we failed to send to the failure target. In this scenario, Snowbridge will crash.
min_processing_latencyMin time between entering Snowbridge and write to target.
max_processing_latencyMax time between entering Snowbridge and write to target.
min_message_latencyMin time between entering the source stream and write to target.
max_message_latencyMax time between entering the source stream and write to target.
min_transform_latencyMin time between start and completion of transformation.
max_transform_latencyMax time between start and completion of transformation.
min_filter_latencyMin time between entering Snowbridge and being filtered out.
max_filter_latencyMax time between entering Snowbridge and being filtered out.
min_request_latencyMin time between starting request to target and finishing request to target.
max_request_latencyMax time between starting request to target and finishing request to target.
sum_request_latencySum of request times, use with target_request_count to calculate average request latency.
target_request_countNumber of requests sent to target, use with sum_request_latency to calculate average request latency.
min_e2e_latencyMin time between Snowplow collector tstamp and finishing request to target. Enabled via configuration - Snowplow enriched data only.
max_e2e_latencyMax time between Snowplow collector tstamp and finishing request to target. Enabled via configuration - Snowplow enriched data only.