Integrations

One install to start. Everything else is optional.

The cluster agent gives sudoSRE everything it needs. Other tools add detail, like the commit behind a deploy, and none of them is required.

Status is marked per item. First is the core install. Next follows in build order. Planned is on the roadmap and not built yet. Naming a tool here describes what sudoSRE reads from, not a partnership.

01

Core: the cluster agent

One Helm install. This is all sudoSRE needs to build the Prod Map, detect bad changes, and investigate them.

  • Traffic via eBPF

    Requests, errors, and latency between services, no code changes

    first

  • Kubernetes

    Rollouts, config and secret changes, scaling, events

    first

  • Helm

    Release history and upgrades

    first

  • Slack

    Findings, approvals, and pages

    first

  • Bring your own model

    Any provider, your key, your account

    first

02

Code and delivery

Optional. Adds the commit and diff behind a change, so a finding can point at the exact line.

  • GitHub

    Commits, pull requests, diffs

    ◐ next

  • Argo CD

    Sync history

    ◐ next

  • GitLab

    Merge requests, pipelines

    planned

  • Flux

    Reconciliation history

    planned

  • Bitbucket

    Commits and diffs

    planned

03

Monitoring you already run

Optional. sudoSRE reads metrics you already collect for extra context, where they already live.

  • Prometheus

    Metrics and recording rules

    ◐ next

  • Datadog

    Metrics and monitors

    planned

  • Grafana

    Dashboards and alerts

    planned

  • Amazon CloudWatch

    Metrics and alarms

    planned

04

Cloud and infrastructure

Optional. Changes made outside the cluster, such as a security group edit or a database parameter change.

  • AWS CloudTrail

    API changes to cloud resources

    planned

  • GCP Audit Logs

    API changes to cloud resources

    planned

  • Azure Activity Log

    API changes to cloud resources

    planned

  • Terraform

    Applies and state changes

    planned

05

Paging

Optional. sudoSRE pages through Slack on its own. Forward to an existing on-call tool if your team uses one.

  • PagerDuty

    Forward pages

    planned

  • Opsgenie

    Forward pages

    planned

  • Microsoft Teams

    Findings and approvals

    planned

Missing the one you need?

Design partners decide what gets built next. Tell us what you run and we will say plainly whether sudoSRE can read it yet.

Request early accessHow it works