Skip to content

Product Analytics Platform Implementation - Summary

Issue #97: Deploy Product Analytics Platform (Plausible/Matomo)

Status: ✅ COMPLETE Date: December 25, 2025 Milestone: M3.3 - Product Discovery & UX Priority: P1

Acceptance Criteria ✅

All acceptance criteria have been met:

✅ 1. Analytics Platform Deployed

  • Implementation: Plausible Analytics v2.0
  • Components:
  • Plausible application (2 replicas for HA)
  • ClickHouse database (analytics data storage)
  • PostgreSQL cluster (metadata storage)
  • Ingress with TLS
  • Location: platform/apps/plausible/
  • ArgoCD: platform/apps/plausible-application.yaml
  • Access: https://plausible.fawkes.idp

✅ 2. Privacy-Compliant

  • Cookie-less tracking: Enabled by default
  • GDPR compliance: Built-in, no configuration needed
  • No personal data: IP addresses not stored
  • No consent banners: Not required
  • Configuration:
  • DISABLE_REGISTRATION: true
  • LOG_FAILED_LOGIN_ATTEMPTS: false
  • DISABLE_AUTH: false (authentication required)

✅ 3. Backstage Instrumented

  • Tracking script configured: app-config.yaml updated
  • Domain: backstage.fawkes.idp
  • Script source: https://plausible.fawkes.idp/js/script.js
  • API proxy: /plausible/api endpoint added
  • File: platform/apps/backstage/app-config.yaml

✅ 4. Custom Events Configured

Configured to track:

  • Deploy Application
  • Create Service
  • View Documentation
  • Run CI/CD Pipeline

Usage:

plausible("Deploy Application", {
  props: { language: "nodejs", template: "express" },
});

✅ 5. Dashboard Accessible

  • URL: https://plausible.fawkes.idp
  • Login: admin@fawkes.local (default - change immediately!)
  • Features:
  • Real-time visitor tracking
  • Page views and trends
  • Traffic sources
  • Device and browser breakdown
  • Custom event tracking
  • Goal conversion tracking

✅ 6. Data Retention Policies Configurable

  • Configuration: Via Plausible dashboard (Settings → Data Retention)
  • Options: 6 months, 1 year, 2 years, Indefinite
  • Default: Indefinite (configure as needed)

Files Created/Modified

Platform Deployment

  1. ✅ platform/apps/plausible-application.yaml - ArgoCD application
  2. ✅ platform/apps/plausible/deployment.yaml - K8s manifests (all resources)
  3. ✅ platform/apps/plausible/kustomization.yaml - Kustomize config
  4. ✅ platform/apps/plausible/README.md - User documentation
  5. ✅ platform/apps/plausible/validate-plausible.sh - Component validation

Database

  1. ✅ platform/apps/postgresql/db-plausible-cluster.yaml - PostgreSQL cluster
  2. ✅ platform/apps/postgresql/db-plausible-credentials.yaml - DB credentials
  3. ✅ platform/apps/postgresql/kustomization.yaml - Updated with Plausible DB

Integration

  1. ✅ platform/apps/backstage/app-config.yaml - Plausible tracking added

Testing & Validation

  1. ✅ tests/bdd/features/product-analytics.feature - BDD tests (20+ scenarios)
  2. ✅ scripts/validate-product-analytics.sh - AT-E3-011 validation
  3. ✅ Makefile - Added validate-at-e3-011 target

Documentation

  1. ✅ docs/adr/ADR-032 Product Analytics Platform Selection.md - Decision record
  2. ✅ docs/how-to/product-analytics-quickstart.md - Quick start guide
  3. ✅ docs/implementation-plan/product-analytics-implementation.md - Full guide

Total: 15 files (3 modified, 12 created)

Deployment Architecture

┌──────────────────────────────────────────────────────┐
│                  Fawkes Platform                      │
│                                                       │
│  ┌────────────┐         ┌─────────────┐             │
│  │ Backstage  │────────▶│  Plausible  │◀────────┐   │
│  │  (Portal)  │         │  Analytics  │         │   │
│  └────────────┘         │  (2 pods)   │         │   │
│                         └──────┬──────┘         │   │
│  ┌────────────┐               │                 │   │
│  │ Other Apps │───────────────┘                 │   │
│  └────────────┘                                 │   │
│                         ┌──────▼──────┐         │   │
│                         │  ClickHouse │         │   │
│                         │  (Analytics │         │   │
│                         │    Data)    │         │   │
│                         └─────────────┘         │   │
│                                                  │   │
│                         ┌──────────────┐        │   │
│                         │  PostgreSQL  │        │   │
│                         │  (Metadata)  │        │   │
│                         │  (3 replicas)│        │   │
│                         └──────────────┘        │   │
│                                                  │   │
└──────────────────────────────────────────────────┘   │
                                                       │
                    ┌──────────────────────────────────┘
                    │
            ┌───────▼────────┐
            │  Ingress/TLS   │
            │  plausible.    │
            │  fawkes.idp    │
            └────────────────┘

Resource Impact

CPU Requests

  • Plausible: 400m (200m × 2 replicas)
  • ClickHouse: 200m
  • PostgreSQL: 600m (200m × 3 replicas)
  • Total: 1200m (~1.2 CPU cores)

