Documentation
Connect your CI provider, integrate the public API, and run Exlogare in production.
Start here
New to Exlogare? Begin with the five-minute Getting started guide — it walks you from sign-up to a first RCA in your merge request.
Open Getting startedGetting started
Integrations
- GitLab and Bitbucket webhook mode
Event-driven integration for environments where OAuth is not allowed.
- GitLab, GitHub and Bitbucket OAuth
OAuth-based integration with automatic repo discovery and webhooks.
- GitHub App integration
Install Exlogare via the GitHub App for org-policy-friendly, fine-grained access to your repositories.
- GitHub Action — exlogare-ingest
Use the official `exlogare/exlogare-ingest-action` to push CI logs to Exlogare from any GitHub Actions runner.
- Exlogare CLI
Install and use `exl` to send CI logs and read AI root-cause analyses from the terminal.
- Status checks (Check Run / Build Status)
Exlogare publishes a green/red status check next to the failing commit on GitHub and Bitbucket, deep-linked to the analysis. It fires alongside the comment cascade — not instead of it.
API & ingest
- API reference
Programmatic access to Exlogare — endpoints, authentication, and examples.
- CI ingest API overview
One pattern for any CI — POST your failed-build log to Exlogare with an API key and get an RCA in the dashboard (and on paid plans, in Slack/Telegram/Matrix).
- Read API (v1)
Versioned, token-authenticated REST API for reading RCA history and stats — for dashboards, scripts, and bots.
- Grafana dashboard for Exlogare RCA
Drop-in Grafana dashboard backed by /api/v1/stats — failures/day, severity split, top projects, top root causes, p50/p90 time-to-RCA.
- Jenkins ingest
Send Jenkins console logs to Exlogare from a declarative pipeline, scripted pipeline, or a freestyle post-build script.
- CircleCI ingest
Send CircleCI job logs to Exlogare via a "when on_fail" step.
- TeamCity ingest
Send TeamCity build logs to Exlogare via a Build Failure Condition or service-message step.
- Drone CI / Woodpecker ingest
Send Drone or Woodpecker pipeline logs to Exlogare via an on-failure step.
- Generic CI ingest
One endpoint for any CI/CD platform — Buildkite, AppVeyor, custom in-house tooling.
- GitHub Actions ingest (no OAuth)
Send GitHub Actions workflow failures to Exlogare via the universal ingest API — no OAuth installation needed.
- GitLab CI ingest (no OAuth)
Send GitLab CI failures to Exlogare via after_script — no GitLab admin OAuth required.
- Outbound webhooks
Push every analysis.completed event to your own URL — PagerDuty, Sentry, Linear, Jira, or a custom relay. HMAC-SHA256 signed, retried with backoff.
Operations
- Self-hosting
A self-hosted distribution is on the roadmap. Today Exlogare is available as managed SaaS only.
- Recurring failures (clusters)
Every CI failure that happens more than once gets clustered automatically. See it in the dashboard, query it via the API, and let cost-saver mode skip duplicate LLM calls.
- Privacy & "State of CI Failures" aggregates
How Exlogare derives the public quarterly report on CI root causes — what is aggregated, what we never publish, and how to opt out.