Preskoči na glavni sadržaj
🔒 Način pregleda. Prvih petnaest Foundations lekcija je besplatno; ova je Pro. Pokrenite 7-dnevni trial da otključate editor, AI savjete i ostatak programa. Kartica obavezna, otkažite bilo kada u Dashboard.
Pokreni 7-dnevni trial →
⚡
← Kolegiji
›
DevOps for Python services
›
Module 1 · Docker & Containers · Recap
›
Stražar za praćenje grešaka
quiz
27 / 104
🇭🇷
HR
▼
↗
Podijeli
⋯
Više
+75 XP
📋
Zadatak
📖
Teorija
🤖
AI Pomoć
Zadatak
🌐 shown in EN
📝 **Question:** Why use Sentry on top of structured logs? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Kviz
Pitanje
📝 **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
Odgovori
💬
Kontaktiraj podršku