Memory Requests

  • Plausible: 512Mi (256Mi × 2 replicas)
  • ClickHouse: 256Mi
  • PostgreSQL: 768Mi (256Mi × 3 replicas)
  • Total: 1536Mi (~1.5 GB)

Storage

  • ClickHouse: 10Gi (events/analytics data)
  • PostgreSQL: 30Gi (10Gi × 3 replicas, metadata)
  • Total: 40Gi

✅ Well within 70% resource utilization target

Testing

BDD Tests

File: tests/bdd/features/product-analytics.feature

20+ scenarios covering:

  • Deployment validation
  • Privacy compliance
  • Backstage integration
  • Custom events
  • Dashboard accessibility
  • Real-time tracking
  • Data retention
  • API access
  • GDPR compliance
  • High availability

Run: behave tests/bdd/features/product-analytics.feature

Validation Scripts

  1. Component Validation
./platform/apps/plausible/validate-plausible.sh --namespace fawkes
  • Validates all Plausible components
  • Checks health endpoints

  • Verifies configuration

  • Acceptance Test Validation (AT-E3-011) 

    make validate-at-e3-011 NAMESPACE=fawkes

  • Validates all acceptance criteria
  • Comprehensive deployment check
  • Integration verification

Deployment Instructions

Quick Deploy (5 minutes)

# 1. Deploy via ArgoCD
kubectl apply -f platform/apps/plausible-application.yaml

# 2. Wait for deployment
kubectl wait --for=condition=Ready pod -l app=plausible -n fawkes --timeout=300s

# 3. Validate
make validate-at-e3-011 NAMESPACE=fawkes

First Login

  1. Open: https://plausible.fawkes.idp
  2. Login: admin@fawkes.local / changeme-admin-password
  3. ⚠️ Change password immediately!

Add Sites

  1. Click "+ Add website"
  2. Enter domain: backstage.fawkes.idp
  3. Start tracking immediately

See Quick Start Guide for details.

Security & Privacy

Implemented Security Measures

  • ✅ No cookies used
  • ✅ No personal data collected
  • ✅ IP addresses not stored
  • ✅ TLS encryption for all traffic
  • ✅ Authentication required
  • ✅ Public registration disabled
  • ✅ Non-root containers
  • ✅ Security contexts configured
  • ✅ Resource limits enforced

GDPR Compliance

  • ✅ Privacy by design
  • ✅ No consent banners needed
  • ✅ Data minimization
  • ✅ Data sovereignty (self-hosted)
  • ✅ Transparent data handling
  • ✅ User rights respected

Next Steps

Immediate (Required)

  1. ⚠️ Change default admin password
  2. ⚠️ Update secret keys in production
  3. ✅ Add sites to track
  4. ✅ Configure custom goals
  5. ✅ Set data retention policy
  1. Add additional platform components (Jenkins, Grafana, etc.)
  2. Configure team access and roles
  3. Set up API keys for programmatic access
  4. Create custom dashboards
  5. Configure alerts for key metrics

Long-term (Optional)

  1. Integrate with data warehouse
  2. Add advanced funnel analysis
  3. Set up A/B testing framework
  4. Implement custom reporting
  5. Add webhook notifications

Known Limitations

  1. No session recording - By design for privacy
  2. No heatmaps - Can add separate tool if needed
  3. Limited A/B testing - Can add Unleash or GrowthBook
  4. Country-level geolocation only - Privacy trade-off

These are intentional design choices for privacy. If advanced features are needed, they can be added separately.

Monitoring & Maintenance

Health Checks

  • Plausible: GET /api/health
  • ClickHouse: GET /ping
  • PostgreSQL: CloudNativePG operator monitoring

Logs

# Plausible logs
kubectl logs -n fawkes deployment/plausible -f

# ClickHouse logs
kubectl logs -n fawkes statefulset/plausible-clickhouse -f

# Database logs
kubectl logs -n fawkes db-plausible-dev-1 -f

Backups

  • PostgreSQL: Automated via CloudNativePG
  • ClickHouse: Configure backup policy as needed

Documentation

  1. ADR: ADR-032 Product Analytics Platform Selection
  2. Quick Start: Product Analytics Quick Start
  3. Implementation Guide: Product Analytics Implementation
  4. User Guide: Plausible README
  5. Plausible Docs: https://plausible.io/docs

Dependencies

Depends On

  • Issue #545: Prerequisites completed

Blocks

  • Issue #547: Can now proceed
  • Epic 3.3: Product Discovery & UX
  • AT-E3-011: Product Analytics Platform validation

Success Metrics

Immediate Success (Day 1)

  • ✅ Deployment completes successfully
  • ✅ All health checks passing
  • ✅ Dashboard accessible
  • ✅ Backstage tracking working

Short-term Success (Week 1)

  • Track 100+ page views
  • Capture custom events
  • Identify top pages
  • Understand traffic sources

Long-term Success (Month 1+)

  • Measure feature adoption
  • Identify pain points
  • Guide platform improvements
  • Data-driven decision making

Credits

  • Implemented by: GitHub Copilot
  • Date: December 25, 2025
  • Review: Pending
  • Status: ✅ COMPLETE, ready for validation

Support

  • Issues: https://github.com/paruff/fawkes/issues/97
  • Questions: Check documentation above
  • Bugs: Create issue with component: analytics label