Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Monitoring] Adjust code to send events for monitor "Sentry Forms: Find Forms - Form Detail - invalid PDF accessed Error Monitor" directly to DataDog #18965

Open
3 tasks
FranECross opened this issue Aug 15, 2024 · 0 comments
Assignees
Labels
Monitoring Needs refining Issue status Public Websites Scrum team in the Sitewide crew sitewide VA.gov frontend CMS team practice area

Comments

@FranECross
Copy link

FranECross commented Aug 15, 2024

Status

[2024-08-29] [Fran] Spike completed; this ticket updated and moved to Next Refinement.
[2024-08-19] [Fran] Blocked by the SPIKE referenced below. This ticket will be updated when the it's decided what mechanism will replace Sentry.

Description

Sentry will be deprecated, and some monitors for Sitewide products in Datadog rely on Sentry to push up errors, that are then aggregated in Datadog.

All Sentry Form monitors are written in such a way that they can be adjusted via code to send events directly to Datadog instead of Sentry, then the monitors will need to be adjusted to look for the error being sent into the logs. Bryan was able to find an example of the alerts being sent from vet website today in this slack thread.

Since we will be moving events that are already being sent, this should not result in any additional Datadog costs.

This is the forms monitor to be adjusted: Sentry Forms: Find Forms - Form Detail - invalid PDF accessed Error Monitor: https://vagov.ddog-gov.com/monitors/167983?view=spans

Engineering notes / background

Spike

Analytics considerations

Quality / testing notes

Acceptance criteria

  • "Sentry Forms: Find Forms - Form Detail - invalid PDF accessed Error Monitor: https://vagov.ddog-gov.com/monitors/167983?view=spans" monitor has been adjusted via code to send events directly to Datadog
  • Monitors have been adjusted to look for the error being sent into the logs
  • Datadog monitoring functions as expected for this item
@FranECross FranECross added Monitoring Needs refining Issue status Public Websites Scrum team in the Sitewide crew sitewide VA.gov frontend CMS team practice area Blocked Issues that are blocked on factors other than blocking issues. labels Aug 15, 2024
@FranECross FranECross self-assigned this Aug 19, 2024
@FranECross FranECross removed the Blocked Issues that are blocked on factors other than blocking issues. label Aug 29, 2024
@FranECross FranECross changed the title [Monitoring] Convert the monitor "Sentry Forms: Find Forms - Form Detail - invalid PDF accessed Error Monitor" to [mechanism TBD] [Monitoring] Convert the monitor "Sentry Forms: Find Forms - Form Detail - invalid PDF accessed Error Monitor" directly to DataDog Sep 9, 2024
@FranECross FranECross changed the title [Monitoring] Convert the monitor "Sentry Forms: Find Forms - Form Detail - invalid PDF accessed Error Monitor" directly to DataDog [Monitoring] Adjust code to send events for monitor "Sentry Forms: Find Forms - Form Detail - invalid PDF accessed Error Monitor" directly to DataDog Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Monitoring Needs refining Issue status Public Websites Scrum team in the Sitewide crew sitewide VA.gov frontend CMS team practice area
Projects
None yet
Development

No branches or pull requests

2 participants