chore: Sentry Wrapper with Performance and Error Tracing

[bwoody13]

What does this PR do?

Creates a wapper for callbacks using Sentry to monitor performance and log errors directly into the dashboard. We updated all calls in getUserAvailability as a demonstration of how to use the wrapper and confirmed that calls are being traced in the dashboard by making a booking. Adds tracking to an existing parent transaction if it can locate one. See photo below for this.

Fixes # (issue)
https://osshack.com/bounty/29

Updated tracesSampleRate in apps/web/sentry.server.config.ts to 1.0, so that transactions can be traced.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Chore (refactoring code, technical debt, workflow improvements)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How should this be tested?

Create bookings and check that the dashboard is monitoring performance.

Mandatory Tasks

• Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected.

Performance Results

Running a script that performs a simple mathematical calculation within a loop of 1000000 iterations. See comments for the script. Our results were: Plain execution time: 441, Monitored execution time: 8094. This suggests that using these wrappers within large loops can incur significant overhead and is thus not recommended.

For smaller loops, the cost incurred may not be very significant on an absolute scale
considering that a million monitored iterations only took roughly 8 seconds when monitored.

[vercel]

@bwoody13 is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Thank you for following the naming conventions! 🙏 Feel free to join our discord and post your PR link to collect XP and win prizes!

[github-actions]

📦 Next.js Bundle Analysis for @calcom/web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[ThyMinimalDev]

when writing the wrapper functions, no need to respecify all the parameters, you can use typescript Parameters<typeof _getUserAvailability> and the same approach used in sentry wrapper with ...args, example:

const getEventType = async (...args: Parameters<typeof _getEventType>) => {
  return monitorCallback(_getEventType, ...args);
};

[bwoody13]

In the newest commit. Thanks for the suggestion!

[bwoody13]

Performance Script:

import monitorCallback from "./sentryWrapper";

const processorBoundTask = async (x: number) => {
  return Math.sin(x) + Math.cos(x);
};

const measureExecutionTime = async (fn: (x: number) => Promise<number>, numIterations = 1000000) => {
  const start = Date.now();
  for (let i = 0; i < numIterations; i++) {
    fn(i);
  }
  const end = Date.now();
  return end - start;
};

const compareExecutionTimes = async () => {
  const plainExecutionTime = await measureExecutionTime(processorBoundTask);
  const monitoredExecutionTime = await measureExecutionTime((x: number) =>
    monitorCallback(processorBoundTask, x)
  );

  console.log(`Plain execution time: ${plainExecutionTime}`);
  console.log(`Monitored execution time: ${monitoredExecutionTime}`);
  return [plainExecutionTime, monitoredExecutionTime];
};

export default compareExecutionTimes;

export { measureExecutionTime };

[keithwillcode]

Nice work!

[zomars]

Seems like this is causing this #12753