autotel-plugins 0.19.2 → 0.19.4

package/README.md

@@ -6,8 +6,8 @@ OpenTelemetry instrumentation for libraries **without official support** OR wher
 
 **autotel-plugins only includes instrumentation that:**
 
-1. **Has NO official OpenTelemetry package** (e.g., Drizzle ORM)
-2. **Has BROKEN official instrumentation** (e.g., Mongoose in ESM+tsx)
+1. **Has NO official OpenTelemetry package** (e.g., BigQuery)
+2. **Has BROKEN official instrumentation**
 3. **Adds significant value** beyond official packages
 
 **We do NOT include:**
@@ -57,10 +57,6 @@ For databases/ORMs with **working** official instrumentation, **use those direct
 
 [Browse all official instrumentations →](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node)
 
-### ⚠️ Mongoose ESM Exception
-
-**Note:** [`@opentelemetry/instrumentation-mongoose`](https://www.npmjs.com/package/@opentelemetry/instrumentation-mongoose) is fundamentally broken in ESM+tsx environments due to module loading hook issues. It works in CommonJS, but if you're using ESM with tsx/ts-node, use our custom plugin below.
-
 ## Installation
 
 Install the package and **autotel** (required for all plugins):
@@ -75,20 +71,12 @@ Each plugin needs the core packages above plus the library (and optional OTel in
 
 | Plugin       | Install                                                                                                                    |
 | ------------ | -------------------------------------------------------------------------------------------------------------------------- |
-| **Mongoose** | `autotel` + `autotel-plugins` + `mongoose`                                                                                 |
-| **Drizzle**  | `autotel` + `autotel-plugins` + `drizzle-orm` + your driver (e.g. `postgres`, `mysql2`, `better-sqlite3`)                  |
 | **BigQuery** | `autotel` + `autotel-plugins` + `@google-cloud/bigquery`                                                                   |
 | **Kafka**    | `autotel` + `autotel-plugins` + `kafkajs`. Optional: `@opentelemetry/instrumentation-kafkajs` for producer/consumer spans. |
 
 Examples:
 
 ```bash
-# Mongoose
-npm install autotel autotel-plugins mongoose
-
-# Drizzle (e.g. Postgres)
-npm install autotel autotel-plugins drizzle-orm postgres
-
 # BigQuery
 npm install autotel autotel-plugins @google-cloud/bigquery
 
@@ -98,209 +86,6 @@ npm install autotel autotel-plugins kafkajs @opentelemetry/instrumentation-kafka
 
 ## Currently Supported
 
-### Mongoose
-
-Instrument Mongoose database operations with OpenTelemetry tracing using runtime patching. Works in ESM+tsx unlike the official package. **✨ NEW: Automatic hook instrumentation - no manual trace() calls needed!**
-
-**Why we provide this:**
-
-The official [`@opentelemetry/instrumentation-mongoose`](https://www.npmjs.com/package/@opentelemetry/instrumentation-mongoose) package is fundamentally broken in ESM+tsx environments:
-
-- Uses module loading hooks (`import-in-the-middle`) that fail with ESM import hoisting
-- Mongoose package lacks proper dual-mode exports (CJS only)
-- Works in CommonJS, but fails in modern ESM projects
-- No timeline for ESM support
-
-Our implementation uses **runtime patching** instead of module loading hooks, so it works everywhere.
-
-#### Basic Usage (with Automatic Hook Tracing)
-
-```typescript
-import mongoose from 'mongoose';
-import { init } from 'autotel';
-import { instrumentMongoose } from 'autotel-plugins/mongoose';
-
-// Initialize Autotel
-init({ service: 'my-app' });
-
-// IMPORTANT: Instrument BEFORE defining schemas to enable automatic hook tracing
-instrumentMongoose(mongoose, {
-  dbName: 'myapp',
-  peerName: 'localhost',
-  peerPort: 27017,
-});
-
-// NOW define schemas - hooks are automatically traced!
-const userSchema = new mongoose.Schema({ name: String, email: String });
-
-userSchema.pre('save', async function () {
-  // ✨ This hook is AUTOMATICALLY traced - no manual trace() needed!
-  this.email = this.email.toLowerCase();
-});
-
-const User = mongoose.model('User', userSchema);
-
-// Connect to MongoDB
-await mongoose.connect('mongodb://localhost:27017/myapp');
-
-// All operations AND hooks are automatically traced
-await User.create({ name: 'Alice', email: 'ALICE@EXAMPLE.COM' });
-// Creates spans: mongoose.users.create + mongoose.users.pre.save
-```
-
-#### What Gets Automatically Traced
-
-**1. Model Operations** (all automatic):
-
-- `create`, `insertMany`, `find`, `findOne`, `findById`
-- `findOneAndUpdate`, `findByIdAndUpdate`, `updateOne`, `updateMany`
-- `deleteOne`, `deleteMany`, `countDocuments`, `aggregate`
-- Instance methods: `save`, `remove`, `deleteOne`
-
-**2. Schema Hooks** (automatic - no manual code needed!):
-
-- Pre hooks: `pre('save')`, `pre('findOneAndUpdate')`, etc.
-- Post hooks: `post('save')`, `post('remove')`, etc.
-- Built-in hooks: `post('init')` (document hydration)
-
-#### Hook Instrumentation Setup
-
-For automatic hook tracing, call `instrumentMongoose()` **before** defining schemas. ESM import hoisting means you need a separate init file:
-
-**Pattern for ESM+tsx projects:**
-
-Create `init-mongoose.ts`:
-
-```typescript
-import mongoose from 'mongoose';
-import { instrumentMongoose } from 'autotel-plugins/mongoose';
-
-instrumentMongoose(mongoose, { dbName: 'myapp' });
-```
-
-Import before schemas in `index.ts`:
-
-```typescript
-import './init-mongoose'; // Import first!
-import { User, Post } from './schema'; // Hooks auto-instrumented
-```
-
-#### Configuration
-
-```typescript
-{
-  dbName?: string                  // Database name
-  captureCollectionName?: boolean  // Include collection in spans (default: true)
-  peerName?: string                // MongoDB host
-  peerPort?: number                // MongoDB port (default: 27017)
-  tracerName?: string              // Custom tracer name
-}
-```
-
-#### Span Attributes
-
-**Operation Spans (SpanKind.CLIENT):**
-
-- `db.system` - "mongoose"
-- `db.operation` - create, find, update, etc.
-- `db.mongodb.collection` - Collection name
-- `db.name` - Database name
-- `net.peer.name` / `net.peer.port` - MongoDB server
-
-**Hook Spans (SpanKind.INTERNAL):**
-
-- `hook.type` - "pre" or "post"
-- `hook.operation` - save, findOneAndUpdate, etc.
-- `hook.model` - Model name (User, Post, etc.)
-- `db.mongodb.collection` - Collection name
-- `db.system` - "mongoose"
-- `db.name` - Database name
-
-#### Before vs After (70% Less Code!)
-
-**Before (Manual instrumentation):**
-
-```typescript
-import { trace } from 'autotel';
-
-userSchema.pre('save', async function () {
-  await trace((ctx) => async () => {
-    ctx.setAttribute('hook.type', 'pre');
-    ctx.setAttribute('hook.operation', 'save');
-    // ... lots of boilerplate
-    this.email = this.email.toLowerCase();
-  })();
-});
-```
-
-**After (Automatic instrumentation):**
-
-```typescript
-// NO trace() imports needed!
-userSchema.pre('save', async function () {
-  // Automatically traced with all attributes!
-  this.email = this.email.toLowerCase();
-});
-```
-
-### Drizzle ORM
-
-Instrument Drizzle database operations with OpenTelemetry tracing. Drizzle doesn't have official instrumentation, so we provide it here.
-
-```typescript
-import { drizzle } from 'drizzle-orm/postgres-js';
-import postgres from 'postgres';
-import { instrumentDrizzleClient } from 'autotel-plugins/drizzle';
-
-const queryClient = postgres(process.env.DATABASE_URL!);
-const db = drizzle({ client: queryClient });
-
-// Instrument the database instance
-instrumentDrizzleClient(db, {
-  dbSystem: 'postgresql',
-  dbName: 'myapp',
-  peerName: 'db.example.com',
-  peerPort: 5432,
-  captureQueryText: true,
-});
-
-// All queries are now traced
-await db.select().from(users).where(eq(users.id, 123));
-```
-
-**Supported databases:**
-
-- PostgreSQL (node-postgres, postgres.js)
-- MySQL (mysql2)
-- SQLite (better-sqlite3, LibSQL/Turso)
-
-**Functions:**
-
-- `instrumentDrizzle(client, config)` - Instrument a database client/pool
-- `instrumentDrizzleClient(db, config)` - Instrument a Drizzle database instance
-
-**Configuration:**
-
-```typescript
-{
-  dbSystem?: string           // Database type (postgresql, mysql, sqlite)
-  dbName?: string            // Database name
-  captureQueryText?: boolean // Capture SQL in spans (default: true)
-  maxQueryTextLength?: number // Max SQL length (default: 1000)
-  peerName?: string          // Database host
-  peerPort?: number          // Database port
-}
-```
-
-**Span Attributes:**
-
-- `db.system` - Database type (postgresql, mysql, sqlite)
-- `db.operation` - Operation name (SELECT, INSERT, UPDATE, DELETE)
-- `db.name` - Database name
-- `db.statement` - SQL query text (if `captureQueryText: true`)
-- `net.peer.name` - Database host
-- `net.peer.port` - Database port
-
 ### Kafka
 
 Composition layer for KafkaJS: processing span wrapper, producer span wrapper, batch lineage for fan-in trace correlation, and batch consumer wrapper. Works alongside optional `@opentelemetry/instrumentation-kafkajs` for producer/consumer spans.
@@ -334,38 +119,12 @@ await consumer.run({
 
 Optional: install `@opentelemetry/instrumentation-kafkajs` for producer/consumer spans.
 
-## Usage with Autotel
-
-Drizzle instrumentation works seamlessly with [Autotel](../autotel):
-
-```typescript
-import { init } from 'autotel';
-import { instrumentDrizzleClient } from 'autotel-plugins/drizzle';
-import { drizzle } from 'drizzle-orm/postgres-js';
-import postgres from 'postgres';
-
-// Initialize Autotel
-init({
-  service: 'my-service',
-  endpoint: 'http://localhost:4318',
-});
-
-// Instrument your database
-const client = postgres(process.env.DATABASE_URL!);
-const db = drizzle({ client });
-instrumentDrizzleClient(db, { dbSystem: 'postgresql' });
-
-// Traces will be sent to your OTLP endpoint
-await db.select().from(users);
-```
-
 ## Combining with Official Packages
 
 Mix autotel-plugins with official OpenTelemetry instrumentations:
 
 ```typescript
 import { init } from 'autotel';
-import { instrumentDrizzleClient } from 'autotel-plugins/drizzle';
 import { HttpInstrumentation } from '@opentelemetry/instrumentation-http';
 import { ExpressInstrumentation } from '@opentelemetry/instrumentation-express';
 import { PgInstrumentation } from '@opentelemetry/instrumentation-pg';
@@ -378,47 +137,8 @@ init({
     new PgInstrumentation(), // Official packages
   ],
 });
-
-// Drizzle (no official package available)
-const db = drizzle({ client: postgres(process.env.DATABASE_URL!) });
-instrumentDrizzleClient(db, { dbSystem: 'postgresql' });
 ```
 
-## Security Considerations
-
-### Query Text Capture
-
-By default, Drizzle instrumentation captures SQL text which may contain sensitive data:
-
-```typescript
-// Disable SQL capture to prevent PII leakage
-instrumentDrizzleClient(db, {
-  captureQueryText: false,
-});
-```
-
-## Examples
-
-See the [example-drizzle](../../apps/example-drizzle) directory for a complete working example.
-
-## TypeScript
-
-Full type safety with TypeScript:
-
-```typescript
-import type { InstrumentDrizzleConfig } from 'autotel-plugins';
-
-const config: InstrumentDrizzleConfig = {
-  dbSystem: 'postgresql',
-  captureQueryText: true,
-  maxQueryTextLength: 1000,
-};
-```
-
-## Future
-
-When official OpenTelemetry instrumentation becomes available for Drizzle ORM, we will announce deprecation and provide a migration guide.
-
 ## Creating Your Own Instrumentation
 
 Don't see your library here? Autotel makes it easy to create custom instrumentation for any library using simple, well-tested utilities.

package/dist/bigquery.d.cts

@@ -1,4 +1,4 @@
-import { BigQuery, BigQueryOptions } from '@google-cloud/bigquery';
+import { BigQueryOptions, BigQuery } from '@google-cloud/bigquery';
 
 /**
  * Plugin-only options for BigQuery instrumentation (not part of official BigQueryOptions).

package/dist/bigquery.d.ts

@@ -1,4 +1,4 @@
-import { BigQuery, BigQueryOptions } from '@google-cloud/bigquery';
+import { BigQueryOptions, BigQuery } from '@google-cloud/bigquery';
 
 /**
  * Plugin-only options for BigQuery instrumentation (not part of official BigQueryOptions).

package/dist/{constants-DoaoDYT8.d.cts → constants-DKKe2D25.d.cts}

@@ -49,4 +49,4 @@ declare const SEMATTRS_MESSAGING_KAFKA_BATCH_MESSAGES_PROCESSED: "messaging.kafk
 declare const SEMATTRS_MESSAGING_KAFKA_BATCH_MESSAGES_FAILED: "messaging.kafka.batch.messages_failed";
 declare const SEMATTRS_MESSAGING_KAFKA_BATCH_PROCESSING_TIME_MS: "messaging.kafka.batch.processing_time_ms";
 
-export { SEMATTRS_MESSAGING_KAFKA_OFFSET as A, SEMATTRS_MESSAGING_KAFKA_MESSAGE_KEY as B, SEMATTRS_LINKED_TRACE_ID_COUNT as C, SEMATTRS_LINKED_TRACE_ID_HASH as D, CORRELATION_ID_HEADER as E, SEMATTRS_MESSAGING_BATCH_MESSAGE_COUNT as F, SEMATTRS_MESSAGING_KAFKA_BATCH_FIRST_OFFSET as G, SEMATTRS_MESSAGING_KAFKA_BATCH_LAST_OFFSET as H, SEMATTRS_MESSAGING_KAFKA_BATCH_MESSAGES_PROCESSED as I, SEMATTRS_MESSAGING_KAFKA_BATCH_MESSAGES_FAILED as J, SEMATTRS_MESSAGING_KAFKA_BATCH_PROCESSING_TIME_MS as K, SEMATTRS_MESSAGING_OPERATION_NAME as L, SEMATTRS_MESSAGING_MESSAGE_ID as M, SEMATTRS_MESSAGING_MESSAGE_CONVERSATION_ID as N, SEMATTRS_MESSAGING_CONSUMER_ID as O, SEMATTRS_MESSAGING_RABBITMQ_DESTINATION_ROUTING_KEY as P, SEMATTRS_MESSAGING_RABBITMQ_DESTINATION_EXCHANGE as Q, SEMATTRS_MESSAGING_RABBITMQ_ACK_RESULT as R, SEMATTRS_DB_SYSTEM as S, SEMATTRS_MESSAGING_RABBITMQ_REQUEUE as T, SEMATTRS_DB_SYSTEM_NAME as a, SEMATTRS_DB_OPERATION as b, SEMATTRS_DB_OPERATION_NAME as c, SEMATTRS_DB_STATEMENT as d, SEMATTRS_DB_NAME as e, SEMATTRS_DB_NAMESPACE as f, SEMATTRS_DB_COLLECTION_NAME as g, SEMATTRS_DB_QUERY_TEXT as h, SEMATTRS_DB_QUERY_SUMMARY as i, SEMATTRS_NET_PEER_NAME as j, SEMATTRS_NET_PEER_PORT as k, SEMATTRS_GCP_BIGQUERY_JOB_ID as l, SEMATTRS_GCP_BIGQUERY_JOB_LOCATION as m, SEMATTRS_GCP_BIGQUERY_PROJECT_ID as n, SEMATTRS_GCP_BIGQUERY_DESTINATION_TABLE as o, SEMATTRS_GCP_BIGQUERY_SOURCE_TABLES as p, SEMATTRS_GCP_BIGQUERY_STATEMENT_TYPE as q, SEMATTRS_GCP_BIGQUERY_QUERY_HASH as r, SEMATTRS_GCP_BIGQUERY_ROWS_AFFECTED as s, SEMATTRS_GCP_BIGQUERY_ROWS_RETURNED as t, SEMATTRS_GCP_BIGQUERY_SCHEMA_FIELDS as u, SEMATTRS_MESSAGING_SYSTEM as v, SEMATTRS_MESSAGING_DESTINATION_NAME as w, SEMATTRS_MESSAGING_OPERATION as x, SEMATTRS_MESSAGING_KAFKA_CONSUMER_GROUP as y, SEMATTRS_MESSAGING_KAFKA_PARTITION as z };
+export { SEMATTRS_MESSAGING_KAFKA_BATCH_MESSAGES_FAILED as A, SEMATTRS_MESSAGING_KAFKA_BATCH_MESSAGES_PROCESSED as B, CORRELATION_ID_HEADER as C, SEMATTRS_MESSAGING_KAFKA_BATCH_PROCESSING_TIME_MS as D, SEMATTRS_MESSAGING_KAFKA_CONSUMER_GROUP as E, SEMATTRS_MESSAGING_KAFKA_MESSAGE_KEY as F, SEMATTRS_MESSAGING_KAFKA_OFFSET as G, SEMATTRS_MESSAGING_KAFKA_PARTITION as H, SEMATTRS_MESSAGING_MESSAGE_CONVERSATION_ID as I, SEMATTRS_MESSAGING_MESSAGE_ID as J, SEMATTRS_MESSAGING_OPERATION as K, SEMATTRS_MESSAGING_OPERATION_NAME as L, SEMATTRS_MESSAGING_RABBITMQ_ACK_RESULT as M, SEMATTRS_MESSAGING_RABBITMQ_DESTINATION_EXCHANGE as N, SEMATTRS_MESSAGING_RABBITMQ_DESTINATION_ROUTING_KEY as O, SEMATTRS_MESSAGING_RABBITMQ_REQUEUE as P, SEMATTRS_MESSAGING_SYSTEM as Q, SEMATTRS_NET_PEER_NAME as R, SEMATTRS_DB_COLLECTION_NAME as S, SEMATTRS_NET_PEER_PORT as T, SEMATTRS_DB_NAME as a, SEMATTRS_DB_NAMESPACE as b, SEMATTRS_DB_OPERATION as c, SEMATTRS_DB_OPERATION_NAME as d, SEMATTRS_DB_QUERY_SUMMARY as e, SEMATTRS_DB_QUERY_TEXT as f, SEMATTRS_DB_STATEMENT as g, SEMATTRS_DB_SYSTEM as h, SEMATTRS_DB_SYSTEM_NAME as i, SEMATTRS_GCP_BIGQUERY_DESTINATION_TABLE as j, SEMATTRS_GCP_BIGQUERY_JOB_ID as k, SEMATTRS_GCP_BIGQUERY_JOB_LOCATION as l, SEMATTRS_GCP_BIGQUERY_PROJECT_ID as m, SEMATTRS_GCP_BIGQUERY_QUERY_HASH as n, SEMATTRS_GCP_BIGQUERY_ROWS_AFFECTED as o, SEMATTRS_GCP_BIGQUERY_ROWS_RETURNED as p, SEMATTRS_GCP_BIGQUERY_SCHEMA_FIELDS as q, SEMATTRS_GCP_BIGQUERY_SOURCE_TABLES as r, SEMATTRS_GCP_BIGQUERY_STATEMENT_TYPE as s, SEMATTRS_LINKED_TRACE_ID_COUNT as t, SEMATTRS_LINKED_TRACE_ID_HASH as u, SEMATTRS_MESSAGING_BATCH_MESSAGE_COUNT as v, SEMATTRS_MESSAGING_CONSUMER_ID as w, SEMATTRS_MESSAGING_DESTINATION_NAME as x, SEMATTRS_MESSAGING_KAFKA_BATCH_FIRST_OFFSET as y, SEMATTRS_MESSAGING_KAFKA_BATCH_LAST_OFFSET as z };

package/dist/{constants-DoaoDYT8.d.ts → constants-DKKe2D25.d.ts}

@@ -49,4 +49,4 @@ declare const SEMATTRS_MESSAGING_KAFKA_BATCH_MESSAGES_PROCESSED: "messaging.kafk
 declare const SEMATTRS_MESSAGING_KAFKA_BATCH_MESSAGES_FAILED: "messaging.kafka.batch.messages_failed";
 declare const SEMATTRS_MESSAGING_KAFKA_BATCH_PROCESSING_TIME_MS: "messaging.kafka.batch.processing_time_ms";
 
-export { SEMATTRS_MESSAGING_KAFKA_OFFSET as A, SEMATTRS_MESSAGING_KAFKA_MESSAGE_KEY as B, SEMATTRS_LINKED_TRACE_ID_COUNT as C, SEMATTRS_LINKED_TRACE_ID_HASH as D, CORRELATION_ID_HEADER as E, SEMATTRS_MESSAGING_BATCH_MESSAGE_COUNT as F, SEMATTRS_MESSAGING_KAFKA_BATCH_FIRST_OFFSET as G, SEMATTRS_MESSAGING_KAFKA_BATCH_LAST_OFFSET as H, SEMATTRS_MESSAGING_KAFKA_BATCH_MESSAGES_PROCESSED as I, SEMATTRS_MESSAGING_KAFKA_BATCH_MESSAGES_FAILED as J, SEMATTRS_MESSAGING_KAFKA_BATCH_PROCESSING_TIME_MS as K, SEMATTRS_MESSAGING_OPERATION_NAME as L, SEMATTRS_MESSAGING_MESSAGE_ID as M, SEMATTRS_MESSAGING_MESSAGE_CONVERSATION_ID as N, SEMATTRS_MESSAGING_CONSUMER_ID as O, SEMATTRS_MESSAGING_RABBITMQ_DESTINATION_ROUTING_KEY as P, SEMATTRS_MESSAGING_RABBITMQ_DESTINATION_EXCHANGE as Q, SEMATTRS_MESSAGING_RABBITMQ_ACK_RESULT as R, SEMATTRS_DB_SYSTEM as S, SEMATTRS_MESSAGING_RABBITMQ_REQUEUE as T, SEMATTRS_DB_SYSTEM_NAME as a, SEMATTRS_DB_OPERATION as b, SEMATTRS_DB_OPERATION_NAME as c, SEMATTRS_DB_STATEMENT as d, SEMATTRS_DB_NAME as e, SEMATTRS_DB_NAMESPACE as f, SEMATTRS_DB_COLLECTION_NAME as g, SEMATTRS_DB_QUERY_TEXT as h, SEMATTRS_DB_QUERY_SUMMARY as i, SEMATTRS_NET_PEER_NAME as j, SEMATTRS_NET_PEER_PORT as k, SEMATTRS_GCP_BIGQUERY_JOB_ID as l, SEMATTRS_GCP_BIGQUERY_JOB_LOCATION as m, SEMATTRS_GCP_BIGQUERY_PROJECT_ID as n, SEMATTRS_GCP_BIGQUERY_DESTINATION_TABLE as o, SEMATTRS_GCP_BIGQUERY_SOURCE_TABLES as p, SEMATTRS_GCP_BIGQUERY_STATEMENT_TYPE as q, SEMATTRS_GCP_BIGQUERY_QUERY_HASH as r, SEMATTRS_GCP_BIGQUERY_ROWS_AFFECTED as s, SEMATTRS_GCP_BIGQUERY_ROWS_RETURNED as t, SEMATTRS_GCP_BIGQUERY_SCHEMA_FIELDS as u, SEMATTRS_MESSAGING_SYSTEM as v, SEMATTRS_MESSAGING_DESTINATION_NAME as w, SEMATTRS_MESSAGING_OPERATION as x, SEMATTRS_MESSAGING_KAFKA_CONSUMER_GROUP as y, SEMATTRS_MESSAGING_KAFKA_PARTITION as z };
+export { SEMATTRS_MESSAGING_KAFKA_BATCH_MESSAGES_FAILED as A, SEMATTRS_MESSAGING_KAFKA_BATCH_MESSAGES_PROCESSED as B, CORRELATION_ID_HEADER as C, SEMATTRS_MESSAGING_KAFKA_BATCH_PROCESSING_TIME_MS as D, SEMATTRS_MESSAGING_KAFKA_CONSUMER_GROUP as E, SEMATTRS_MESSAGING_KAFKA_MESSAGE_KEY as F, SEMATTRS_MESSAGING_KAFKA_OFFSET as G, SEMATTRS_MESSAGING_KAFKA_PARTITION as H, SEMATTRS_MESSAGING_MESSAGE_CONVERSATION_ID as I, SEMATTRS_MESSAGING_MESSAGE_ID as J, SEMATTRS_MESSAGING_OPERATION as K, SEMATTRS_MESSAGING_OPERATION_NAME as L, SEMATTRS_MESSAGING_RABBITMQ_ACK_RESULT as M, SEMATTRS_MESSAGING_RABBITMQ_DESTINATION_EXCHANGE as N, SEMATTRS_MESSAGING_RABBITMQ_DESTINATION_ROUTING_KEY as O, SEMATTRS_MESSAGING_RABBITMQ_REQUEUE as P, SEMATTRS_MESSAGING_SYSTEM as Q, SEMATTRS_NET_PEER_NAME as R, SEMATTRS_DB_COLLECTION_NAME as S, SEMATTRS_NET_PEER_PORT as T, SEMATTRS_DB_NAME as a, SEMATTRS_DB_NAMESPACE as b, SEMATTRS_DB_OPERATION as c, SEMATTRS_DB_OPERATION_NAME as d, SEMATTRS_DB_QUERY_SUMMARY as e, SEMATTRS_DB_QUERY_TEXT as f, SEMATTRS_DB_STATEMENT as g, SEMATTRS_DB_SYSTEM as h, SEMATTRS_DB_SYSTEM_NAME as i, SEMATTRS_GCP_BIGQUERY_DESTINATION_TABLE as j, SEMATTRS_GCP_BIGQUERY_JOB_ID as k, SEMATTRS_GCP_BIGQUERY_JOB_LOCATION as l, SEMATTRS_GCP_BIGQUERY_PROJECT_ID as m, SEMATTRS_GCP_BIGQUERY_QUERY_HASH as n, SEMATTRS_GCP_BIGQUERY_ROWS_AFFECTED as o, SEMATTRS_GCP_BIGQUERY_ROWS_RETURNED as p, SEMATTRS_GCP_BIGQUERY_SCHEMA_FIELDS as q, SEMATTRS_GCP_BIGQUERY_SOURCE_TABLES as r, SEMATTRS_GCP_BIGQUERY_STATEMENT_TYPE as s, SEMATTRS_LINKED_TRACE_ID_COUNT as t, SEMATTRS_LINKED_TRACE_ID_HASH as u, SEMATTRS_MESSAGING_BATCH_MESSAGE_COUNT as v, SEMATTRS_MESSAGING_CONSUMER_ID as w, SEMATTRS_MESSAGING_DESTINATION_NAME as x, SEMATTRS_MESSAGING_KAFKA_BATCH_FIRST_OFFSET as y, SEMATTRS_MESSAGING_KAFKA_BATCH_LAST_OFFSET as z };