This module provides automatic instrumentation for mssql
There are two variations
This is the recomended variation. The source code can be found here
docker run -p 1433:1433 -d -e ACCEPT_EULA=Y --name otmssql -e SA_PASSWORD=P@ssw0rd mcr.microsoft.com/mssql/server
npm install --save opentelemetry-instrumentation-mssql
const { NodeTracerProvider } = require('@opentelemetry/node'); const { registerInstrumentations } = require('@opentelemetry/instrumentation'); const { MssqlInstrumentation } = require('opentelemetry-instrumentation-mssql'); const traceProvider = new NodeTracerProvider({ // be sure to disable old plugin plugins: { sequelize: { enabled: false, path: 'opentelemetry-plugin-mssql' } } }); registerInstrumentations({ traceProvider, instrumentations: [ new MssqlInstrumentation({ // see under for available configuration }) ] });MSSQL Instrumentation Options
MSSQL instrumentation has few options available to choose from. You can set the following:
Options Type DescriptionignoreOrphanedSpans
boolean
Set to true if you only want to trace operation which has parent spans
This variation would be depreciated soon. The source code can be found here
npm install --save opentelemetry-plugin-mssql
import {LogLevel} from '@opentelemetry/core' import {NodeTracerProvider} from '@opentelemetry/node' import {registerInstrumentations} from '@opentelemetry/instrumentation' // Enable OpenTelemetry exporters to export traces to Grafan Tempo. const provider = new NodeTracerProvider ({ plugins: { mssql: { enabled: true, // You may use a package name or absolute path to the file. path: "opentelemetry-plugin-mssql", }, }, logLevel: LogLevel.ERROR, }); registerInstrumentations({ tracerProvider: provider });
Supported
Request.query
ConnectionPool.query
Future
Request.execute
Request.batch
Request.bulk
ConnectionPool.batch
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4