O+M 2024-11-11

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

• Check auto generated O&M tickets from no status column
• Check Harvesting Emails
• New Relic Alerts Triaged
• Triage DMARC Report from Google

Weekly Checklist

• DB-Solr Sync
• 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
• Check user management requests
• Check Snyk Dashboard and cleanup

Monthly Checklist

• Invicti Scan

ad-hoc checklist

• audit/review applications on cloud foundry and determine what can be stopped and/or deleted.

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]

All weekly tasks complete.

[FuhuXia]

ed.gov's json source harvest/education-json has been failing for the past week due to SSL certificate problem for the URL https://data.ed.gov/data.json

$ curl -I https://data.ed.gov/data.json
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

[hkdctol]

The URL resolves for me--is it a different situation for harvester?

[FuhuXia]

Yeah chrome browser does not complain. But curl or our python agent complain data.ed.gov's Sectigo cert issuer. Taking a closer look...

[FuhuXia]

Their cert was updated recently. I don't think it was successful, since ssllab grade it B.
https://www.ssllabs.com/ssltest/analyze.html?d=data.ed.gov&s=165.224.131.203
This server's certificate chain is incomplete. Grade capped to B.

[FuhuXia]

We can contact ed.gov's POC and let them know this SSL issue on their site. The harvester will give error until the issue is fixed.
https://www.sslshopper.com/ssl-checker.html#hostname=data.ed.gov