Dashboards, alerts, and scheduled reports for your time-series metrics. Connect the database where you already track metrics with Trifle Stats, then visualize, monitor, and share insights with your team.

Part of the Trifle ecosystem.

• Real-time dashboards. Phoenix LiveView-powered analytics with Apache ECharts visualizations.
• Metrics API. Read metrics, manage dashboards and alerts programmatically via REST API.
• Monitors & alerts. Scheduled checks with email, Slack, and Discord delivery.
• AI-powered chat. Conversational analytics assistant (OpenAI GPT integration).
• Connect your database. Read metrics directly from your existing Postgres, MongoDB, Redis, MySQL, or SQLite where you track with Trifle Stats.
• Self-hosted. Deploy on Kubernetes or Docker Compose on your own infrastructure.
• Dark mode. Full dark mode support across all components.

# Create local env
echo "TRIFLE_DB_ENCRYPTION_KEY=$(openssl rand -base64 32)" >> .env.local

# Start PostgreSQL and the application
docker compose up -d

# Inside the app container: install deps, setup DB, start server
docker compose exec -T app mix deps.get
docker compose exec -T app mix deps.compile
docker compose exec -T app mix ecto.create
docker compose exec -T app mix ecto.migrate
docker compose exec -T app mix run priv/repo/seeds.exs
docker compose exec -T app mix phx.server

Visit http://localhost:4000.

• Email. Configure Trifle.Mailer (see EMAILS.md). All organization members are available as delivery targets.
• Slack. Set SLACK_CLIENT_ID, SLACK_CLIENT_SECRET, SLACK_SIGNING_SECRET, and SLACK_REDIRECT_URI. Authorize workspaces from Organization > Delivery.
• Discord. Set DISCORD_CLIENT_ID, DISCORD_CLIENT_SECRET, DISCORD_BOT_TOKEN, and DISCORD_REDIRECT_URI. Connect servers from Organization > Delivery.

Conversational analytics assistant that queries your metrics using OpenAI GPT models. Available at /chat.

Automated builds via GitHub Actions on every push to main and version tags:

• trifle/app: Application image (AMD64 + ARM64)
• trifle/environment: Base image (Ruby, Erlang, Elixir)

Version is defined in the root VERSION file.

helm install trifle .devops/kubernetes/helm/trifle \
  --set app.secretKeyBase="$(openssl rand -base64 48)" \
  --set postgresql.auth.password="$(openssl rand -base64 32)" \
  --set initialUser.email="admin@example.com"

cd .devops/docker/production
cp .env.example .env
# Edit .env with your production values
docker-compose up -d

Configurable via Helm. Supported adapters: local (default), smtp, postmark, sendgrid, mailgun, brevo.

app:
  mailer:
    adapter: "smtp"
    from:
      name: "Trifle"
      email: "no-reply@example.com"
    smtp:
      relay: "smtp.example.com"
      username: "smtp-user"
      password: "smtp-pass"
      port: 587

• Honeybadger. Set app.honeybadger.apiKey in Helm values.
• AppSignal. Set app.appsignal.enabled: true with pushApiKey.

Monitor schedules are orchestrated by Trifle.Monitors.Jobs.DispatchRunner, which runs every minute and enqueues jobs on the reports and alerts queues via Oban.

Oban Web UI is optional: set OBAN_WEB_LICENSE_KEY before mix deps.get to enable the dashboard at /admin/oban.

• Elixir 1.18.4
• Phoenix Framework
• PostgreSQL (or use Docker Compose)

# Quick API validation (4 sample metrics)
./test_metrics.sh YOUR_TOKEN

# Bulk population (recommended for large datasets)
./populate_batch.sh YOUR_TOKEN 500 72   # 500 metrics over 3 days

# Mix task (small datasets)
mix populate_metrics --token=YOUR_TOKEN --count=100 --hours=24

Full guides at docs.trifle.io/trifle-app

Available under the Elastic License 2.0. See LICENSE for details.