BetishOps
Controlled reading / Context / Completeness

Evidence starts at the source.

Processes, jobs, errors, queues, sessions and resources: discover what each source adds to operational investigation.

12 source groups

ST22

ABAP errors

Timestamp, program, error class and system context.

Which error appeared, and when?

SM37

Background jobs

Status, start, end and job duration.

Which jobs stopped or changed duration?

SM13

Update requests

Update-request status and context.

Are update requests pending or interrupted?

SM58

tRFC communication

Destination, status and age of pending units.

Where is pending work accumulating?

SMQ1 / SMQ2

qRFC queues

Direction, queue name, status and observed volume.

Is an inbound or outbound queue growing?

SM66

Work processes

Process activity and state by context.

How is processing activity changing?

SMLG

Logon groups

Groups, instances and distribution observations.

How is the observed load distributed?

ST06

Host resources

CPU, memory and available host measurements.

Which resource changed before degradation?

AL08

Sessions

Sessions and instances with observation scope and time.

Which activity pattern coincides with the event?

DBACOCKPIT

Database

Inventory and metrics according to the available interface and permissions.

What changed in database capacity or behavior?

SAP BTP

Subaccounts and services

Identity, resources and observations for authorized services.

Which cloud service and context need attention?

Integration Suite

Integration flows

Message status, time and technical identifiers.

Which messages fail, and how do they evolve?

This catalog presents observation domains. Available fields and history depend on the source interface, version, retention and authorization. A transaction name does not imply universal availability or authorize writes.

Anatomy of an observation

A record is more than a row.

Illustrative scenario · No customer data
Demo organizationDEMO-ERPClient 100
FieldIllustrative valueWhy it matters
SourceSMQ1Identifies the observation being read.
QueueDEMO_OUTBOUND_01Preserves a technical identity, not an ambiguous alias.
Pending records184A volume measurement at the observation point.
Oldest age27 minutesDistinguishes accumulated volume from waiting time.
Observation09:12 / E-103Links the record to its time and evidence.
Coverage11 of 12 intervalsAvoids confusing the latest valid result with a complete period.
Explicit time semantics

History depends on the source.

Current state

An observation describes the time of reading. Its evolution is built by retaining successive observations.

Native history

Retrospective windows use only what the source exposes and retains. They do not reconstruct a past that was never observed.

Pagination without hidden losses

Collection retains its scope and progress. Reaching a technical limit does not make a partial result complete.

One result, multiple consumers

History, indicators and investigation use retained evidence instead of requesting another extraction independently.

01 / Narrated walkthrough

From extraction to history.

1:04 · English narration
Captions available

Illustrative visual demonstration. A connected story using example data; not a recording of a customer environment.

Download video ↓
Read the full transcript

BetishOps. Your SAP operations, explained with evidence. An alert reveals a symptom. Understanding it requires knowing what happened, when it changed, and which observations support it. This walkthrough uses illustrative data.

Observation starts at the source: processes, queues, jobs, sessions, and resources. Each extraction retains its context and observation time. Jobs organize collection, while coverage separates a complete observation from information that is still missing.

History turns those observations into a sequence. In this example, the queue grows from twelve to one hundred and eighty-four pending records. Daily close brings the period's evidence together and shows its coverage, without hiding missing intervals.

Indicators connect a measurement to a question: how much did the queue grow, how long has the oldest record been waiting, and what changed since the previous period? From source to history, and from an indicator to its evidence. BetishOps: fewer isolated signals, clearer decisions.

From your question to a demonstration

Let’s explore your operational context.

Let’s discuss your sources, your questions and the outcome you need. No credentials or sensitive data required.

Request a demonstration