CoreQ Academy3.1 Given a scenario, configure appropriate resources to achieve observability.
Observability lets you understand what a system is doing from the outside, using logs, metrics and traces, and act quickly through alerts.
Logging
- Collection
- Gathering logs from services, hosts and cloud control planes (e.g. audit trails).
- Aggregation
- Centralising logs in one searchable place with consistent formats and timestamps.
- Retention
- Keeping logs for the period required by policy and law, then deleting them.
Tracing and monitoring
- Tracing
- Following a single request across services to find where time is spent or errors occur.
- Monitoring
- Continuously watching system health.
- Metrics
- Numeric measurements over time: CPU, latency, error rate, queue depth.
Alerting
- Triage
- Assessing an alert's severity and deciding who handles it.
- Response
- The actions taken to resolve the issue, ideally guided by runbooks.
Check your understanding
Loading quiz…
Original CoreQ Academy material, mapped to objective 3.1 of the publicly available CompTIA Cloud+ CV0-004 exam objectives (Exam objectives V4, document version 5.0). Not affiliated with or endorsed by CompTIA. Contains no exam questions.