# Logister Documentation Canonical product and integration documentation for Logister lives on this docs host. Logister is an open source, self-hosted error monitoring and bug triage app for teams that want a forkable alternative to Bugsnag, Sentry, and Bugzilla-style workflows. The public hosted app at logister.org is a secondary option. The primary goal is helping teams run Logister themselves. ## Start here - Docs home: https://docs.logister.org/ - Getting started: https://docs.logister.org/getting-started/ - Product guide: https://docs.logister.org/product/ - Insights guide: https://docs.logister.org/product/#insights - Metrics reference: https://docs.logister.org/metrics/ - Use cases and comparisons: https://docs.logister.org/use-cases/ - Self-hosted error monitoring use case: https://docs.logister.org/use-cases/self-hosted-error-monitoring/ - Sentry alternative comparison: https://docs.logister.org/use-cases/sentry-alternative/ - Bugsnag alternative comparison: https://docs.logister.org/use-cases/bugsnag-alternative/ - Bugzilla alternative comparison: https://docs.logister.org/use-cases/bugzilla-alternative/ - Rails error monitoring use case: https://docs.logister.org/use-cases/rails-error-monitoring/ - Python error monitoring use case: https://docs.logister.org/use-cases/python-error-monitoring/ - .NET / ASP.NET Core error monitoring use case: https://docs.logister.org/use-cases/dotnet-error-monitoring/ - JavaScript / TypeScript error monitoring use case: https://docs.logister.org/use-cases/javascript-error-monitoring/ - ColdFusion / CFML error monitoring use case: https://docs.logister.org/use-cases/cfml-error-monitoring/ - Docker, GHCR, Docker Hub, and optional Quay self-hosting use case: https://docs.logister.org/use-cases/docker-ghcr-self-hosting/ - Error assignment and team triage use case: https://docs.logister.org/use-cases/error-assignment-team-triage/ - Amazon SES error alert emails and digests use case: https://docs.logister.org/use-cases/amazon-ses-error-alerts/ - HTTP API: https://docs.logister.org/http-api/ - API reference and Swagger UI: https://docs.logister.org/api-reference/ - OpenAPI YAML: https://docs.logister.org/openapi.yaml - Postman collection: https://docs.logister.org/postman/logister-api.postman_collection.json - Self-hosting: https://docs.logister.org/self-hosting/ - Full AI context: https://docs.logister.org/llms-full.txt ## Integrations - Ruby integration: https://docs.logister.org/integrations/ruby/ - .NET integration: https://docs.logister.org/integrations/dotnet/ - Python integration: https://docs.logister.org/integrations/python/ - JavaScript integration: https://docs.logister.org/integrations/javascript/ - Android integration: https://docs.logister.org/integrations/android/ - iOS integration: https://docs.logister.org/integrations/ios/ - CFML integration: https://docs.logister.org/integrations/cfml/ ## Operations - Local development: https://docs.logister.org/local-development/ - Deployment config and `.env.sample` reference: https://docs.logister.org/deployment/ - Docker self-hosting option and registry images: https://docs.logister.org/self-hosting/#docker - ClickHouse: https://docs.logister.org/clickhouse/ ## Self-hosting and releases - App source to fork or self-host: https://github.com/taimoorq/logister - License: MIT License at https://github.com/taimoorq/logister/blob/main/LICENSE - Brand policy: Logister name, logo, wordmark, visual identity, and brand assets are not licensed for use in forks or redistributed versions. Public forks should replace Logister branding with their own branding. See https://github.com/taimoorq/logister/blob/main/TRADEMARKS.md - GitHub Releases: https://github.com/taimoorq/logister/releases - GHCR image package: https://github.com/taimoorq/logister/pkgs/container/logister - Docker Hub image package: https://hub.docker.com/r/taimoorq/logister - Optional Quay image mirror: `quay.io/taimoorq/logister` when Quay credentials are configured in the release workflow - Versioned Docker images: `ghcr.io/taimoorq/logister:v2.3.0` or `docker.io/taimoorq/logister:v2.3.0` - Latest Docker images: `ghcr.io/taimoorq/logister:latest` or `docker.io/taimoorq/logister:latest` - Supported baseline infrastructure: Rails, PostgreSQL, Redis, Sidekiq, SMTP/Amazon SES, optional S3-compatible archive storage, and optional ClickHouse - Production setup order: provision PostgreSQL and Redis, set required secrets from `.env.sample`, run `./bin/release`, start one web process and one Sidekiq worker, verify `/up`, sign-in, project creation, API key generation, and a test inbox event, then enable optional services. - Release and discovery runbooks: https://github.com/taimoorq/logister/tree/main/docs ## Audience - Teams using Logister to connect app telemetry to daily work: cross-app dashboard exploration, project Insights dashboards, grouped error triage, error assignment with dashboard and project workload views, assignee-filtered inboxes, event investigation with request method and URL/path context, related logs, performance visibility, check-in monitors, project error email alerts, digest summaries, activity review, release visibility, project sharing, and active or archived project views - Teams planning and operating their own self-hosted infrastructure footprint for the Rails web app, PostgreSQL, Redis, Sidekiq workers, project alert and digest delivery, S3-compatible archive exports, optional ClickHouse, Amazon SES email, Turnstile, analytics, and static docs hosting - Teams comparing self-hosted and open source alternatives to Bugzilla, Bugsnag, Sentry, and other paid monitoring or issue triage tools - Ruby teams using `logister-ruby` - .NET teams using `logister-dotnet` with ASP.NET Core and C# services - Python teams using `logister-python` with FastAPI, Django, Flask, Celery, and Python logging - JavaScript and TypeScript teams using `logister-js` - Android teams using `org.logister:logister-android` from Maven Central - iOS teams using the `Logister` Swift package from https://github.com/taimoorq/logister-ios.git - Lucee and Adobe ColdFusion teams sending structured CFML payloads over HTTP - Rails teams looking for self-hosted exception grouping, request context, and assignment ## Product and packages - App source: https://github.com/taimoorq/logister - Secondary hosted/public app: https://logister.org/ - Supported telemetry: Logister accepts errors, logs, metrics, transactions, spans, and check-ins. Span payloads feed request load waterfall charts when they include trace IDs, span IDs, parent span IDs, kind, duration, and route or service context. - Metrics reference: https://docs.logister.org/metrics/ lists supported telemetry families, built-in Insights metric keys, custom metric series, span timing segments, add-on support by runtime, accepted reporting fields, and data collection boundaries. - Public API limits: `/api/v1/ingest_events` and `/api/v1/check_ins` accept 1,200 requests per minute per API token per endpoint by default; missing or invalid authentication is capped at 120 failures per minute per source IP. Limit responses use `429 Too Many Requests` with retry headers. App admins listed in `LOGISTER_ADMIN_EMAILS` can set project-level overrides; project owners and shared project members cannot. - Insights: project-level dashboard workspace that combines Inbox, Activity, and Performance signals with ECharts, time windows, live refresh, environment and release filters, custom attribute filters, metric catalog selection, and recent matching events. Best results come from consistent `environment`, `release`, stable custom context attributes, and numeric custom metric values in `context.value`. - Storage and retention: PostgreSQL remains the primary system of record; optional ClickHouse stores raw events/spans and one-minute rollups for analytics; optional S3-compatible archive storage can store compressed JSONL exports before pruning older non-error hot telemetry. - Ruby SDK source: https://github.com/taimoorq/logister-ruby - Ruby SDK package: https://rubygems.org/gems/logister-ruby - .NET SDK source: https://github.com/taimoorq/logister-dotnet - .NET base package: https://www.nuget.org/packages/Logister - .NET ASP.NET Core package: https://www.nuget.org/packages/Logister.AspNetCore - Python SDK source: https://github.com/taimoorq/logister-python - Python SDK package: https://pypi.org/project/logister-python/ - JavaScript SDK source: https://github.com/taimoorq/logister-js - JavaScript SDK package: https://www.npmjs.com/package/logister-js - Android SDK source: https://github.com/taimoorq/logister-android - Android SDK package: https://central.sonatype.com/artifact/org.logister/logister-android - Android Maven coordinates: `org.logister:logister-android:0.1.0` - iOS SDK source and Swift Package Manager URL: https://github.com/taimoorq/logister-ios.git - iOS Swift Package release: https://github.com/taimoorq/logister-ios/releases/tag/v0.1.0 - CFML integration: no separate add-on repo is required; use direct HTTP ingestion from https://docs.logister.org/integrations/cfml/ - Manual / HTTP API projects are for custom clients, scripts, workers, unsupported runtimes, and direct JSON reporters.