Add graphql error tracking for secrets manager UI

Ahmad Husseinrequested to merge
577449-track-graphql-errors into master

What does this MR do and why?

As part of #577449 (closed) there is a desire to track more data from secrets manager usage for the closed beta, and this MR implements a portion of that by tracking graphql errors on the frontend in Sentry. This has been done by using the captureError feature of createAlert which was already in use for all of the graphql requests in these components.

References

Partially implements #577449 (closed)

Screenshots or screen recordings

image

How to set up and validate locally

The easiest to validate would be the secret form.

  1. Upload a Premium+ license.
  2. Enable the feature flags secrets_manager and secrets_manager_group.
  3. Set up openbao on your gdk.
  4. Enable the Secrets Manager on gdk for a project.
  5. Navigate to the Secure > Secret Manager page, and click on New Secret
  6. Fill out required details (excluding expiration/rotation) but enter an invalid name (i.e add a space) to trigger an error
  7. Verify Sentry captureException stub is logged to the devtools console

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #577449 (closed)

Edited by Ahmad Hussein

Merge request reports