Add in Sentry, WebRTC Statistics (#345)
Collect WebRTC Statistical Information Add in some instrumentation to track the duration of the setup phase, and set up a job to make periodic use of the WebRTC Statistics API to collect information about the connection (specifically, each track), including transport-level information, timing information and bandwidth information. Sentry isn't the best place for that information, but it'll work until we can work out a good long-term solution for it. Signed-off-by: Paul Tagliamonte <paul@kittycad.io>
This commit is contained in:
@ -8,6 +8,9 @@ export const VITE_KC_API_WS_MODELING_URL = import.meta.env
|
||||
.VITE_KC_API_WS_MODELING_URL
|
||||
export const VITE_KC_API_BASE_URL = import.meta.env.VITE_KC_API_BASE_URL
|
||||
export const VITE_KC_SITE_BASE_URL = import.meta.env.VITE_KC_SITE_BASE_URL
|
||||
export const VITE_KC_CONNECTION_WEBRTC_REPORT_STATS_MS = import.meta.env
|
||||
.VITE_KC_CONNECTION_WEBRTC_REPORT_STATS_MS
|
||||
export const VITE_KC_CONNECTION_TIMEOUT_MS = import.meta.env
|
||||
.VITE_KC_CONNECTION_TIMEOUT_MS
|
||||
export const VITE_KC_SENTRY_DSN = import.meta.env.VITE_KC_SENTRY_DSN
|
||||
export const TEST = import.meta.env.TEST
|
||||
|
Reference in New Issue
Block a user