{"version":"2.1.267","anchor":"artifact-url-inputs-are-now-classified-for-telemetry-on-writ","canonical_anchor":"artifact-url-inputs-are-now-classified-for-telemetry-on-writ","heading":"Artifact URL inputs are now classified for telemetry on write\/publish errors","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/artifact-url-inputs-are-now-classified-for-telemetry-on-writ","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Artifact URL inputs are now classified for telemetry on write\/publish errors\n\nMalformed Artifact URLs passed to publish or link actions are now classified and reported in telemetry\n\n**What**\n\nWhen a publish or link action receives an artifact URL that's malformed or unexpected, a new classifier now categorizes what's wrong with it, using labels such as `chat_artifact_link`, `viewer_path_bad_id`, `bare_id`, `missing_scheme`, `loopback_host`, and `same_artifact`. This classification is sent via telemetry whenever a specific error code is hit.\n\n**Why**\n\nCategorizing the specific way a URL is malformed makes it easier to spot patterns in what's going wrong with artifact links, rather than lumping every bad-URL error together.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}