# Lexicon terms whose category is observability-auditability-traceability

> 59 records

This index as JSON: https://banes-lab.com/json/api/facets/lexicon/category/observability-auditability-traceability

## Entries

- [Cost/Noise](https://banes-lab.com/records/lexicon/cost-noise.md): The degree to which collecting more telemetry adds cost and noise that can obscure the signals that matter.
- [Incident Diagnosis](https://banes-lab.com/records/lexicon/incident-diagnosis.md): The ability to diagnose the cause of an incident from a system's observable signals.
- [Logs](https://banes-lab.com/records/lexicon/logs.md): A record of discrete, timestamped events a system emits about what it did.
- [Traces](https://banes-lab.com/records/lexicon/traces.md): A record of the path and timing of a request as it moves through a system's components.
- [Incident Analysis](https://banes-lab.com/records/lexicon/incident-analysis.md): The ability to reconstruct and analyze an incident from the events a system logged.
- [Noise/Personal Data Leakage](https://banes-lab.com/records/lexicon/noise-personal-data-leakage.md): The degree to which verbose logging adds noise and risks leaking personal or sensitive data.
- [Structured Events](https://banes-lab.com/records/lexicon/structured-events.md): Log entries emitted as structured, machine-parsable records rather than free-form text.
- [Alert Noise](https://banes-lab.com/records/lexicon/alert-noise.md): The degree to which monitoring many signals generates alerts that drown out the meaningful ones.
- [Blind Operation](https://banes-lab.com/records/lexicon/blind-operation.md): Running a system in production with no monitoring, so problems are noticed only when users report them.
- [Failure Detection](https://banes-lab.com/records/lexicon/failure-detection.md): The ability to detect that a system has failed or degraded by watching its monitored signals.
- [Alert Fatigue](https://banes-lab.com/records/lexicon/alert-fatigue.md): The degree to which too many alerts desensitize responders, so the ones that matter are ignored.
- [Incident Response](https://banes-lab.com/records/lexicon/incident-response.md): Detecting, triaging, and resolving an operational incident once an alert fires.
- [Timely Intervention](https://banes-lab.com/records/lexicon/timely-intervention.md): The ability to intervene on a problem quickly by being alerted the moment it arises.
- [Accountability](https://banes-lab.com/records/lexicon/accountability.md): The ability to attribute every consequential action to the actor responsible for it.
- [Opaque Mutation](https://banes-lab.com/records/lexicon/opaque-mutation.md): Changing state with no record of who changed what or when, so the change cannot be audited.
- [Storage/Privacy](https://banes-lab.com/records/lexicon/storage-privacy.md): The degree to which retaining a full audit history grows storage and raises privacy concerns.
- [Action](https://banes-lab.com/records/lexicon/action.md): A field of an audit record identifying the operation that was performed.
- [Actor](https://banes-lab.com/records/lexicon/actor.md): A field of an audit record identifying who or what performed an action.
- [Forensics](https://banes-lab.com/records/lexicon/forensics.md): The ability to reconstruct after the fact what happened from an immutable audit record.
- [Privacy](https://banes-lab.com/records/lexicon/privacy.md): The degree to which a system limits the collection and exposure of personal or sensitive information.
- [Target](https://banes-lab.com/records/lexicon/target.md): A field of an audit record identifying the resource an action was performed on.
- [Timestamp](https://banes-lab.com/records/lexicon/timestamp.md): A field of an audit record marking when an action occurred.
- [Untracked Mutation](https://banes-lab.com/records/lexicon/untracked-mutation.md): Mutating state without writing an audit entry, so the change leaves no trace.
- [Anonymous Flow](https://banes-lab.com/records/lexicon/anonymous-flow.md): Data or requests flowing through a system with no identifiers, so their path cannot be reconstructed.
- [End-to-End Causality](https://banes-lab.com/records/lexicon/end-to-end-causality.md): The ability to follow a request's cause-and-effect chain across every component it touches.
- [Logs/Traces](https://banes-lab.com/records/lexicon/logs-traces.md): The combined log and trace records that let a request be followed from end to end.
- [Metadata Propagation Overhead](https://banes-lab.com/records/lexicon/metadata-propagation-overhead.md): The degree to which carrying trace metadata through every call adds size and processing cost.
- [Context Propagation](https://banes-lab.com/records/lexicon/context-propagation.md): The requirement that request context be carried across service boundaries so related calls can be correlated.
- [Header/Metadata Management](https://banes-lab.com/records/lexicon/header-metadata-management.md): The degree to which threading correlation identifiers through headers adds handling to every call.
- [Request-Level Traceability](https://banes-lab.com/records/lexicon/request-level-traceability.md): The ability to trace all work belonging to one request by a shared correlation identifier.
- [Uncorrelated Events](https://banes-lab.com/records/lexicon/uncorrelated-events.md): Emitting events with no shared identifier, so those belonging to one request cannot be tied together.
- [Audit Trail](https://banes-lab.com/records/lexicon/audit-trail.md): A chronological record linking each event to the one that caused it.
- [Cause-Effect Reconstruction](https://banes-lab.com/records/lexicon/cause-effect-reconstruction.md): The ability to reconstruct which event triggered which by following causation identifiers.
- [Event Metadata](https://banes-lab.com/records/lexicon/event-metadata.md): Descriptive fields attached to an event, such as its identifiers, timestamps, and causation links.
- [Metadata Verbosity](https://banes-lab.com/records/lexicon/metadata-verbosity.md): The degree to which stamping every event with causation metadata makes the event payload verbose.
- [Unlinked Events](https://banes-lab.com/records/lexicon/unlinked-events.md): Recording events with no link to their cause, so cause-and-effect chains cannot be rebuilt.
- [Latency/Failure Root Cause Analysis](https://banes-lab.com/records/lexicon/latency-failure-root-cause-analysis.md): The ability to pinpoint which service caused a request's latency or failure by tracing it across hops.
- [Opaque Distributed Calls](https://banes-lab.com/records/lexicon/opaque-distributed-calls.md): Calls crossing service boundaries with no tracing, so a request's path and bottlenecks are invisible.
- [Overhead/Sampling](https://banes-lab.com/records/lexicon/overhead-sampling.md): The degree to which tracing every request adds overhead, forcing sampling that can miss rare cases.
- [Trace Context Propagation](https://banes-lab.com/records/lexicon/trace-context-propagation.md): The requirement that trace identifiers be propagated across every hop of a distributed request.
- [Error-Budget Decisions](https://banes-lab.com/records/lexicon/error-budget-decisions.md): The ability to decide how much risk to take by spending against a defined reliability error budget.
- [Feature Velocity](https://banes-lab.com/records/lexicon/feature-velocity.md): The degree to which holding to strict reliability targets limits how fast new features can ship.
- [Vague Reliability Goals](https://banes-lab.com/records/lexicon/vague-reliability-goals.md): Stating reliability aims in vague, unmeasurable terms, so no check can tell whether they are met.
- [At-a-Glance System Health](https://banes-lab.com/records/lexicon/at-a-glance-system-health.md): The ability to see a system's overall health at a glance from a consolidated visual display.
- [Dashboard Sprawl](https://banes-lab.com/records/lexicon/dashboard-sprawl.md): The degree to which unchecked creation of dashboards scatters attention across too many redundant views.
- [Log-Grep-Only Diagnosis](https://banes-lab.com/records/lexicon/log-grep-only-diagnosis.md): Diagnosing problems solely by grepping raw logs, with no aggregated view of system health.
- [Trend Visibility](https://banes-lab.com/records/lexicon/trend-visibility.md): The ability to see how a metric is trending over time from a visualized history.
- [Structured Log](https://banes-lab.com/records/lexicon/structured-log.md): A technique for writing log entries as typed fields, so they are queried by field instead of by text.
- [Trace Span](https://banes-lab.com/records/lexicon/trace-span.md): A technique for recording the start, end and context of an operation as a span within a request's trace.
- [Alert on Critical Failure](https://banes-lab.com/records/lexicon/alert-on-critical-failure.md): A technique for raising an alert with an owner and a severity when a critical path fails.
- [Cardinality Reduction](https://banes-lab.com/records/lexicon/cardinality-reduction.md): A technique for limiting the distinct label values a metric carries, so its storage and queries stay bounded.
- [Sampling and Aggregation](https://banes-lab.com/records/lexicon/sampling-and-aggregation.md): A technique for keeping a representative share of telemetry or a summary of it instead of every event.
- [Runbook Owner](https://banes-lab.com/records/lexicon/runbook-owner.md): A technique for naming the person or team responsible for each alert and its response steps.
- [Causation Tracing](https://banes-lab.com/records/lexicon/causation-tracing.md): A technique for carrying the id of the event or request that caused each effect, so a chain can be followed back.
- [Usage Instrumentation](https://banes-lab.com/records/lexicon/usage-instrumentation.md): A technique for counting calls to a code path in production, so its use is measured before it is removed.
- [Data Change Audit](https://banes-lab.com/records/lexicon/data-change-audit.md): A technique for recording who changed which data, when, and from what value to what value.
- [Execution Log](https://banes-lab.com/records/lexicon/execution-log.md): A technique for recording each step an automated or manual procedure performed and its result.
- [Define Signal Quality](https://banes-lab.com/records/lexicon/define-signal-quality.md): A technique for stating what makes a log, metric or alert useful before it is emitted.
- [Service Level Objectives](https://banes-lab.com/records/lexicon/service-level-objectives.md): A technique for choosing measured indicators of reliability and setting the targets a service must meet on them.