Ugrás a fő tartalomra
🔒 Előnézet mód. Az első tizenöt Foundations lecke ingyenes; ez Pro. Indíts 7 napos trial-t, hogy feloldd a szerkesztőt, az AI tippeket és a tananyag többi részét. Kártya szükséges, bármikor lemondhatod a Dashboard-ban.
7 napos trial indítása →
⚡
← Kurzusok
›
DevOps for Python services
›
Module 1 · Docker & Containers · Recap
›
Sentry a hibakövetéshez
quiz
27 / 104
🇭🇺
HU
▼
↗
Megosztás
⋯
Több
+75 XP
📋
Feladat
📖
Elmélet
🤖
AI Segítség
Feladat
🌐 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
Kérdés
📝 **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
Válaszolj
💬
Ügyfélszolgálat