O+M 2023-09-15

[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.

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

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
  • NOTE: This job will consistently timeout, but it is processing results ((more details)[https://github.com/change tracking update from nightly job to weekly #4345])
• Check Catalog Solr
• Catalog Dupe Check

Monthly Checklist

• Invicti Scan

Reference

• 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
• Update and revise Data.gov O&M Tasks

[btylerburton]

FYI db-solr-sync job failed in staging after timeout: https://github.com/GSA/catalog.data.gov/actions/runs/6180392791

16856 packages without harvest_object need to be manually deleted

EDIT: Not an issue worth investigating since it's staging

[btylerburton]

Weekly tracking update job timed out after indexing 24784/160168 datasets. Set it to re-run.

[btylerburton]

Solr review finds lots of memory pressure:

(% usage)

• Leader: 98.6
• F0: 64.7
• F1: 85
• F2: 97.4

[btylerburton]

Still, queries are executable, and fast. Does this have to do with running tracking update?

[btylerburton]

Catalog DCAT-US Dupe Check reports: 266 duplicated identifiers, where 42 are single digit integers
Catalog Geospatial Dupe check reports: 52 duplicated guids, most concerning of which is that an empty string ( ) is recorded across 179 datasets.

More on that here: https://catalog.data.gov/api/action/package_search?q=guid:%22%22&facet.field=[%22organization%22]