feat(node)!: Use function span op for hapi plugin route handlers

A plugin-registered hapi route runs the user's request handler, so it is a
terminal handler like the express/fastify/hono routes in this migration.
Map `plugin.hapi` to the cross-framework `function` op; `router.hapi` and
`server.ext.hapi` (framework routing/extension lifecycle) keep their ops.

Op is set via the `sentry.op` attribute only; `hapi.type` is unchanged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: msonnb

dev-packages/node-integration-tests/suites/tracing/hapi/scenario.mjs

@@ -51,7 +51,7 @@ const run = async () => {
     },
   });
 
-  // Route registered via a plugin produces a `plugin.hapi` span.
+  // Route registered via a plugin produces a `function` op span.
   await server.register({
     name: 'testPlugin',
     version: '1.0.0',

dev-packages/node-integration-tests/suites/tracing/hapi/test.ts

@@ -58,13 +58,13 @@ describe('hapi auto-instrumentation', () => {
             spans: expect.arrayContaining([
               expect.objectContaining({
                 description: 'GET /plugin-route',
-                op: 'plugin.hapi',
+                op: 'function',
                 origin,
                 data: expect.objectContaining({
                   'http.route': '/plugin-route',
                   'hapi.type': 'plugin',
                   'hapi.plugin.name': 'testPlugin',
-                  'sentry.op': 'plugin.hapi',
+                  'sentry.op': 'function',
                   'sentry.origin': origin,
                 }),
               }),

packages/server-utils/src/integrations/tracing-channel/hapi-utils.ts

@@ -2,12 +2,15 @@
  * OTel-free, `@hapi/*`-free port of the span-building helpers and handler/ext
  * wrap logic from the vendored `@opentelemetry/instrumentation-hapi`
  * (upstream @opentelemetry/instrumentation-hapi@0.64.0). Span output (names,
- * ops, origins, attributes) is kept byte-identical to that instrumentation;
+ * origins, attributes) is kept close to that instrumentation — except the
+ * plugin-route op, which is normalized to the cross-framework `function` op;
  * span creation goes through the `@sentry/core` API and the OTel active-span
  * guard is replaced with `getActiveSpan()`.
  */
 
 import { getActiveSpan, SEMANTIC_ATTRIBUTE_SENTRY_ORIGIN, startSpan } from '@sentry/core';
+import { SENTRY_OP } from '@sentry/conventions/attributes';
+import { WEB_SERVER_FUNCTION_SPAN_OP } from '@sentry/conventions/op';
 import type {
   LifecycleMethod,
   PatchableExtMethod,
@@ -104,12 +107,14 @@ export const getExtMetadata = (
 };
 
 function startMetadataSpan(metadata: SpanMetadata, original: () => unknown): unknown {
+  const hapiType = metadata.attributes[AttributeNames.HAPI_TYPE];
+  const op = hapiType === HapiLayerType.PLUGIN ? WEB_SERVER_FUNCTION_SPAN_OP : `${hapiType}.hapi`;
   return startSpan(
     {
       name: metadata.name,
-      op: `${metadata.attributes[AttributeNames.HAPI_TYPE]}.hapi`,
       attributes: {
         ...metadata.attributes,
+        [SENTRY_OP]: op,
         [SEMANTIC_ATTRIBUTE_SENTRY_ORIGIN]: 'auto.http.hapi',
       },
     },