OCI 1Z0-1111-25 Glossary: Key Terms
March 31, 2026
OCI 1Z0-1111-25 glossary of logs, metrics, alarms, tracing, and incident response terms.
Use this glossary to clean up high-confusion OCI observability terms before you go back into mixed sets. On this exam, vocabulary mistakes usually hide a signal-selection or workflow-stage mistake.
High-value terms
| Term |
What it means here |
Why it matters on the exam |
| Alert rule |
the condition set that decides when an operator should be notified |
alert quality is a core tie-break on this exam |
| APM |
application performance monitoring used to inspect application behavior more deeply |
it often wins when the issue is request-path latency, not simple health |
| Log Analytics |
OCI service for analyzing logs at scale and extracting patterns |
this is different from raw log collection |
| Metric |
a numeric measurement collected over time |
metrics are often the best first lane for detection |
| Notification topic |
the routing target used to fan alerts out to subscribers |
routing is not the same as diagnosis |
| Signal quality |
how useful a signal stream is for spotting real issues without excess noise |
strong answers improve quality, not just quantity |
| Telemetry |
operational data emitted so systems can be observed |
telemetry is the raw material, not the final response path |
| Threshold |
the numeric or logical boundary that triggers a response |
weak thresholds create noise or blind spots |
| Trace-style visibility |
request-flow insight that helps explain where time or failure occurred |
traces help localize path-level bottlenecks |
| Visibility gap |
missing or weak operational coverage that slows diagnosis |
many bad answers create or ignore these gaps |
Common confusion pairs
| Pair |
Clean separation |
| Metric vs log |
metrics summarize numeric state over time, logs capture event or message detail |
| Logging vs Log Analytics |
Logging collects and stores events, Log Analytics helps analyze them at scale |
| Monitoring vs APM |
Monitoring tracks broad health, APM goes deeper into application behavior and path performance |
| Collection vs notification |
collection gathers the data, notification routes the alert after conditions are met |
| Noise reduction vs blind spots |
noise reduction lowers unnecessary alerts, blind spots remove needed visibility |
| Threshold vs runbook |
threshold decides when to signal, runbook decides how to act |
| Detection vs diagnosis |
detection proves there is a problem, diagnosis explains what happened |
Fast recall anchors
| If you see… |
Think… |
| service health or breach state |
metric |
| event details and error records |
log |
| request-path latency or bottleneck |
trace or APM |
| who should act next |
notification topic or routing |
If three terms blur together
| Terms |
Short reset |
| metric, log, trace |
metrics detect broad health, logs explain events, traces localize path-level latency |
| logging, log analytics, notifications |
logging stores events, log analytics analyzes them, notifications route action |
| threshold, alert, runbook |
threshold defines condition, alert raises the signal, runbook guides the response |
| telemetry, dashboard, observability |
telemetry is raw data, dashboards present it, observability is the broader ability to detect and explain behavior |
Route misses well
| If you missed because… |
Go next |
| you mixed up signal roles |
FAQ |
| you need fast signal and alert tie-breaks |
Cheat Sheet |
| you need a paced rebuild of the weak lane |
Study Plan |
| you need the official Oracle or OCI source |
Resources |
Revised on Monday, June 15, 2026