Services
The Services page is the single catalog of every observed software entity — anything that carries a service.namespace. That includes your instrumented applications and the external software you collect from and have attributed (databases, caches, message queues). If you haven't met the entity vocabulary yet, read Services and Projects first.
The catalog
The landing view is one unified, presence-based table. Every entity appears here regardless of which signals it has — a log-only service, a cron-only job, and a metrics-only database all show up, because the catalog is built from what's actually been seen across spans, logs, crons, and metrics.
Each row shows, per signal axis, a sample count and a colored error-rate badge (green / yellow / red, tuned by your organization's thresholds), plus a Metrics column. Non-service entities carry an inline type badge — Database, Cache, or Message Queue — so a graduated external service is visible at a glance. Plain services have no badge.
A type filter at the top scopes the list: All, Services, Databases, Caches, or Message Queues. There are no separate nav items for databases or caches — they all live here, distinguished by their badge. Changing the filter resets your selection.
Per-entity detail
Click a row to open the entity's detail. The detail is presence-gated: it shows only the sections for the signals that entity actually has, always in the order:
- Traces
- Metrics
- Logs
- Cron
A signal the entity doesn't emit is simply absent — no empty placeholder. The Metrics lens appears for database, cache, and message-queue entities that report metrics. Entities with the same name in different Projects stay distinct, because every detail view is scoped to the entity's namespace.
Related
- Services and Projects — how entities, services, external services, and Projects fit together.
- Namespace Projects — the same entities, grouped by the Project they belong to.
- Traces and Logs — the underlying signals, explorable on their own.