Reviewer's Guide

This pull request enforces user opt-in for MCP tracing by short-circuiting reportPluginCall based on user preference, removes server-config gating from telemetry notifications and settings to streamline the UI, and cleans up deprecated fields in the market and MCP tracing schemas.

Sequence diagram for plugin call reporting with user opt-in tracing

sequenceDiagram
    participant User
    participant DiscoverService
    participant UserStore
    participant LambdaClient
    User->>DiscoverService: Initiate plugin call
    DiscoverService->>UserStore: Check userAllowTrace
    alt User has not opted in
        DiscoverService-->>User: Skip reporting
    else User has opted in
        DiscoverService->>LambdaClient: Report plugin call
        LambdaClient-->>DiscoverService: Response
    end

Entity relationship diagram for updated market and MCP tracing schemas

erDiagram
    MARKET_REPORT {
      callDurationMs int
      clientId string
      customPluginInfo any
      errorCode string
      errorMessage string
      identifier string
      isCustomPlugin boolean
      metadata object
      methodName string
      methodType enum
      platform string
      requestSizeBytes int
      responseSizeBytes int
    }
    MCP_TRACE {
      errorCode string
      errorMessage string
      identifier string
      isCustomPlugin boolean
      metadata object
      methodName string
      methodType enum
      requestSizeBytes int
      responseSizeBytes int
      sessionId string
    }

Class diagram for DiscoverService and MCPService tracing changes

classDiagram
    class DiscoverService {
      +reportPluginCall(reportData: CallReportRequest)
      - Skips reporting if !userAllowTrace
    }
    class MCPService {
      +trace(...)
      - inputParams removed
      - outputResult removed
    }

File-Level Changes

Possibly linked issues

• #0: The PR implements user opt-in for MCP tracing and refines telemetry, addressing the issue's data collection concerns.

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.