Reliability, SLO and observability
SLI specification, SLO target, evaluation window, error budget and reaction rules. Metric definitions and observations are reused from the analytics foundation.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseTEC
- Industry
- Cross-industry
- Tags
- EM-TEC-06W1subjectSLISpecificationSLOSLOEvaluationErrorBudgetPolicyObservabilityBinding
What it is Filled
SLI specification, SLO target, evaluation window, error budget and reaction rules. Metric definitions and observations are reused from the analytics foundation.
Why it exists Filled
SLI specification, SLO target, evaluation window, error budget and reaction rules. Metric definitions and observations are reused from the analytics foundation.
Distinguishing features Derived, awaiting review
- An SLO specifies an SLI, a target and a window
- No data does not equal met
- SLA and SLO have different grounds
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: 99.9% on a product card with no window and no measurement method is declared proven reliability.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
CTO / CIO / владелец сервиса
Master systems
- Каталог ПО
- Git
- CI/CD
- CMDB
- observability
Links to other meta-models Filled
neighbor
- EM-PRD-02
- EM-TEC-04
references
- WM-SFT-016 - conceptual-candidate
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Derived, awaiting review
- SLISpecification
- SLO
- SLOEvaluation
- ErrorBudgetPolicy
- ObservabilityBinding
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Sources Filled
- AISMM/WM-SFT and ArchiMate: product, system and architecture
- CSDM: business application, service and runtime instance
- SPDX/OpenTelemetry/Google SRE: delivery, observation and reliability; choose by boundary
Open questions
- How to define a useful outcome for the user?
- Where does the SLO live: service, journey, system or instance?
- How to treat telemetry gaps and a window change?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-tec-06/brief.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.