S3 loader monitoring
The S3 loader has several types of monitoring built in, to help the pipeline operator: Statsd metrics, Sentry alerts, and Snowplow tracking.
Statsd is a daemon that aggregates and summarizes application metrics. It receives metrics sent by the application over UDP, and then periodically flushes the aggregated metrics to a pluggable storage backend.
When processing enriched events, the S3 loader can emit metrics to a statsd daemon describing every S3 file it writes. Here is a string representation of the metrics it sends:
count_good: the total number of events in the batch that was loaded.
latency_collector_to_load: this is the time difference between reaching the collector and getting loaded to S3.
Statsd monitoring is configured by setting the
monitoring.metrics.statsd section in the hocon file:
Sentry is a popular error monitoring service, which helps developers diagnose and fix problems in an application. The S3 loader can send an error report to sentry whenever something unexpected happens. The reasons for the error can then be explored in the sentry server’s UI.
Common reasons might be failure to read or write from Kinesis, or failure to write to S3.
Sentry monitoring is configured by setting the
monitoring.sentry.dsn key in the hocon file with the url of your sentry server:
The loader can emit a Snowplow event to a collector when the application experiences runtime problems. It sends app_initialized and app_heartbeat events to show the application is alive. A storage_write_failed event is sent when a file cannot be written to S3, and a app_shutdown event is sent when the application exits due to too many S3 errors.
Snowplow monitoring is configured by setting the
monitoring.snowplow section in the hocon file: