Přejít k hlavnímu obsahu
🔒 Režim náhledu. Prvních patnáct lekcí Foundations je zdarma; tato je Pro. Spusťte 7denní trial pro odemčení editoru, AI nápověd a zbytku kurzu. Karta vyžadována, zrušte kdykoli v Dashboard.
Spustit 7denní trial →
⚡
← Kurzy
›
DevOps for Python services
›
Module 1 · Docker & Containers · Recap
›
Hlídač pro sledování chyb
quiz
27 / 104
🇨🇿
CS
▼
↗
Sdílet
⋯
Více
+75 XP
📋
Úkol
📖
Teorie
🤖
Pomoc AI
Úkol
🌐 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
Odpovědět
💬
Kontaktovat podporu