Introduction

GreenSlope is Auto-SRE for small teams: deploy-aware error tracking, AI-assisted triage, Slack incident loops, and OpenTelemetry SLOs.

These docs are the hands-on companion to the product. They focus on what you need to evaluate GreenSlope at launch: send traces, connect the core integrations, troubleshoot setup, and understand how data is handled.

Where to start

• Quickstart: choose Next.js or Node.js and send your first trace.
• OpenTelemetry setup: endpoints, headers, resource attributes, sampling, and traces-only boundaries.
• Integrations: Vercel, GitHub, and Slack.
• Troubleshooting: common setup failures.
• Security and data handling: what telemetry may contain, retention, region, and support boundaries.

What is currently supported

GreenSlope currently ingests OpenTelemetry traces. Do not configure logs or metrics exporters for GreenSlope yet.

At launch, the core setup path is:

1. Instrument a service with the standard OpenTelemetry SDK.
2. Add the required GreenSlope release attributes.
3. Export traces to GreenSlope's OTLP endpoint.
4. Connect GitHub and/or Vercel for release context.
5. Connect Slack for the incident loop.

GreenSlope does not currently provide a GreenSlope-branded SDK, ingest-side PII redaction, SAML/SSO, a public status page, or SOC 2 / ISO 27001 attestations. Contact us if one of those blocks your evaluation.

Docs feedback

If something here is wrong or missing, email

support [at] greenslope [dot] io. A support answer that isn't already in docs is a docs bug.