fix(nextjs): correctly drop tunnel-route spans for full URLs

packages/nextjs/src/common/utils/dropMiddlewareTunnelRequests.ts

@@ -54,12 +54,35 @@
   // eslint-disable-next-line deprecation/deprecation
   const httpTarget = spanAttributes[SEMATTRS_HTTP_TARGET];
 
-  if (typeof httpTarget === 'string') {
-    // Extract pathname from the target (e.g., "/tunnel?o=123&p=456" -> "/tunnel")
-    const pathname = httpTarget.split('?')[0] || '';
+  if (typeof httpTarget !== 'string') {
+    return false;
+  }
+
+  // Next.js / OTel can sometimes report `http.target` as a full URL (including scheme/host), e.g.
+  // "https://example.com/monitoring/tunnel?o=...". In that case, comparing the raw string to the tunnel
+  // route path would fail.
+  const pathname = extractPathnameFromHttpTarget(httpTarget);
+  if (!pathname) {
+    return false;
+  }
+
+  const normalizedTunnelPath = tunnelPath.startsWith('/') ? tunnelPath : `/${tunnelPath}`;
+  return pathname === normalizedTunnelPath || pathname.startsWith(normalizedTunnelPath + '/');
+}
+
+function extractPathnameFromHttpTarget(httpTarget: string): string {
+  if (!httpTarget) {
+    return '';
+  }
 
-    return pathname.startsWith(tunnelPath);
+  if (httpTarget.startsWith('http://') || httpTarget.startsWith('https://')) {
+    try {
+      return new URL(httpTarget).pathname;
+    } catch {
+      // Fall back to best-effort parsing below.
+    }
   }
 
-  return false;
+  // Example: "/tunnel?o=123&p=456" -> "/tunnel"
+  return httpTarget.split('?')[0] || '';
 }