Skip to main content

Overview

Astra is SkySignal's AI DevOps agent. It reads your traces, finds the real bug, and opens a pull request with a fix and a test — on a branch, ready for review.

Astra turns the telemetry you already collect into executed work. Instead of surfacing a slow method or a failing error and leaving the next step to you, it takes the next step: reads the relevant code, writes the change, runs the tests, and files the PR.

How Astra Works​

Every Astra job follows the same four-stage pipeline:

  1. Analyze — Astra reads the SkySignal trace, error context, and Mongo query plan for the issue.
  2. Fetch code — Using the GitHub App, Astra checks out the site's configured branch and pulls the relevant files.
  3. Fix — Astra generates a patch. Where applicable, it also writes a regression test.
  4. Test & PR — Astra runs the test suite (if enabled), pushes to a branch, and opens a pull request against the configured base branch.

You can watch each stage in real time from the AI DevOps tab on any site — status dots update as the job moves through queued → analyzing → fetching_code → fixing → testing → awaiting_approval → pr_created.

What Astra Fixes​

Astra runs one of eight job types depending on what triggered it:

Job TypeWhat It Fixes
Error FixUncaught exceptions surfaced in the Errors tab
N+1 FixMethod calls making the same query in a loop
IndexMissing indexes flagged by COLLSCAN warnings
Query OptimizationSlow aggregation pipelines and inefficient query shapes
Publication OptimizationOver-fetching pubs missing field projections
API MigrationDeprecated sync Meteor APIs (e.g. Meteor.call → Meteor.callAsync)
Vulnerability FixHigh/critical npm audit findings
General OptimizationAd-hoc performance work triggered from a metric anomaly

See the Job Types reference for examples of each.

What Astra Will Not Do​

Astra is designed to be a trustworthy contributor — not a fire-and-forget automation. By default:

  • Astra never merges its own PRs. Every change goes through your normal review workflow on GitHub.
  • Astra never pushes to your base branch. Every fix lands on a new branch (e.g. astra/error-fix-abc123).
  • Astra respects branch protection. If a required check fails, the PR stays in draft.
  • You can gate PR creation behind human approval. The Require Approval toggle holds jobs at awaiting_approval until you confirm.
  • You can exclude errors by regex (e.g. timeout|ECONNREFUSED) so Astra never wastes credits on issues you're already tracking separately.
  • You can restrict which job types run automatically. For example, allow error_fix and vulnerability_fix but keep performance work manual.
Start with manual triggering

When onboarding a site, leave Auto-Trigger off. Fire jobs manually from the Errors, Methods, Database, or System tabs for a week or two to build trust with Astra's output, then turn on auto-trigger once you know the kinds of PRs you want it filing.

How Astra Fits with SkySignal APM​

Astra is an add-on to the SkySignal Pro plan. It reuses every signal the APM platform already collects:

  • Errors tab → error_fix jobs
  • Methods tab → n1_optimization, API migration jobs
  • Database tab → index_recommendation, query_optimization jobs
  • System tab → Code Health → publication_optimization, deprecated_api_migration jobs
  • System tab → Security → vulnerability_fix jobs

Nothing new needs to be instrumented. If your site is already reporting to SkySignal, Astra has what it needs.

Pricing​

Astra is priced per site at $100/month, including $50 in Astra credits. Credits are consumed by every job based on complexity (model tokens + compute) — including jobs you cancel, jobs that fail, and PRs you reject. Usage beyond the included credits is billed on a per-use basis.

See the pricing page for the latest details.

Next Steps​