Implement Datadog tagging standards for Form 526

[pacerwow]

As a user I want to be able to find any dashboard or monitor and know which application, service, and team owns it so that I can locate relevant dashboards in a timely manner, especially important for troubleshooting errors and outages.

Slack thread w Steve Albers

• Please begin with this dashboard, as it's most relevant to the immediate need (Toxic Exposure & EVSS to LH migration)
• Then locate any additional dashboards or monitors that are in need of updated tagging

1. Make sure that all of our dashboards and monitors are tagged to the "OCTO Benefits Portfolio" team: (That by itself gets us from 476 dashboards to 74)
2. For monitors, tag them service:disability-application
   • For monitors we are more flexible with the titles because they double as the title of notifications that are posted in Slack - so starting everything with "Benefits - Disability Claims - etc" makes them less readable
   • An added benefit to using the service:disability-application tag is that it adds the monitor to the disability service overview found here:
3. Naming convention, consistently name Dashboards “Benefits - Disability- 526 - [details]"
4. Use a shared, editable list that contains all of the Disability-related dashboards.
   • Steve created - Benefits - Disability - 526 (This can be renamed later if we feel there’s a better one to use.)
   • Team members should add their dashboard to this shared list when they create new dashboards
   • Team members should check to see if any existing dashboards have been added and add them if necessary

Acceptance Criteria

• [ ] All Datadog dashboards, monitors, and naming conventions follow the format provided.
• [ ] Please begin with

Other dashboards that might be ours?

---

How to configure this issue

• [ ] Attached to a Milestone (when will this be completed?)
• [ ] Attached to an Epic (what body of work is this a part of?)
• [ ] Labeled with Team (product support, analytics-insights, operations, service-design, Console-Services, tools-fe)
• [ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
• [ ] Labeled with Type (bug, request, discovery, documentation, etc.)

[pacerwow]

See this slack thread for additional info on Monitoring tagging:

https://dsva.slack.com/archives/C05QMQHQHKK/p1722865991826379?thread_ts=1721839305.054489&cid=C05QMQHQHKK