What is the difference between a page, a ticket, and a dashboard signal? [Advanced]
Answer
A page is for urgent human action now, a ticket is for non-urgent work that should be tracked, and a dashboard signal is context for investigation or review. Mixing these creates fatigue and poor prioritization.
Technical explanation
Pages should be rare, actionable, and user-impacting or immediately risk-bearing.
Tickets are appropriate for capacity trends, flaky jobs, low-severity policy violations, or slow error-budget burn.
Dashboard signals can be useful without triggering workflow, such as dependency latency trends or deploy markers.
Hands-on example
Example: 20x SLO burn for checkout = page. Disk projected full in seven days = ticket. CPU at 70 percent during expected peak = dashboard signal. One failed synthetic probe from one region for one minute = dashboard or warning, not a page.
Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.
More Observability interview questions
- What is observability, and how is it different from traditional monitoring? [Basic]
- What are the three pillars of observability (metrics, logs, traces)? [Basic]
- What is the difference between monitoring and observability in practice? [Basic]
- What are the four golden signals of monitoring? [Basic]
- What is the difference between the USE method and the RED method? [Basic]
- When would you use the USE method versus the RED method? [Basic]
- What is an SLI, an SLO, and an SLA, and how do they relate? [Basic]
- How do you choose good SLIs for a service? [Basic]