--- title: "Observability Stack: Monitoring, Logging & Tracing" description: "Master observability fundamentals: monitoring with metrics, structured logging, distributed tracing, and observability practices. Learn to build observable systems and debug production issues." author: "Mohammad Abu Mattar" canonical: https://mkabumattar.com/quizzes/post/observability-stack-quiz --- # Observability Stack: Monitoring, Logging & Tracing Welcome to the Observability Stack Quiz! This quiz will test your knowledge of monitoring, logging, and tracing concepts in modern software systems. Each question is designed to challenge your understanding of how observability works and how it can be applied to build reliable, maintainable applications. Good luck! ## Questions ### 1. What are the three pillars of observability? - Metrics, logs, and distributed traces - Uptime, availability, and error rates - Dashboards, alerts, and report logs - CPU, memory, and disk utilization **Hint:** Think about the main data types collected from systems. ### 2. What are metrics in observability? - Timestamped numerical measurements of system behavior - Textual records of specific application events - Contextual paths of requests across services - Automated notifications triggered by thresholds **Hint:** Think about numerical measurements over time. ### 3. What is structured logging? - Logs using fixed key-value formats like JSON - Logs organized strictly by severity levels - Logs stored in a relational SQL database - Logs restricted to system-level kernel events **Hint:** Think about logs with consistent, parseable format. ### 4. What is a distributed trace in observability? - A map of a request as it moves through services - A collection of all error logs from one host - A snapshot of memory usage during a crash - A history of configuration changes in a cluster **Hint:** Think about following a request through multiple services. ### 5. What is Prometheus in the observability stack? - A time-series database for metric collection - A centralized engine for log search and index - A dashboarding UI for multi-source visualization - A proxy for load balancing network requests **Hint:** Think about a tool for collecting and scraping metrics. ### 6. What is Grafana used for? - Visualizing data via dashboards and graphs - Scraping and storing time-series metric data - Generating and propagating trace context IDs - Parsing and transforming raw log aggregates **Hint:** Think about visualizing metric data with dashboards. ### 7. What is the ELK Stack in observability? - A platform for log search, ingestion, and UI - A suite for infrastructure performance metrics - A protocol for standardized trace propagation - A framework for automated incident response **Hint:** Think about three tools for log aggregation and analysis. ### 8. What is Jaeger used for? - Monitoring and troubleshooting distributed traces - Aggregating and indexing application log files - Proving uptime through external health checks - Managing alert notifications and on-call rotations **Hint:** Think about visualizing request flows across services. ### 9. What is a span in distributed tracing? - The record of a single unit of work or operation - The total time a request takes from start to finish - A unique identifier assigned to a specific user - A threshold limit for triggering a system alert **Hint:** Think about a single operation within a trace. ### 10. What is a trace context, and why is it important? - Metadata passed between services to link spans - The configuration file for a tracing backend - A summary report of system-wide performance - The specific code library used for instrumentation **Hint:** Think about correlating requests across services. ### 11. What is sampling in observability? - Recording a subset of events to reduce overhead - Testing a system under heavy simulated load - Selecting random servers for manual log inspection - The process of converting raw logs into metrics **Hint:** Think about not collecting every single event. ### 12. What is an SLO (Service Level Objective)? - A target value or range for service reliability - The actual measured uptime of a service - A legal contract specifying penalties for downtime - A technical tool used for synthetic monitoring **Hint:** Think about target reliability or performance. ### 13. What is an SLI (Service Level Indicator)? - A specific metric used to measure service levels - The target percentage for service availability - A notification sent when a service is failing - The documentation for an application API **Hint:** Think about measuring actual system performance. ### 14. What is an error budget in observability? - The total allowed unreliability before missing an SLO - The financial cost allocated for cloud monitoring - The maximum number of errors a developer can make - A buffer for network latency in a distributed system **Hint:** Think about allowed downtime within an SLO. ### 15. What is cardinality in metrics? - The number of unique sets of label-value pairs - The frequency at which metrics are collected - The total number of servers being monitored - The mathematical accuracy of a numerical metric **Hint:** Think about the number of unique label combinations. ### 16. What is APM (Application Performance Monitoring)? - A suite for monitoring code-level execution and health - A protocol for basic hardware-level status checks - A method for managing project development lifecycles - A dashboard showing only network bandwidth usage **Hint:** Think about end-to-end application monitoring. ### 17. What is a RED metric (Rate, Errors, Duration)? - A framework focusing on request-based service health - A color-coded system for prioritizing incident response - A dashboard for tracking resource-level utilization - A validation check for data integrity in logs **Hint:** Think about the core metrics for service health. ### 18. What is a USE metric (Utilization, Saturation, Errors)? - A framework for monitoring hardware resource health - A method for calculating user engagement rates - A strategy for optimizing cloud computing costs - A protocol for encrypting telemetry data in transit **Hint:** Think about infrastructure health metrics. ### 19. What is alerting fatigue, and how do you prevent it? - Operational burnout from high volumes of noise - System degradation caused by frequent health checks - The loss of data when an alerting tool fails - A delay in notification delivery during outages **Hint:** Think about too many false alarms from alerts. ### 20. What is a runbook in observability? - A guide containing procedures for resolving incidents - A chronological log of all past system failures - A configuration script for automated cloud deployments - A database index of all available system metrics **Hint:** Think about documentation for responding to alerts. ### 21. What is MTTR (Mean Time To Recover)? - The average time taken to restore service after failure - The typical duration between two separate outages - The time required to detect that a problem exists - The total uptime divided by the number of users **Hint:** Think about how fast you can fix an incident. ### 22. What is a correlation ID in observability? - A unique value used to tag related telemetry data - A statistical score measuring metric relationships - A password used to access restricted monitoring tools - A version number for application deployment tracking **Hint:** Think about linking logs across requests. ### 23. What is log aggregation? - Centralizing logs from various sources for analysis - Compressing old log files to save storage space - The process of deleting duplicate error messages - Converting unstructured text into numerical metrics **Hint:** Think about collecting logs from multiple sources. ### 24. What is flame graph visualization? - A chart visualizing code execution and CPU usage - A real-time map of global network traffic spikes - A heat map showing server room temperature data - A trend line showing the growth of log storage **Hint:** Think about seeing where time is spent in a profile. ### 25. What is the relationship between observability and monitoring? - Monitoring tracks knowns; observability probes unknowns - Observability is the tool; monitoring is the data - They are identical terms used by different vendors - Monitoring is for apps; observability is for hardware **Hint:** Think about monitoring vs. the deeper investigation. ### 26. What is OpenTelemetry (OTel)? - A vendor-neutral standard for telemetry collection - A commercial SaaS platform for metric storage - A specialized database for high-cardinality logs - A security protocol for monitoring user behavior **Hint:** Think about standardized instrumentation across languages. ### 27. What is continuous profiling in observability? - Always-on analysis of application resource usage - A one-time test performed before a software release - The process of constantly updating user permissions - A method for real-time monitoring of SQL queries **Hint:** Think about always-on performance monitoring. ### 28. What is observability-driven development (ODD)? - Designing systems with instrumentation as a priority - A practice of debugging only using visual dashboards - The requirement to use only open-source monitoring - Automated code generation based on system metrics **Hint:** Think about building systems with observability from the start. ### 29. What is data retention policy in observability? - Rules defining the lifespan of stored telemetry data - The encryption standard used for data at rest - A legal requirement to never delete application logs - The speed at which data is written to a database **Hint:** Think about how long to keep observability data. ### 30. What is alert routing and escalation policy? - Rules that direct alerts to the correct personnel - A method for automatically fixing system errors - The physical network path taken by alert packets - A limit on the number of alerts sent per hour **Hint:** Think about directing alerts to right people. ### 31. What is observability for databases? - Monitoring internal database health and query execution - Performing regular backups of relational tables - Restricting access to the database using firewall rules - The process of normalizing data to reduce redundancy **Hint:** Think about monitoring query performance and health. ### 32. What is observability cost optimization? - Managing telemetry volume to control expenses - Selecting the cheapest monitoring vendor available - Removing all logs to eliminate storage overhead - Moving all monitoring data to local on-prem servers **Hint:** Think about reducing observability tool spending.