Decision map
Observability
Which operational or behavioral signal answers the team's current question without collapsing distinct telemetry and analytics jobs?
Recommendation
Start with Error Monitoring
Engineering, reliability, product, and growth teams choosing operational telemetry, external availability checks, behavioral analytics, or qualitative session playback.
Scope
Use this boundary to avoid solving adjacent problems in the wrong layer.
Included
- Issue-centric exception and crash grouping
- Centralized log collection, retention, search, and operations
- Application tracing, transaction performance, and service diagnostics
- Host, VM, container, Kubernetes, cloud-resource, process, and system metrics
- External availability and synthetic checks
- Product interaction and identity analysis
- Web acquisition and traffic analysis
- Privacy-controlled individual session replay
Excluded
- Product-facing accountable action ledgers, which belong to Security Audit Logs
- Feature rollout control, which belongs to Feature Flags
- Incident status communication
- LLM and agent-specific traces, evaluations, and cost semantics, which belong to AI Observability
- Feature Monitoring as an independent Task
Important tools
These tools represent distinct routes inside this decision area; open the relevant Task before treating any as a default.
Decision sequence
Make the foundational ownership decisions before adding specialized capabilities.
Is the question about system operation or user behavior?
Separate operational telemetry from behavioral analytics before comparing suites that may expose both.
Error Monitoring Application Logging Application Performance Monitoring Infrastructure Monitoring Product Analytics
Is the operational unit a grouped failure, a searchable event, an instrumented request path, or an external symptom?
Choose the signal that matches triage, investigation, transaction diagnosis, or availability verification.
Error Monitoring Application Logging Application Performance Monitoring Infrastructure Monitoring Uptime & Synthetic Monitoring
Is the behavioral unit an identified product event or an acquisition and traffic session?
Product Analytics centers on product interaction and identity; Web Analytics centers on source, medium, campaign, and site traffic.
Does aggregate data leave an individual interaction unexplained?
Evaluate Session Replay only when qualitative playback is justified and consent, masking, retention, and access constraints are defined.
Decision groups
Each Task owns a distinct user decision rather than a product feature label.
System health and failure signals
These Tasks choose grouped failures, searchable event records, application request traces and performance, or external availability symptoms.
User behavior and experience signals
These Tasks choose product-event analysis, acquisition and site measurement, or qualitative playback of individual sessions.
Common confusions
These boundaries prevent adjacent Tasks from collapsing into one generic shortlist.
- Error Monitoring and Logging are treated as interchangeable event stores.
- Error Monitoring groups similar exception events into issues; Logging preserves and queries a broader event history.
- Uptime Monitoring and Application Performance Monitoring are treated as the same health signal.
- Uptime Monitoring executes black-box checks against externally visible behavior; APM instruments application internals and request paths.
- Application Performance Monitoring and Infrastructure Monitoring are treated as one generic monitoring decision.
- APM owns application request and service behavior; Infrastructure Monitoring owns host, container, cluster, cloud-resource, process, and system metrics.
- Product Analytics and Web Analytics are treated as one generic analytics decision.
- Product Analytics centers on product events and identity; Web Analytics centers on acquisition, traffic, source, medium, and campaign.
- Feature Monitoring is treated as a retained independent Task.
- Adoption belongs to Product Analytics, rollout control to Feature Flags, and failures or performance to Error Monitoring and Application Performance Monitoring.
What to defer
Do not add specialized identity systems before the product has the requirement they serve.
Aggregate events and operational telemetry already answer the question without individual interaction playback.
Replay adds privacy, masking, retention, storage, and access-control obligations.
The product has no meaningful website acquisition, referrer, or campaign decision.
Product-event analysis can proceed without adding a separate acquisition and traffic measurement surface.
The selected hosting platform already exposes sufficient resource health for the current workload and no independent metric, topology, retention, or alerting requirement exists.
A separate infrastructure metrics platform should follow a concrete resource-health and operating-ownership need.
Authoritative resources
Standards and primary documentation supporting the Category boundaries.
Sources
Claim-level references used for this decision map.
- 1Signals
OpenTelemetry · Accessed Official
- 2Grouping Issues
Sentry · Accessed Official
- 3Guide to Computer Security Log Management
NIST · Accessed Official
- 4Trace Context
W3C · Accessed Official
- 5Synthetic Monitoring introduction
Grafana Labs · Accessed Official
- 6Set up events
Google Analytics · Accessed Official
- 7Send User IDs
Google Analytics · Accessed Official
- 8Traffic-source dimensions
Google Analytics · Accessed Official
- 9Frequently asked questions
Microsoft Clarity · Accessed Official
- 10Data retention
Microsoft Clarity · Accessed Official
- 11Prometheus overview
Prometheus · Accessed Official