Add backend (server) performance monitoring docs for remix

[AbhiPrasad]

Right now our Remix performance docs are frontend focused. Let's add more specifics around what to add for backend performance monitoring.

Discussed in getsentry/sentry-javascript#6965

^{Originally posted by alexblack January 28, 2023}
Hi, we're running Remix with express. I want to make sure our performance monitoring and tracing is setup as extensively as possible with Sentry.

The docs only seem to mention browser tracing for Remix. What about the server? Should we set it up as described for express?

https://docs.sentry.io/platforms/node/guides/express/

const Sentry = require("@sentry/node");
const Tracing = require("@sentry/tracing");
const express = require("express");
const app = express();

Sentry.init({
  dsn: "https://9149118330e64539861e6112c30b1fff@o522466.ingest.sentry.io/5633981",
  integrations: [
    // enable HTTP calls tracing
    new Sentry.Integrations.Http({ tracing: true }),
    // enable Express.js middleware tracing
    new Tracing.Integrations.Express({
      // to trace all requests to the default router
      app,
      // alternatively, you can specify the routes you want to trace:
      // router: someRouter,
    }),
  ],

  // We recommend adjusting this value in production, or using tracesSampler
  // for finer control
  tracesSampleRate: 1.0,
});

Thanks!

Alex

[mydea]

I think we can close this, as we now have better support for remix server side through OTEL!