We use essential cookies for authentication and optional analytics cookies to improve the platform. Privacy Policy

    Video Observability

    Video Observability: Monitoring Your Operations Through Video

    Video observability is the practice of using continuous video analysis to maintain operational awareness — the same way application observability uses logs, metrics, and traces to monitor software systems.

    Observability vs monitoring vs surveillance

    ApproachInputOutputWho acts
    SurveillanceRaw recorded videoArchive for manual reviewHuman after incident
    MonitoringMotion events, alertsTriggered notificationsHuman in response
    ObservabilityContinuous AI analysisLogs + metrics + traces + searchSystem automatically surfaces anomalies

    The three pillars applied to video

    Logs (Event Records)

    Every detected event with timestamp, type, persons involved, and location. Queryable via AI chat: "Show me all idle events on Line 3 last week over 60 seconds."

    Metrics (Time Series)

    Quantitative measures over time: cycle time per shift, utilization rate per operator, crowd density per hour. Exportable to BI tools and OTel collectors.

    Traces (Activity Flows)

    End-to-end process execution: from first operator action to completion, with each step timed and classified. Maps to OpenTelemetry span concepts.

    VidForgeX observability infrastructure

    VidForgeX logs the lifecycle of every analysis — started, completed, failed — to a centralised log service. Raw request bodies and AI payloads are never logged, and credentials are scrubbed before anything is stored.

    Analysis results are stored durably in encrypted object storage (JSON artifacts) with metadata in a managed database. The notification system provides in-platform observability for analysis status. For operational use cases requiring real-time dashboards, the MCP API enables custom integrations: pollget_team_summary on a schedule and pipe results to your preferred metrics platform.

    video observabilityoperational video monitoringvideo metricsvideo event logsOpenTelemetry videovideo intelligence monitoringfacility observabilityprocess observabilityVidForgeXvideo audit trail

    Frequently Asked Questions

    What is video observability?
    Video observability applies the three pillars of software observability (logs, metrics, traces) to operational video: logs = timestamped event records from video analysis; metrics = time-series data (cycle time, utilization rate, crowd density); traces = activity flow from start to end of a process. Together they give operators a real-time and historical view of what is happening in their physical environment.
    How is video observability different from video surveillance?
    Surveillance records footage for potential review. Observability continuously extracts structured data from footage and makes it queryable, alertable, and dashboard-ready — like the difference between writing log files and running a metrics platform. Observability surfaces anomalies automatically rather than requiring human watchers.
    What alert conditions can VidForgeX detect?
    Analysis completion/failure notifications are native (via the notifications system). For threshold-based operational alerts (e.g., "alert when cycle time exceeds 50 seconds three times in a row"), the MCP API can be called by an orchestration layer (n8n, Zapier, custom service) that monitors get_team_summary data and triggers alerts via webhook.
    How does VidForgeX relate to OpenTelemetry?
    VidForgeX analysis data can be exported in structured JSON formats compatible with OpenTelemetry span conventions. The event log (timestamped activity records) maps to OTel traces; the metric series (cycle time, utilization) maps to OTel metrics. Enterprise customers building unified observability stacks can pipe VidForgeX data into their OTel collector alongside application metrics.