Connect your systems.

Connect the telemetry and repos you want Perfloop to use, with access to private packages when builds need them. Each guide covers setup, required permissions, and the data Perfloop reads and stores. See Security for how we handle your data.

Telemetry sources

• Axiom Query aggregates from the Axiom datasets and saved views you choose.

• Prometheus® Read metrics from your Prometheus endpoint, filtered by service or environment.

• VictoriaMetrics Query metrics from a single-node or cluster deployment.

• Pyroscope Read profiles for the services you select in Pyroscope.

• Loki Query logs and log metrics from selected Loki streams.

• Google Cloud Profiler Read profiles from one Google Cloud project with a dedicated service account.

• Datadog Connect metrics and log aggregates. Use API keys to add Go CPU profiles.

• Polar Signals Read profiles for selected workloads in a Polar Signals project.

• Grafana Connect Prometheus, Loki, or Pyroscope through your Grafana stack.

• Grafana Cloud Authorize access to a Prometheus or Loki data source in Grafana Cloud.

A source inside your network, which the internet cannot reach, connects through the Perfloop relay, a program you run there. It reads Prometheus® and VictoriaMetrics for metrics, Loki for logs, and Go pprof for live profiles of Go processes.

Code hosts

• GitHub Connect selected repos through the Perfloop GitHub App.

• GitHub Enterprise Server Connect selected repos through a GitHub App you create on your server.

• GitLab Connect selected projects on GitLab.com or a self-managed server.

A code-host account can connect to several Perfloop workspaces. An Admin connects it separately in each workspace and selects its repos. Changing one workspace's connection or selection leaves the others unchanged. Removing access at the code host can affect every workspace that uses it.

Each code-host account can earn the signup free budget once. Connecting it to another workspace or reconnecting it does not grant another free budget.

Private packages

GitHub Packages uses a separate package-read credential. The guide covers least-privilege access, Setup and token removal.

Slack

An admin connects Slack from Setup to talk with Perfloop about Cases and work. Slack does not need a telemetry connection. Scheduling workspace deletion stops its conversations. It does not remove messages already held by Slack.

Each member links their own Perfloop account before starting a conversation. If the account-link message does not appear, open https://app.perfloop.ai/t/WORKSPACE/slack/link. Replace WORKSPACE with the name from your workspace URL. After linking, send Perfloop a new DM or mention @Perfloop in a channel.

A linked Admin chooses an Inbox channel in Setup → Slack Agent. Change accepts a channel link or ID. Join the channel and invite @Perfloop before saving it. Two or more pending items arrive in one summary. Open Inbox to read and decide each request. Turning notices off leaves the Slack connection and conversations in place.

Need another source? hello@perfloop.ai