Skip to content

Services and service map

Use Services to see what has sent telemetry into a project. Use Service Map to inspect rolled-up dependencies between services.

Open Services to see catalog entries created from service.name. Oriel creates a service catalog row on first ingest for each project and service name.

Services screen showing catalog entries, signal presence, owners, repository links, and service health columns.

Service catalog fields include:

  • Service name
  • Owner
  • Repository URL
  • Description
  • Signal presence derived from telemetry

Open Service Map to inspect rolled-up service edges. The worker role evaluates service-map rollups on a fixed cadence and backfills recent completed hours.

Service Map screen showing rolled-up dependencies between services with calls, errors, and latency.

Reading services requires projects:read and telemetry views require telemetry:query. Editing service catalog metadata requires services:manage.

  • From a service row, open traces or logs scoped to that service.
  • From a service-map edge, inspect calls, errors, and p95 latency.
  • Use missing signal presence to find instrumentation gaps.
  • Add owner and repo metadata to make incident triage faster.