Topic lessonTopic: AWS and SQL Server telemetry and audit
Choose metrics, logs and traces for AWS and SQL Server monitoring
Break a report of slowness into scale, failed operations and time spent waiting. Choose the next evidence source for an API that connects to SQL Server.
Choose the next evidence source for an API that connects to SQL Server.
This exercise uses fictional evidence and makes no changes in a live environment.
Use the signal that answers the question
Metrics describe trends, logs capture individual outcomes and traces show intervals within a request. Audit records help identify who changed a setting.
- Trend → RequestFix the time window
- Request → IntervalMatch identifiers
- Interval → ChangeTest a hypothesis
- Trend
- Identify affected intervals
- Request
- Find the failing operation
- Interval
- Measure database-related waits
- Change
- Check the audit record
A synthetic order API is slow for ten minutes
| Signal | Observation | Next decision |
|---|---|---|
| Metrics | p95 rises from 180 to 900 ms | Fix the affected window |
| Application logs | Connection retries on the request | Identify the request |
| Trace | 740 ms before database work | Inspect each interval |
| Audit record | A configuration changed | Reconcile time and request conditions |
Timing alone cannot tell you which change caused the difference. Match a representative request and its conditions.
Evidence for the decision
Define coverage Record collection scope, aggregation interval and unobserved requests.
Match the request Use request IDs or trace IDs to distinguish separate attempts.
Measure after correction Compare success, waits and retries under equivalent traffic and conditions.
Check your decision
Choose an option to see the result and explanation.
Check, then explain in your own words
- State a measurable question.
- Choose the appropriate signal.
- Correlate the request and actual change.
Check your understanding: Do untraced requests count as successful?
Use logs and metrics and record the gaps.
Signal coverage and workload outcomes are separate.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
- Develop application telemetryChecked:
Scope and conditionsUsing observability to understand operational state.
Used in this lessonUse the signal that answers the question A synthetic order API is slow for ten minutes Evidence for the decision