construct-hub 0.4.520 → 0.4.522

package/.jsii

@@ -21906,7 +21906,7 @@
         },
         "locationInModule": {
           "filename": "src/package-sources/npmjs.ts",
-          "line": 115
+          "line": 120
         },
         "parameters": [
           {
@@ -21924,7 +21924,7 @@
       "kind": "class",
       "locationInModule": {
         "filename": "src/package-sources/npmjs.ts",
-        "line": 114
+        "line": 119
       },
       "methods": [
         {
@@ -21934,7 +21934,7 @@
           },
           "locationInModule": {
             "filename": "src/package-sources/npmjs.ts",
-            "line": 117
+            "line": 122
           },
           "name": "bind",
           "overrides": "construct-hub.IPackageSource",
@@ -21965,7 +21965,7 @@
           },
           "locationInModule": {
             "filename": "src/package-sources/npmjs.ts",
-            "line": 377
+            "line": 397
           },
           "name": "metricBatchProcessingTime",
           "parameters": [
@@ -21990,7 +21990,7 @@
           },
           "locationInModule": {
             "filename": "src/package-sources/npmjs.ts",
-            "line": 390
+            "line": 410
           },
           "name": "metricChangeCount",
           "parameters": [
@@ -22016,7 +22016,7 @@
           },
           "locationInModule": {
             "filename": "src/package-sources/npmjs.ts",
-            "line": 404
+            "line": 424
           },
           "name": "metricLastSeq",
           "parameters": [
@@ -22040,7 +22040,7 @@
           },
           "locationInModule": {
             "filename": "src/package-sources/npmjs.ts",
-            "line": 414
+            "line": 434
           },
           "name": "metricNpmJsChangeAge",
           "parameters": [
@@ -22065,7 +22065,7 @@
           },
           "locationInModule": {
             "filename": "src/package-sources/npmjs.ts",
-            "line": 427
+            "line": 447
           },
           "name": "metricPackageVersionAge",
           "parameters": [
@@ -22090,7 +22090,7 @@
           },
           "locationInModule": {
             "filename": "src/package-sources/npmjs.ts",
-            "line": 440
+            "line": 460
           },
           "name": "metricPackageVersionCount",
           "parameters": [
@@ -22115,7 +22115,7 @@
           },
           "locationInModule": {
             "filename": "src/package-sources/npmjs.ts",
-            "line": 453
+            "line": 473
           },
           "name": "metricRelevantPackageVersions",
           "parameters": [
@@ -22140,7 +22140,7 @@
           },
           "locationInModule": {
             "filename": "src/package-sources/npmjs.ts",
-            "line": 467
+            "line": 487
           },
           "name": "metricRemainingTime",
           "parameters": [
@@ -22165,7 +22165,7 @@
           },
           "locationInModule": {
             "filename": "src/package-sources/npmjs.ts",
-            "line": 481
+            "line": 501
           },
           "name": "metricUnprocessableEntity",
           "parameters": [
@@ -22198,7 +22198,7 @@
       "kind": "interface",
       "locationInModule": {
         "filename": "src/package-sources/npmjs.ts",
-        "line": 67
+        "line": 72
       },
       "name": "NpmJsProps",
       "namespace": "sources",
@@ -22214,7 +22214,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/package-sources/npmjs.ts",
-            "line": 108
+            "line": 113
           },
           "name": "canaryMaxStale",
           "optional": true,
@@ -22232,7 +22232,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/package-sources/npmjs.ts",
-            "line": 89
+            "line": 94
           },
           "name": "canaryPackage",
           "optional": true,
@@ -22251,7 +22251,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/package-sources/npmjs.ts",
-            "line": 98
+            "line": 103
           },
           "name": "canarySla",
           "optional": true,
@@ -22269,7 +22269,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/package-sources/npmjs.ts",
-            "line": 81
+            "line": 86
           },
           "name": "enableCanary",
           "optional": true,
@@ -22287,7 +22287,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/package-sources/npmjs.ts",
-            "line": 73
+            "line": 78
           },
           "name": "stagingBucket",
           "optional": true,
@@ -22299,6 +22299,6 @@
       "symbolId": "src/package-sources/npmjs:NpmJsProps"
     }
   },
-  "version": "0.4.520",
-  "fingerprint": "gCAq9NQCy5mOJ7e6+ezNj2eHmcq3fNdCtC+v3L40gBA="
+  "version": "0.4.522",
+  "fingerprint": "JMcRJP5n4oIU2h3WsTaiKhDDZVkhZx71Y1u/nkzhQJ4="
 }

package/docs/operator-runbook.md

@@ -753,6 +753,21 @@ latest version was ingested out-of-SLA.
 
 #### Investigation
 
+Start with the *Package Canary* section of the backend dashboard. The *Stuck
+Versions* widget lists the tracked package versions the canary is still waiting
+for (with how long each has been outstanding), and the *Pipeline Trace* button
+opens a Log Analytics query showing every follower and stager log line
+mentioning the tracked package (a comment in the query shows how to narrow it
+down to one stuck version). A healthy version shows the full sequence (follower
+sends it for staging, stager downloads and stores the tarball, then notifies
+the ingestion queue); the point where a stuck version's trail stops indicates
+which component dropped it. Lines that do not mention the package name are not
+part of the trace, so also check the surrounding log stream of the last
+component that saw the version. For example, a `404` logged by the stager right
+after the download line means the tarball was not yet available on npm's CDN
+when the version was discovered, and the version was dropped (see the
+Resolution below to re-stage it).
+
 If the alarm went off due to insufficient data, the canary might not be emitting
 metrics properly. In this case, start by ensuring the lambda function that
 implements the canary is executing as intended. It is normally scheduled to run