O+M 2022-08-25

[hkdctol]

As part of day-to-day operation of Data.gov, there are many Operation and Maintenance (O&M) responsibilities. Instead of having the entire team watching notifications and risking some notifications slipping through the cracks, we have created an O&M Triage role. One person on the team is assigned the Triage role which rotates each sprint. This is not meant to be a 24/7 responsibility, only East Coast business hours. If you are unavailable, please note when you will be unavailable in Slack and ask for someone to take on the role for that time.

Check the O&M Rotation Schedule for future planning.

Miscs

• Watch for user email requests
• Watch in #datagov-alerts and Vulnerable dependency notifications (daily email reports) for critical alerts.
• Monitor and improve Data.gov O&M Dashboard

Acceptance criteria

You are responsible for all O&M responsibilities this week. We've highlighted a few so they're not forgotten. You can copy each checklist into your daily report.

Daily Checklist

Check Production State/Actions

• README

Note: Catalog Auto Tasks
You will need to update the chart values manually. Click the Action link in each issue and grab the values from monitor task output and check runtime.

• DB-Solr Sync
• Check Harvesting Emails
• New Relic Alerts Triaged
• Triage DMARC Report from Google

Weekly Checklist

• Audit Log (more info on AU-3 and AU-6 Log auditing)
• Tracking Update
• Check Catalog Solr
• Catalog Dupe Check
• Invicti Scan

[btylerburton]

8.22.23

• Lots of harvest failures due to validations errors in sources. No anomalies.

[nickumia-reisys]

O&M Retro started to document a way of structuring the O&M role a bit more.

[btylerburton]

• Tracking update fails, but this is expeted
• DMARC has numerous 116 fails in the last 5 days, but there is no documentation on how to triage this
• DB-SOLR-SYNC has identified 5k+ objects that have to be removed manually. That process is in action, and troubleshooting steps have been added to the new O&M troubleshooting section.
• Ran duplicate check and it turned up several with shared identifiers.
  • Ran check org duplicates to identify the orgs with dupes
  • Ran De-dupe on each org with duplicates
  • De-dupe script continued to run for ca-gov
• Catalog Solr instances have MANY logging errors, but this is expected drive-by hacking traffic per Fuhu
• Added troubleshooting section to O&M doc: https://github.com/GSA/data.gov/wiki/Operation-and-Maintenance-Responsibilities#troubleshooting