fix(event-log): add event logging for embedded Superset

[luizotavio32]

SUMMARY

Cherry-picks #40083 (add event logging for embedded Superset) into the 6.1 branch.

This also includes the follow-up fix from #41942, which refines the embedded-dashboard detection in loggerMiddleware. The original check classified events by testing whether the URL contained the substring /embedded/, which was too broad: a regular dashboard whose slug is literally embedded (URL /dashboard/embedded/) also contains /embedded/, so its events were incorrectly tagged with source: 'embedded_dashboard' instead of source: 'dashboard'.

The substring check is replaced with a regular expression that matches only the actual embedded route shapes:

• /dashboard/:idOrSlug/embedded/
• /embedded/:uuid/

As a result, regular dashboard events are no longer misclassified as embedded, while genuine embedded routes continue to be detected correctly.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

N/A — internal event-logging metadata change only.

TESTING INSTRUCTIONS

Unit tests in superset-frontend/src/middleware/logger.test.ts cover source classification across paths:

• /dashboard/123/embedded/ -> embedded_dashboard
• /embedded/abc-def-uuid/ -> embedded_dashboard
• /dashboard/123/ -> dashboard
• /dashboard/embedded/ (slug is literally embedded) -> dashboard

Run:

cd superset-frontend
npm run test -- src/middleware/logger.test.ts

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[bito-code-review]

Bito Automatic Review Skipped - Branch Excluded

Bito didn't auto-review because the source or target branch is excluded from automatic reviews.
No action is needed if you didn't intend for the agent to review it. Otherwise, to manually trigger a review, type /review in a comment and save.
You can change the branch exclusion settings here, or contact your Bito workspace admin at evan@preset.io.

[netlify]

✅ Deploy Preview for superset-docs-preview ready!

Name	Link
🔨 Latest commit	b73902c
🔍 Latest deploy log	https://app.netlify.com/projects/superset-docs-preview/deploys/6a512cbc6a6f88000801fa21
😎 Deploy Preview	https://deploy-preview-41938--superset-docs-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[bito-code-review]

The flagged issue is correct. Using path?.includes('/embedded/') is indeed too broad, as it will incorrectly match any URL containing the string 'embedded', including regular dashboard URLs like /dashboard/embedded/.

To resolve this, you should use a more precise check that validates the URL structure. You can use a regular expression or check for the specific path segments to ensure it only matches actual embedded routes.

Here is a concise fix using a regex to ensure /embedded/ is part of the expected path structure:

    const isEmbedded = /\/(embedded|dashboard\/.*\/embedded)\//.test(path || '');
    if (dashboardInfo?.id && (path?.includes('/dashboard/') || isEmbedded)) {
      logMetadata = {
        source: isEmbedded ? 'embedded_dashboard' : 'dashboard',
        source_id: dashboardInfo.id,
        dashboard_id: dashboardInfo.id,
        ...logMetadata,
      };
    }

There are no other comments on this PR to address. Would you like me to help with anything else?

superset-frontend/src/middleware/loggerMiddleware.ts

const isEmbedded = /\/(embedded|dashboard\/.*\/embedded)\//.test(path || '');
    if (dashboardInfo?.id && (path?.includes('/dashboard/') || isEmbedded)) {
      logMetadata = {
        source: isEmbedded ? 'embedded_dashboard' : 'dashboard',
        source_id: dashboardInfo.id,
        dashboard_id: dashboardInfo.id,
        ...logMetadata,
      };
    }