✨(summary) add hostname to analytics properties

This helps track down what was the source of events. This can be usefull when checking perf of different workers for instance.
📈(frontend) stop double-reporting media device failures
2026-08-15 05:03:34 +00:00 · 2026-08-14 14:45:18 +02:00 · 2026-08-14 14:04:35 +02:00 · 2026-08-14 11:22:40 +02:00 · 2026-08-14 11:22:40 +02:00
5 changed files with 21 additions and 10 deletions
@@ -12,6 +12,7 @@ and this project adheres to

 - 🔥(frontend) drop unused vendored ConnectionObserver
 - 🐛(frontend) vendor formatChatMessageLinks and trim surrounding newlines
+- ✨(summary) add hostname to analytics properties

 ### Fixed

@@ -23,6 +24,7 @@ and this project adheres to
 - 🐛(analytics) filter benign ResizeObserver loop error in Sentry/PostHog
 - 🐛(frontend) stop reporting screen-share denials as errors
 - 🐛(frontend) generalize screen-share error modal beyond macOS
+- 📈(frontend) stop double-reporting media device failures

 ## [1.26.0] - 2026-08-12

@@ -23,6 +23,7 @@ export type LogCode =
  | 'livekit_room_error'
  | 'device_switch_failure'
  | 'permission_poll_failure'
+  | 'media_devices_error_event'
  // non-media families
  | 'participant_mute_api_failure'
  | 'permissions_api_failure'
@@ -225,9 +225,10 @@ export const Conference = ({
            backgroundColor: 'primaryDark.50 !important',
          })}
          onError={(e) => {
+            const failure = MediaDeviceFailure.getFailure(e)
+            if (failure && failure !== MediaDeviceFailure.Other) return
            reportError('livekit_room_error', e, {
              path: 'connect_publish',
-              failure: MediaDeviceFailure.getFailure(e) ?? 'not-a-device-error',
            })
          }}
          onConnected={async () => {
@@ -50,15 +50,16 @@ export const useWatchMediaDeviceErrors = (): MediaDeviceAlert & {
  useEffect(() => {
    const onDeviceError = (error: Error, kind?: MediaDeviceKind) => {
      const failure = MediaDeviceFailure.getFailure(error)
-      if (!failure || !kind) return
-
-      void captureMediaEvent('media-device-error', {
-        log_code: 'media_devices_error_event',
-        path: 'connect_publish',
-        failure,
-        kind,
-      })
-
+      if (!failure) return
+      if (failure != MediaDeviceFailure.Other) {
+        void captureMediaEvent('media-device-error', {
+          log_code: 'media_devices_error_event',
+          path: 'connect_publish',
+          failure,
+          kind: kind ?? 'unknown',
+        })
+      }
+      if (!kind) return
      const permissionKind = PERMISSION_BY_DEVICE_KIND[kind]
      switch (failure) {
        case MediaDeviceFailure.DeviceInUse:
@@ -1,6 +1,7 @@
 """Analytics classes."""

 import json
+import socket
 import time
 from collections import Counter
 from functools import lru_cache
@@ -43,6 +44,11 @@ class Analytics:
        if self.is_disabled:
            return

+        # We add hostname to help track down the source of events
+        properties = properties or {}
+        if not properties.get("hostname"):
+            properties = {**properties, "hostname": socket.gethostname()}
+
        try:
            self._client.capture(
                event_name, distinct_id=distinct_id, properties=properties
Author	SHA1	Message	Date
Florent Chehab	13c75697c7	✨(summary) add hostname to analytics properties This helps track down what was the source of events. This can be usefull when checking perf of different workers for instance.	2026-08-14 14:45:18 +02:00
lebaudantoine	8d000fc6d9	📈(frontend) stop double-reporting media device failures Only report `Other` `MediaDeviceFailure` cases as they genuinely need investigation. Make sure we do not report the same situation both as a media event and as a media exception when it is already handled.	2026-08-14 14:04:35 +02:00
lebaudantoine	b7abd0ae6e	🐛(frontend) generalize screen-share error modal beyond macOS The screen-share error modal was tailored to macOS and did not work correctly on other operating systems. Make it OS-aware so it also handles Windows properly, showing the right guidance for each platform. Also open the OS settings link in a new tab, so the user is not disconnected from the ongoing meeting when following it.	2026-08-14 11:22:40 +02:00
lebaudantoine	40e4f17c65	🐛(frontend) stop reporting screen-share denials as errors Add a small helper that classifies a `getDisplayMedia` failure as a user, browser, or OS permission denial, or returns null when it is a genuine error. Chromium reports denials with explicit, non-localized messages: * "Permission denied by user" when the user cancels or dismisses the source picker. * "Permission denied by system" when the OS blocks capture (e.g. the macOS Screen Recording privacy setting). * Plain "Permission denied" for browser-level blocks (site settings, enterprise policy, permissions-policy). Firefox and Safari use generic `NotAllowedError` messages, which fall into the "browser" bucket. Firefox additionally does not map macOS Screen Recording (TCC) blocks to `NotAllowedError`: the OS silently returns no capturable sources, so `getDisplayMedia` rejects with `NotFoundError` ("The object can not be found here."). Same quirk as the mic/cam OS blocks handled in `useWatchMediaDeviceErrors` via `isLikelySystemNotFound`. Behavior on a denied screen-share permission: * Denials are expected outcomes (picker cancelled by the user, OS privacy settings, enterprise policy…) and no longer surface as exceptions in error tracking; capture an analytics event instead. * Only OS-level blocks get the modal, since it explains how to unblock them.	2026-08-14 11:22:40 +02:00