"os" key for the device generating the event. User-Agent based OS context under the default key "os". Incoming User-Agent can only come from the crashing device, and creates the The server however knows by looking at the platform ( "javascript") that the In events reported from a JS web frontend, the SDK typically reports no OS Under the default key "os" is the server's operating system, and is set byĪdditionally, the Sentry server will attempt to parse the User-Agent headerįrom the event's Request Interface and create a secondary OSĬontext under the non-default key "client_os". In events reported from a Python/ASP.NET/Rails web backend, the OS context Multiple times under different keys, there has historically been a lot ofĬonfusion about which OS context represents what. The crash happened/the event was created. OS context under the default key "os" describes the operating system on which Is the device capable of reporting its location? OS Context Is accelerometer available on the device? This value might only be used if sendDefaultPii is enabled. For example, Unknown, Charging, Discharging, NotCharging, Full.ĭevice_unique_identifier Optional. For example, Unknown, Handheld, Console, Desktop.īattery_status Optional. Kind of device the application is running on. Note that the actual CPU frequency might vary depending on current load and power conditions,Įspecially on low-powered devices like phones and laptops.ĭevice_type Optional. For example, Intel(R) Core(TM)2 Quad CPU Q6600 2.40GHz. This field is deprecated, please use locale of culture context instead. This field is deprecated, please use timezone of culture context instead. A formatted UTC timestamp when the system was booted. Free size of an attached external storage in bytes (for example,īoot_time Optional. Total size of an attached external storage in bytes (for example,Įxternal_free_storage Optional. Free device storage in bytes.Įxternal_storage_size Optional. Total device storage in bytes.įree_storage Optional. Total system memory available in bytes.įree_memory Optional. A flag indicating whether this device is a simulator or an actual Whether the device was online or not.Ĭharging Optional. A decimal value reflecting the DPI (dots-per-inch) density. A floating point denoting the screen density. This can be a string portrait or landscape to define the If the device has a battery, this can be a floating point valueĭefining the battery level (in the range 0-100). An internal hardware revision to identify the device exactly.īattery_level Optional. This, for example, can be Samsung Galaxy S3. For instance, iPhone would be a reasonable family, This is typically a hostname.įamily Optional. Device Contextĭevice context describes the device that caused the event. įor more details about sending additional data with your event, see the full documentation on Additional Data. More details about this can be found in the contexts code on the Sentry UI. In the Sentry Product, certain contexts are rendered in a special way to make it more readable. Unknown data for the contexts is rendered as a key/value list. Suited to data that is collected over time as the SDK interfaces for contexts You have all the data available at a single point in time. When adding additional data to the event data model contexts are a good fit when Type of the context unless there are two values for a type. However, as per policy, it should match the The key is the “alias” of theĬontext and can be freely chosen. The contexts type can be used to define arbitrary contextual data on theĮvent. For example, the device orĪpplication version. Related to the current user and the environment. The Contexts Interface provides additional context data.
0 Comments
Leave a Reply. |