Tag: Observability
All the articles with the tag "Observability".

AWS from scratch, part 3: logs and detection — CloudTrail, GuardDuty, Security Hub: see the intrusion before your customers do
The third of five articles on securing infrastructure in AWS — seeing and responding: an organization CloudTrail into S3 with Object Lock, GuardDuty detecting crypto-mining, IAM anomalies and EKS runtime threats, Security Hub on the CIS AWS Foundations Benchmark, Config aggregators for drift, CloudTrail Lake for investigations, and an alert pipeline into Telegram. Logs without detection are an archive; detection without an on-call alert is a fantasy — we build the whole chain.

VictoriaMetrics instead of Prometheus+Thanos: one binary instead of three — when it's honest savings
Long-term metric storage on Prometheus means Thanos: sidecar, store gateway, compactor and query on top of S3. Where VictoriaMetrics single-binary covers the same with one process: active-time-series thresholds, the vmagent/vmalert/vmbackup ecosystem, two migration paths, and RAM/disk numbers.

OBI: zero-code application tracing via eBPF, the Grafana Beyla successor
OpenTelemetry eBPF Instrumentation (OBI) traces HTTP/gRPC/SQL straight from the kernel — no in-container agent, no line of application code touched. We look at how OBI differs from Hubble, Tetragon and Pyroscope, how it plugs into an OTel Collector you already run, and where zero-code instrumentation hits its ceiling.

KEDA: event-driven autoscaling, all the way to zero
KEDA scales pods by queue depth, a metric, or a schedule — not just CPU/RAM — and can scale all the way down to zero. ScaledObject, scalers for Kafka/RabbitMQ/Prometheus/cron, and the polling interval, activation-vs-scaling threshold, and cooldown gotchas.