{"version":"2.1.248","anchor":"telemetry-on-how-os-level-managed-settings-are-read","canonical_anchor":"telemetry-on-how-os-level-managed-settings-are-read","heading":"Telemetry on how OS-level managed settings are read","tier":"internal","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/telemetry-on-how-os-level-managed-settings-are-read","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Telemetry on how OS-level managed settings are read\n\nReading administrator-set settings now records how the OS policy lookup went.\n\n**What**\n\nLoading managed (MDM) settings now records how the underlying OS policy read went, so failures to pick up administrator-set settings can be diagnosed.\n\n**Details**\n\n- Event `tengu_managed_settings_os_read` reports per-command status, exit code, errno bucket (ENOENT, EACCES and others) and signal bucket (SIGTERM, SIGKILL, SIGINT), plus timeout, spawn_error and killed.\n- Emitted unconditionally, wrapped in try\/catch so a reporting failure cannot break settings loading.\n\n**Evidence**\n\n`tengu_managed_settings_os_read`\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}