Prejsť na hlavný obsah
🔒 Režim náhľadu. Prvých pätnásť lekcií Foundations je zadarmo; táto je Pro. Spustite 7-dňový trial pre odomknutie editora, AI nápovied a zvyšku kurzu. Karta vyžadovaná, zrušte kedykoľvek v Dashboard.
Spustiť 7-dňový trial →
⚡
← Kurzy
›
DevOps for Python services
›
Module 1 · Docker & Containers · Recap
›
Sentry pre sledovanie chýb
quiz
27 / 104
🇸🇰
SK
▼
↗
Zdieľať
⋯
Viac
+75 XP
📋
Úloha
📖
Teória
🤖
Pomoc AI
Úloha
🌐 shown in EN
📝 **Question:** Why use Sentry on top of structured logs? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Kvíz
Otázka
📝 **Question:** Why use Sentry on top of structured logs? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
A
Sentry replaces your log pipeline entirely because every log line above WARN is captured as a structured event with stack trace, making your ELK or Loki deployment redundant for most workloads
B
Sentry deduplicates errors, groups by fingerprint, tracks release regressions, and alerts on new/spiking issues
C
Sentry is meaningfully cheaper than equivalent log volume because its event-based pricing scales with unique errors rather than total lines, so noisy debug logs no longer drive the storage bill
D
It's required by GDPR — Sentry automatically scrubs personally identifiable information from every captured event, which raw logs don't do, so compliance audits will fail without it in place
Odpovedať
💬
Kontaktovať podporu