Skip to content

Using both Bun and Express leads to "express is not instrumented" warning #17779

@RudolfSchreier

Description

@RudolfSchreier

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/bun

SDK Version

10.15.0

Framework Version

Express 5.1.0

Link to Sentry event

No response

Reproduction Example/SDK Setup

https://github.com/RudolfSchreier/sentry-express-bun-demo

Steps to Reproduce

  1. Get a working SENTRY_DSN for some project
  2. start the demo using env SENTRY_DSN=... bun run dev

Expected Result

The express server starts up with working Sentry integration and no warnings.

Actual Result

The express server starts up, but with a Sentry warning about missing instrumentation:

[Sentry] express is not instrumented. Please make sure to initialize Sentry in a separate file that you --import when running node, see: https://docs.sentry.io/platforms/javascript/guides/express/install/esm/.

Additional Context

When using both Bun and Express, it is unclear which SDK to preferably use (@sentry/node or @sentry/bun), but both appear to show this issue.

It is unclear if the warning is correct or erroneous (and Express integration is actually working).

It is unclear to me from the description of #13674 if this the expected result for Express v5.

Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.

Metadata

Metadata

Assignees

Labels

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions