Перейти к основному содержимому
🔒 Режим превью. Первые 15 уроков Foundations — бесплатные; этот — Pro. Запусти 7-дневный trial чтобы открыть редактор, AI-подсказки и остальной курс. Нужна карта, отмена в Dashboard в любой момент.
Начать 7-дневный trial →
⚡
← Курсы
›
DevOps for Python services
›
Module 1 · Docker & Containers · Recap
›
Sentry для отслеживания ошибок
quiz
27 / 104
🇷🇺
RU
▼
↗
Поделиться
⋯
Ещё
+75 XP
📋
Задание
📖
Теория
🤖
Помощь AI
Задание
🌐 shown in EN
📝 **Question:** Why use Sentry on top of structured logs? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Тест
Вопрос
📝 **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
Ответить
💬
Связаться с поддержкой