Data Collection Overview

PanDev Metrics relies on an event-driven architecture to capture developer activity inside IDEs and the browser. The focus is strictly on corporate projects—personal activity remains private.

⚠️ Security & Privacy

Only work-related data is collected.

• ❌ No screenshots – the system never records the screen.
• ❌ No personal tracking – non-work activity is ignored.
• ❌ No personal projects – only whitelisted corporate repositories.
• ✅ IDE and Chrome only – other apps stay invisible.
• ✅ Full transparency – users can always see what is captured.

Collection Principles

1. Event-driven (no timers)

There are no ticking timers. Data is generated only when real activity occurs (typing, navigation, etc.). Mathematical models derive active time between events.

How it works:

• Events fire exclusively on real interactions.
• Inter-event gaps determine active time.
• No background timers, no idle polling.

2. Zero-click automation

Engineers install the plugin once and sign in once. The entire collection pipeline runs automatically afterwards—no repeated logins or manual triggers.

Benefits:

• One-time setup.
• Background operation.
• Persistent sessions.
• Zero disruption of daily work.

3. Online/offline support

Plugins cache events locally whenever the server is unreachable. As soon as connectivity returns, cached data syncs automatically.

Mechanics:

• Local storage on the developer’s machine.
• Automatic retries until delivery succeeds.
• Visibility into sync status.

4. Straightforward architecture

Plugins send telemetry to the on-premises PanDev Metrics Core, which stores everything in PostgreSQL for downstream analytics.

System Architecture

┌─────────────────┐    ┌─────────────────┐    ┌─────────────────┐
│   IDE Plugin    │    │  Chrome Ext     │    │    Git Hook     │
│    (Events)     │    │    (Events)     │    │    (Events)     │
└─────────────────┘    └─────────────────┘    └─────────────────┘
         │                       │                       │
         └───────────────────────┼───────────────────────┘
                                 │
                     ┌────────────────────────┐
                     │ PanDev Metrics Server  │
                     │     (Event Intake)     │
                     └────────────────────────┘
                                 │
                     ┌────────────────────────┐
                     │    Data Processing     │
                     └────────────────────────┘
                                 │
                     ┌────────────────────────┐
                     │     PostgreSQL DB      │
                     └────────────────────────┘
                                 │
                     ┌────────────────────────┐
                     │      Analytics &       │
                     │        Reports         │
                     └────────────────────────┘

What Happens Next

1. Storage & enrichment – events are normalised, deduplicated, and enriched with metadata.
2. Correlation – IDE, Git, and task-tracker data are linked for context.
3. Analytics – metrics feed dashboards, anomaly detection, and ML models.
4. Insight delivery – recommendations and alerts surface improvement opportunities.

Security & Privacy

Personalised identifiers

• Events are tied to known developers for accurate analytics.
• IDs remain internal; there is no exposure outside the organisation.

Encryption

• TLS protects data in transit.
• Local caches are encrypted at rest.
• Access is only possible through authenticated APIs.

Access control

• Role-based permissions.
• Audit logs for every sensitive operation.
• Compliance with corporate security policies.

Outcome

PanDev Metrics’ event-driven approach ensures:

• Precise telemetry limited to corporate assets.
• Robust privacy with no intrusion into personal life.
• Powerful analytics by combining IDE, Jira, and Git data.
• Actionable insight through AI-assisted recommendations.
• Scalability for engineering teams of any size.