Skip to contentVibraUI
6 pagesopens at /engineering

Engineering

Deploys, uptime, incidents, alerts and logs — what is broken, since when, and who has it — and the public status page.

Preview
/engineering

Install

The whole dashboard — every page under one sidebar, the sample data they read — is one command. Or take a page at a time: each one brings the sidebar with it.

npx shadcn@latest add @vibra/engineering

Widgets

Single cards cut from these pages, each installed on its own.

  • The Engineering headline card
    npx shadcn@latest add @vibra/widget-engineering-overview-engineering-stats
    From Engineering dashboard

    Engineering headline

    Deploy frequency, lead time, change failure rate and time to restore over the last thirty days, a thin median saying how many incidents it stands on; reads engineeringStats().

  • The Deploy frequency card
    npx shadcn@latest add @vibra/widget-engineering-overview-deploy-frequency
    From Engineering dashboard

    Deploy frequency

    Production deploys a week over the last twelve, the ones that shipped clean against the ones that failed on the way out; reads deploysByWeek().

  • The Production timeline card
    npx shadcn@latest add @vibra/widget-engineering-overview-deploys-timeline
    From Engineering dashboard

    Production timeline

    The last six production releases, newest first, each with its commit, branch, author, how long it ran and how it ended; reads productionTimeline().

  • The Recent deployments card
    npx shadcn@latest add @vibra/widget-engineering-overview-recent-deployments
    From Engineering dashboard

    Recent deployments

    The last eight deploys to any environment, with the commit, branch, status, author, pipeline time and when each started; reads recentDeployments().

  • The Open pull requests card
    npx shadcn@latest add @vibra/widget-engineering-overview-open-prs
    From Engineering dashboard

    Open pull requests

    What is waiting for review, oldest first, each with its checks, author, size and how many approvals it has; reads openPullRequests().

  • The Request latency card
    npx shadcn@latest add @vibra/widget-engineering-monitoring-latency-chart
    From Monitoring console

    Request latency

    p50, p95 and p99 by hour of day over every timed request in the gateway log, and the band p95 stayed inside; reads latency().

  • The Cluster load card
    npx shadcn@latest add @vibra/widget-engineering-monitoring-resource-gauges
    From Monitoring console

    Cluster load

    CPU, memory and disk across the ingest fleet right now, each gauge turning at its own warning and danger lines; reads resources().

  • The Uptime card
    npx shadcn@latest add @vibra/widget-engineering-monitoring-uptime-panel
    From Monitoring console

    Uptime

    Ninety days, a bar a day, for the three services that had the worst of it, each with the availability its probes measured; reads uptime().

  • The Regions card
    npx shadcn@latest add @vibra/widget-engineering-monitoring-region-list
    From Monitoring console

    Regions

    Where traffic is served from, the troubled regions first, each with how many services it runs and its worst uptime today; reads regions().

  • The Errors by hour card
    npx shadcn@latest add @vibra/widget-engineering-monitoring-error-heatmap
    From Monitoring console

    Errors by hour

    The errors the gateway logged by weekday and hour, UTC, and the worst block of the week; reads errorGrid().

  • The Incidents card
    npx shadcn@latest add @vibra/widget-engineering-monitoring-incidents-panel
    From Monitoring console

    Incidents

    Open incidents first, then the ones that closed most recently, each with its severity, stage and the services it hit; reads incidents().

  • The Gateway log card
    npx shadcn@latest add @vibra/widget-engineering-monitoring-service-logs
    From Monitoring console

    Gateway log

    The tail of the gateway's stream, newest at the bottom, filterable by level and text and following new lines; reads logLines().

  • The On call card
    npx shadcn@latest add @vibra/widget-engineering-incidents-on-call-card
    From Incident console

    On call

    Who holds the pager — the primary, the secondary and the escalation — and how many incidents each has commanded this quarter; reads onCall().

  • The Service availability card
    npx shadcn@latest add @vibra/widget-engineering-status-service-uptime
    From Public status page

    Service availability

    Every service with its state now and ninety days of availability behind it, a strip each over one shared date legend; reads services().

  • The Past incidents card
    npx shadcn@latest add @vibra/widget-engineering-status-incident-history
    From Public status page

    Past incidents

    The last fourteen days of closed incidents with the updates their responders published, each run of quiet days folded into one line; reads incidentHistory().

Reads from db

Every figure on these pages is read from these repositories of the sample store. Swap one for your own API and each page that reads it follows.

  • db.alerts
  • db.deployments
  • db.incidents
  • db.logEntries
  • db.members
  • db.notifications
  • db.services