docs(traceroute): add canonical frontmatter, merge main, regenerate sitemap

Bring the branch up to date with main (it was ~1485 commits behind, predating
the sitemap tooling + frontmatter check), add the required canonical URLs to the
three Traceroute monitor pages, and regenerate sitemap.xml to include them.
Fixes the static-docs-checks failure.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013AYwkvoaANQTH5dGStbBj2

Author: danielpaulus

constructs/traceroute-monitor.mdx

@@ -2,6 +2,7 @@
 title: 'TracerouteMonitor Construct'
 description: 'Learn how to configure Traceroute monitors with the Checkly CLI.'
 sidebarTitle: 'Traceroute Monitor'
+canonical: 'https://www.checklyhq.com/docs/constructs/traceroute-monitor/'
 ---
 
 import GeneralMonitorOptionsTable from '/snippets/general-monitor-options-table.mdx';
@@ -59,7 +60,7 @@ new TracerouteMonitor('traceroute-db', {
     timeout: 15,
     assertions: [
       TracerouteAssertionBuilder.hopCount().lessThan(15),
-      TracerouteAssertionBuilder.responseTime().avg().lessThan(50),
+      TracerouteAssertionBuilder.responseTime('avg').lessThan(50),
       TracerouteAssertionBuilder.packetLoss().lessThan(5),
     ],
   },
@@ -117,7 +118,7 @@ new TracerouteMonitor('traceroute-monitor', {
 |-----------|------|----------|---------|-------------|
 | `url` | `string` | ✅ | - | Target hostname or IP address. Do not include a scheme or port |
 | `protocol` | `string` | ❌ | `'TCP'` | Probe protocol: `'TCP'` \| `'UDP'` \| `'ICMP'` \| `'SCTP'` |
-| `port` | `number` | ❌ | `443` | Destination port (1–65535). Defaults to `443` for all non-ICMP protocols. For UDP/SCTP, set `port: 33434` explicitly — a high closed port so the destination returns ICMP Unreachable to confirm arrival. Ignored when `protocol` is `'ICMP'` |
+| `port` | `number` | ❌ | `443` (TCP) / `33434` (UDP, SCTP) | Destination port (1–65535). Defaults to `443` for TCP and to `33434` — a high, typically closed port — for UDP/SCTP, so the destination returns ICMP Destination Unreachable to confirm arrival. Ignored (and not sent) when `protocol` is `'ICMP'` |
 | `ipFamily` | `string` | ❌ | `'IPv4'` | IP family: `'IPv4'` \| `'IPv6'` |
 | `maxHops` | `number` | ❌ | `30` | Maximum hops to probe (1–64) |
 | `maxUnknownHops` | `number` | ❌ | `15` | Maximum consecutive unresponsive hops before stopping (1–30) |
@@ -163,7 +164,7 @@ new TracerouteMonitor("traceroute-latency-tiers", {
 
 Assertions for Traceroute monitors are defined using the `TracerouteAssertionBuilder`. The following sources are available:
 
-- `responseTime(property?)`: Validate RTT at the final responding hop. Defaults to the `avg` property. Use `.avg()`, `.min()`, `.max()`, or `.stdDev()` to target a specific statistic. This assertion fails when `destinationReached` is `false`
+- `responseTime(property?)`: Validate RTT at the final responding hop. Pass `'avg'`, `'min'`, `'max'`, or `'stdDev'` as the argument to target a specific statistic; when omitted, it defaults to `'avg'`. This assertion fails when `destinationReached` is `false`
 - `hopCount()`: Assert against the total number of hops recorded in the trace
 - `packetLoss()`: Assert against the packet loss percentage at the last recorded hop (0–100)
 
@@ -180,7 +181,7 @@ TracerouteAssertionBuilder.responseTime().lessThan(100)
 - Assert against a specific RTT property:
 
 ```ts
-TracerouteAssertionBuilder.responseTime().max().lessThan(200)
+TracerouteAssertionBuilder.responseTime('max').lessThan(200)
 // Equivalent to:
 { source: 'RESPONSE_TIME', property: 'max', comparison: 'LESS_THAN', target: '200' }
 ```

detect/uptime-monitoring/traceroute-monitors/configuration.mdx

@@ -2,6 +2,7 @@
 title: 'Traceroute Monitor Configuration'
 description: 'Configure your Traceroute monitor to map network paths and detect routing issues, latency, and packet loss.'
 sidebarTitle: 'Configuration'
+canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/traceroute-monitors/configuration/'
 ---
 
 <Tip>
@@ -46,22 +47,22 @@ Response-time thresholds apply to the **final-hop average RTT**, not the total c
 
 ### JSON Response Schema
 
-The Traceroute response is available as structured JSON. All responses share this format:
+The Traceroute response is available as structured JSON. These are the key fields (a few internal bookkeeping fields are omitted here, and fields marked as omitted are absent from the JSON rather than empty):
 
 ```json
 {
   "hostname": "api.example.com",          // Target hostname or IP as configured
   "resolvedIp": "93.184.216.34",          // IP address used for the trace
-  "port": 443,                             // Destination port; always present (0 for ICMP probes)
+  "port": 443,                             // Destination port; for ICMP probes this reports the unused fallback 443
   "ipFamily": "IPv4",                      // "IPv4" or "IPv6"
   "maxHops": 30,                           // Configured max hops
   "totalHops": 12,                         // Number of hops actually recorded
   "destinationReached": true,              // Whether the destination responded
   "truncationReason": "destinationReached",// Why the trace stopped:
                                            // "destinationReached" | "maxHops" | "maxUnknownHops" | "timeout"
   "probeProtocol": "TCP",                 // Probe protocol: "TCP" | "UDP" | "ICMP" | "SCTP"
-  "finalHopLatency": {                     // RTT stats for the last responding hop
-    "avg": 12.34,                         // Omitted entirely (field absent) when destination is not reached
+  "finalHopLatency": {                     // RTT stats for the last responding hop (the whole object is omitted when the destination is not reached)
+    "avg": 12.34,
     "min": 11.80,
     "max": 13.10,
     "stdDev": 0.42
@@ -70,22 +71,22 @@ The Traceroute response is available as structured JSON. All responses share thi
     {
       "hop_number": 1,
       "main_ip": "10.0.0.1",              // Primary IP observed at this hop
-      "main_host": "router.isp.net",      // Reverse-DNS hostname (empty when PTR lookup is off or lookup fails)
+      "main_host": "router.isp.net",      // Reverse-DNS hostname (omitted when PTR lookup is off or the lookup fails)
       "sent": 3,                           // Probe packets sent to this hop
       "received": 3,                       // Replies received from this hop
       "loss_percentage": 0.0,             // Packet loss at this hop
-      "rtt": {
+      "rtt": {                             // RTT stats (omitted when the hop never replied)
         "last_ms": 1.23,                 // RTT of the most recent probe
         "avg_ms": 1.10,                  // Average RTT across all probes
         "best_ms": 0.95,                 // Minimum RTT
         "worst_ms": 1.23,               // Maximum RTT
         "stddev_ms": 0.12               // Standard deviation
       },
-      "asn": 15169,                        // Autonomous System Number (0 if unknown)
-      "asn_org": "GOOGLE",               // AS organization name
-      "country": "US",                   // Two-letter country code
-      "aws_region": "",                  // AWS region name (if hop is in AWS)
-      "aws_service": ""                  // AWS service name (if hop is in AWS)
+      "asn": 15169,                        // Autonomous System Number (omitted when unknown)
+      "asn_org": "GOOGLE",               // AS organization name (omitted when unknown)
+      "country": "US",                   // Two-letter country code (omitted when unknown)
+      "aws_region": "us-east-1",         // AWS region — only present when the hop is inside AWS
+      "aws_service": "EC2"               // AWS service — only present when the hop is inside AWS
     }
     // ... one entry per recorded hop
   ],

detect/uptime-monitoring/traceroute-monitors/overview.mdx

@@ -2,6 +2,7 @@
 title: 'Traceroute Monitors Overview'
 description: 'Map the network path to any host and detect routing issues, high-latency hops, and packet loss.'
 sidebarTitle: Overview
+canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/traceroute-monitors/overview/'
 ---
 
 <Tip>
@@ -22,7 +23,7 @@ Traceroute monitors map the network path between a Checkly location and your tar
 A Traceroute monitor executes the following steps on each run:
 
 1. **Hostname resolution**: If a hostname is provided, Checkly resolves it to an IP address before sending any probes
-2. **Probe execution**: The runner sends probe packets using the configured protocol (TCP by default). Each probe carries a progressively higher TTL so each router on the path responds with an ICMP Time Exceeded message before forwarding the packet
+2. **Probe execution**: The runner sends probe packets using the configured protocol (TCP by default). Each probe carries a progressively higher TTL, so each router on the path in turn drops the probe whose TTL expires there and responds with an ICMP Time Exceeded message
 3. **Hop collection**: RTT statistics (avg, min, max, stddev) and packet loss are collected for each router hop along the path
 4. **Destination detection**: When the destination host responds directly, the trace is complete and `destinationReached` is set to `true`
 5. **Assertion evaluation**: Configured assertions are evaluated against the results — including final-hop latency, total hop count, and last-hop packet loss
@@ -34,10 +35,10 @@ A Traceroute monitor executes the following steps on each run:
 | **TCP** (default) | 443 | SYN-ACK or RST received from destination |
 | **UDP** | 33434 | Any ICMP Destination Unreachable from the target (port unreachable, admin-prohibited, host unreachable, etc.) |
 | **ICMP** | *(no port)* | Echo Reply from destination |
-| **SCTP** | 33434 | SCTP ABORT or INIT-ACK from destination, or ICMP Destination Unreachable from the target |
+| **SCTP** | 33434 | Any ICMP Destination Unreachable from the target (protocol unreachable, port unreachable, etc.) |
 
 <Note>
-The default port for UDP and SCTP in the Checkly web UI is pre-filled to `33434` — a high, typically-closed port where the destination is more likely to return an ICMP Destination Unreachable. When configuring via the CLI or API, the port defaults to `443` for all non-ICMP protocols, so set `port: 33434` explicitly for UDP/SCTP probes if you want the same behavior.
+The default port is protocol-dependent everywhere — web UI, CLI, and API: `443` for TCP and `33434` for UDP/SCTP. `33434` is a high, typically-closed port: UDP and SCTP arrival is only confirmed when the destination returns an ICMP Destination Unreachable, which requires the probed port to be closed. Avoid setting an open port (like `443`) for UDP/SCTP probes — it would never confirm arrival.
 </Note>
 
 ## Traceroute Monitor Results
@@ -71,7 +72,7 @@ Learn more in our documentation on [Results](/concepts/results).
 
 **How to fix**:
 1. Switch the probe protocol — try `ICMP` if the host responds to ping, or `UDP` for a connectionless probe
-2. Change the port to one that is explicitly open on the target (e.g. `80` or `22`)
+2. For TCP probes, change the port to one that is explicitly open on the target (e.g. `80` or `22`). For UDP/SCTP, keep a *closed* port — arrival is only confirmed by an ICMP Destination Unreachable reply
 3. Confirm reachability at the application layer with an [API Monitor](/detect/synthetic-monitoring/overview) or [TCP Monitor](/detect/uptime-monitoring/tcp-monitors/overview) targeting the same host and port
 </Accordion>
 
@@ -88,7 +89,7 @@ Learn more in our documentation on [Results](/concepts/results).
 <Accordion title="SCTP or raw-socket errors on private locations">
 **Symptom**: SCTP probes fail with a socket permission error on a self-hosted Checkly Agent.
 
-**Root cause**: SCTP probes require raw sockets, which need `CAP_NET_RAW`. Container runtimes drop this capability by default.
+**Root cause**: Container runtimes drop `CAP_NET_RAW` by default. Traceroute monitors always need it — hop discovery listens for ICMP replies on a raw socket regardless of probe protocol — but SCTP is the case that surfaces an explicit socket error, because SCTP probes are also *sent* over a raw socket.
 
 **How to fix** — In **Kubernetes**, update your pod spec or Helm values:
 

sitemap.xml

@@ -903,6 +903,9 @@
   <url>
     <loc>https://www.checklyhq.com/docs/constructs/telegram-alert-channel/</loc>
   </url>
+  <url>
+    <loc>https://www.checklyhq.com/docs/constructs/traceroute-monitor/</loc>
+  </url>
   <url>
     <loc>https://www.checklyhq.com/docs/constructs/url-monitor/</loc>
   </url>
@@ -1077,6 +1080,12 @@
   <url>
     <loc>https://www.checklyhq.com/docs/detect/uptime-monitoring/tcp-monitors/quickstart/</loc>
   </url>
+  <url>
+    <loc>https://www.checklyhq.com/docs/detect/uptime-monitoring/traceroute-monitors/configuration/</loc>
+  </url>
+  <url>
+    <loc>https://www.checklyhq.com/docs/detect/uptime-monitoring/traceroute-monitors/overview/</loc>
+  </url>
   <url>
     <loc>https://www.checklyhq.com/docs/detect/uptime-monitoring/url-monitors/configuration/</loc>
   </url>