O+M 2024-01-13

[FuhuXia]

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

[FuhuXia]

harvest source /harvest/city-of-tempe-data-json-harvest-source sees 400 error on source url https://data.tempe.gov/api/feed/dcat-us/1.1.json for the past a few weeks. Will change its schedule to manual if the error continues.

➜ curl -i https://data.tempe.gov/api/feed/dcat-us/1.1.json
HTTP/1.1 400 Bad Request
Date: Mon, 13 Jan 2025 14:14:18 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 38
Connection: keep-alive
Access-Control-Allow-Origin: *
ETag: W/"26-b+ym8DAgwKWDAufh81PYsfNv0jo"
Vary: Accept-Encoding

{"error":"Invalid template transform"}

[hkdctol]

@tdlowden can you check with @crysacarter if we even have a POC to contact re City of Tempe?

[tdlowden]

I can see from email history that we have a name, but in the org audit, the person did not reply. @crysacarter can we try to reach out to them and let them know their harvest source is broken?