Skip to content

feat: add generic exception telemetry - #5134

Open
pierrealexandre2 wants to merge 2 commits into
webex:nextfrom
pierrealexandre2:piealexa/genericErrorTelemetry
Open

feat: add generic exception telemetry#5134
pierrealexandre2 wants to merge 2 commits into
webex:nextfrom
pierrealexandre2:piealexa/genericErrorTelemetry

feat: add generic exception telemetry

ee209bf
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks skipped Aug 18, 2026 in 13m 5s

You skipped this GitGuardian alert

5 secrets was uncovered from the scan of 1 commit in your pull request. ❌

Please have a look to GitGuardian findings and remediate in order to secure your code.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

Details

🔎 Detected hardcoded secrets in your pull request

  • Pull request #5134: piealexa/genericErrorTelemetry 👉 next
GitGuardian id GitGuardian status Secret Commit Filename
- - Basic Auth String ee209bf packages/@webex/internal-plugin-metrics/test/unit/spec/unhandled-exception-telemetry.ts View secret
- - Basic Auth String ee209bf packages/@webex/internal-plugin-metrics/test/unit/spec/unhandled-exception-telemetry.ts View secret
- - Basic Auth String ee209bf packages/@webex/internal-plugin-metrics/test/unit/spec/unhandled-exception-telemetry.ts View secret
- - Basic Auth String ee209bf packages/@webex/internal-plugin-metrics/test/unit/spec/unhandled-exception-telemetry.ts View secret
- - Basic Auth String ee209bf packages/@webex/internal-plugin-metrics/test/unit/spec/unhandled-exception-telemetry.ts View secret

🛠 Guidelines to remediate hardcoded secrets

  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.