* fix(instrumentation-net): Don't operate on closed span

* Fix lint

* feat(instrumentation-bunyan): add log sending to Logs Bridge API

This extends the Bunyan instrumentation to automatically add a
Bunyan stream to created loggers that will send log records to
the Logs Bridge API: https://opentelemetry.io/docs/specs/otel/logs/bridge-api/

Now that the instrumentation supports separate "injection" of fields
and "bridging" of log records functionality, this also adds two boolean
options to disable those independently: `enableInjection` and
`enableLogsBridge`.

This also updates the instrumentation to work with ES module usage.

Closes: #1559

* markdown lint fixes

* markdown lint fixes

* catch up with recent core-deps update

* some type tweaks suggested by David

* more specific type

Co-authored-by: Amir Blum <[email protected]>

* use more self-explanatory code for mapping Bunyan level to OTel severity, from blumamir

* export OpenTelemetryBunyanStream for direct usage in Bunyan loggers without the instrumentation

* .apply over .call suggestion

* consistency suggestion

* suggestion to use the longer (perhaps clearer) logger var name

* switch to false-by-default config vars to avoid surprises with undefined values

See https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md#boolean-value
Suggestion from blumamir.

* document using OpenTelemetryBunyanStream without the instrumentation

* fix https://eslint.org/docs/latest/rules/prefer-spread lint error

* drop options to OpenTelemetryBunyanStream constructor because YAGNI

* temporarily drop CI caching to test theory on unit-test (18) CI failure

* more CI debugging: restore cache, add some 'npm ls -a' to look into NoopContextManager being used

* elide Bunyan 'pid' and 'hostname' fields in OTel log record attributes

Because they are redundant with 'process.pid' and 'host.name'
resource attributes. Add some docs on how to use resource detectors
to the example, because the HostDetector is not on by default in
the NodeSDK.

* update test for having elided 'pid' and 'hostname' fields

* CI debugging: ignore the 'npm ls -a' exit status, they shouldn't break the build

* fix lint and compile errors

* CI debugging: turn on diag DEBUG to test a theory

* turn off diag in this example

* undo CI debugging changes

* update deps to current releases and sync package-lock.json

* disableInjection -> disableLogCorrelation

* disableLogsBridge -> disableLogSending

Avoid using 'bridge' terminology at suggestion from specs that the Bridge API is an internal detail.

* correct the default instrumentation scope name (as discussed earlier)

* tests: fix test for intrumentationScope.name change in previous commit

* fix lint

---------

Co-authored-by: Amir Blum <[email protected]>
Co-authored-by: Hector Hernandez <[email protected]>

#1832)

Closes: #1823

Co-authored-by: Marc Pichler <[email protected]>

* feat: add support for mongodb v6

* chore: lint fix

* chore: revert bump of mongodb

* chore: revert test script

* chore: revert changelog

* chore: filter node versions in TAV

* chore: fix .tav.yml

---------

Co-authored-by: Daniel Dyla <[email protected]>

… FastifyDeprecation warning for 404 request (#1763)

For a 404 `request.routeOptions.url` is undefined. Since [email protected]
when routeOptions was added, we shouldn't fallback to the deprecated
request.routerPath.

This also corrects the assumption that the handler name is "bound ..."
in all cases. E.g. for a 404 it is Fastify's core "basic404" internal
function.

Also add a test that Fastify instrumentation works for ESM usage.

Fixes: #1757
Co-authored-by: Marc Pichler <[email protected]>

Co-authored-by: Daniel Dyla <[email protected]>

…te to diag.debug (#1836)


Co-authored-by: Trent Mick <[email protected]>

…ions (#1840)

* docs(user-interaction): update docs to include examples of config options

* add example to prevent span creation

* fix lint

* address PR comments

* update link to list of events

* syntax updates

Co-authored-by: Martin Kuba <[email protected]>

---------

Co-authored-by: Martin Kuba <[email protected]>

…ient-sqs versions using the AWS JSON 1.0 protocol (#1844)

Versions 3.446.0 and later switched to a new JSON protocol.
https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-sqs/CHANGELOG.md#34460-2023-11-08

Refs: #1838 (comment)

…ONS_EXTENSION_VERSION is defined (#1846)

Co-authored-by: Trent Mick <[email protected]>

This also reduces the number of pino versions tested with
test-all-versions test (from 42 to 13, currently).

…ion scope name, to align with instrumentations (#1822)

Closes: #1782

…ies (#1804)

Closes: #1787

…ttribute from DynamoDB spans (#1748)

* feat: add configuration to customise dynamodb statement serialization

* fix: format readme

* chore: pass DiagLogger to DynamoDB instrumentation

* chore: omit db statement when serializer is not configured or when it returned undefined
Allow for passing operation to serializer

* chore: run lint:fix

---------

Co-authored-by: Amir Blum <[email protected]>

* chore: release main

* chore: sync package-lock.json

---------

Co-authored-by: opentelemetrybot <[email protected]>