Skip to content

Namespace Projects

A Project is a service.namespace — the boundary that collects and connects related pieces of your software. The Namespace Projects page gives you per-project health and, on drill-in, everything a project is built from. For the full model, see Services and Projects.

Project list

Each Project is a row with a tri-axis health summary — one axis each for spans, logs, and cron — and a per-axis sample count plus a colored error-rate badge (green / yellow / red, tuned by your organization's thresholds). The axes are independent, so a log-only project shows a gray dash on the span axis rather than a misleading 0%, and a project emitting level=error logs won't look healthy just because it has no failing spans. A relative last-seen time sits in the corner.

Header controls let you sort (recently active, alphabetical, highest span error rate, highest log error rate) and pick the time window (presets of 1 / 3 / 7 / 14 / 30 days, or a custom number). Both round-trip through the URL so a sorted, scoped view is shareable.

Project detail

Click a Project to open its hub, which assembles the project's pieces:

  • Services table — a full-width, presence-based list of every entity in the namespace (services plus any graduated databases, caches, and message queues, marked with a type badge). Columns cover Spans, Logs, Crons (each with a sample count and error badge), Metrics, and last-seen. Each row deep-links into the entity's detail on the Services page.
  • External Services — the outbound calls this project makes (dependencies it doesn't own), with kind, instance, call count, and error rate. Each links to a trace search filtered to that dependency.
  • Infrastructure — the hosts this project runs on, each linking to its Host detail.
  • Traces preview and Logs preview — a quick look at the project's recent traces and logs.

The selected Project lives in the URL (?ns=), so a link reopens the same project.

  • Services and Projects — entities, services, external services, and how a Project collects them.
  • Services — the same entities in one global, presence-based catalog.