Luismi Ramírez

fix(instrumentation-http): do not overwrite span error status if already set

2

## Which problem is this PR solving? If a span has already set its status as Error (2), it shouldn't be overwritten as this may result in its status changing...

Less restrictive Redis sanitization

1

We recently changed how MongoDB queries are sanitized to show more information to our users. (https://github.com/appsignal/appsignal-ruby/pull/819) We can do the same to Redis commands. Currently, we are sanitizing the whole...

Add support for Solid Queue

4

Solid Queue was announced in Rails World 2023. Start working on its support once released. https://rubygems.org/gems/solid_queue The current 0.1.0 gem present in Rubygems is empty. ## To do - [...

Remove the need for an Express error handler

1

The OpenTelemetry Express instrumentation now automatically records exceptions without the need of an error handler. See: https://github.com/open-telemetry/opentelemetry-js-contrib/pull/1657 ### ToDo - [ ] Update the integration dependency - [ ] Update...

ElasticSearch instrumentation

3

https://github.com/aspecto-io/opentelemetry-ext-js/tree/master/packages/instrumentation-elasticsearch Do we want to add this one to the default instrumentations? Note that it's not from the official contrib repository. ## To do - [ ] Add extractor -...

gRPC instrumentation

1

I just noticed there's a gRPC instrumentation in [the `opentelemetry-js` package](https://github.com/open-telemetry/opentelemetry-js/tree/main/experimental/packages/opentelemetry-instrumentation-grpc). That might be neat to support. If we agree, let's convert this to an issue.

In TS 4.4, `useUnknownInCatchVariables` is activated by default if you have it configured to `strict: true`. Which is a good practice. This makes the caught variables in a try/catch block...

As noted by @maltesa in [this comment](https://github.com/appsignal/appsignal-javascript/issues/564#issuecomment-1119337252), React's error boundaries pass additional error info that contains additional data such as the error stack trace. We already get the stack traces...

fix: clientComponentLoading span type

1

### What? Add the proper `next.span_type` attribute to `NextNodeServerSpan.clientComponentLoading` spans. ### Why? So all spans fit the same structure. ### How? By adding the attribute when starting the span.

docs->add appsignal pino transport

2

Hi there! 👋🏼 We've created an [AppSignal pino transport](https://github.com/appsignal/appsignal-nodejs/blob/0fffae87ebe269bb86b6adafba23388ecb802979/src/pino_transport.ts) and recently released it as part of our [v3.5.1 integration](https://www.npmjs.com/package/@appsignal/nodejs/v/3.5.1). This PR adds the transport to the v7+ compatible list.