Introduction
GreenSlope is Auto-SRE for teams too small to hire one. You instrument your services with standard OpenTelemetry, point the exporter at our endpoint, and we do the rest — release attribution, SLO burn-rate alerting, the Doctor page, and the incident loop in Slack.
These docs are the hands-on companion to the product. They assume you can read code and follow a setup; they do not assume prior OpenTelemetry or SRE experience. First-time-OTel readers are a first-class audience, and every piece of jargon is explained the first time it appears.
Where to start
- Quickstart — pick your stack and get a trace flowing in under five minutes.
- Concepts — the model behind spans, releases, change events, and burn-rate alerts. Read this if you've never run OpenTelemetry before.
- SDK setup — deeper-than-quickstart install: edge routes, auto-instrumentation, sampling, and the resource attributes we require.
- Integrations — Slack, Vercel, GitHub, Twilio, email, and generic webhooks.
What's in V1
V1 is OpenTelemetry-only. There is no GreenSlope-branded SDK to install — you use the standard OTel SDK for your language and set three resource attributes so we can tie traces back to releases. That choice means setup is slightly more manual than a single-package install, and in exchange you keep full control of your telemetry pipeline.
The following are not in V1 and are not documented as present:
- Ingest-side PII redaction (short retention is the residual mitigation).
- One-click programmatic rollback (V1 is suggest + deep-link to Vercel).
- Change sources beyond Vercel and GitHub.
- SAML, DB-per-tenant, or a customer-facing audit-log UI.
- SOC 2 or ISO 27001 — planned post-V1 on commercial trigger.
See Security and data handling for the specifics.
How we treat these docs
We treat docs as a shipping product. Every SDK setup page is CI-tested against an example app. The API reference is generated from the OpenAPI schema, not hand-written. If something here is wrong or missing, email support@greenslope.io — a support answer that isn't already in docs is a docs bug.