O+M 2025-07-02

[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 applications on Cloud.gov Dashboard 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
• Fix broken links in the tracked issue reports
• Any non-routine blockers/failures should be written up in O&M Events Notes

[FuhuXia]

Reducing catalog-fetch from 3 instances to 1 instance. Will let it run for a month or so and then evaluate the effect to see if it eliminates the duplicates in the harvesting. 1 instance, even it will takes longer, has more than enough bandwidth to finish all the harvest jobs.

[FuhuXia]

issue raised for failed harvest source

• Harvest Source Error: ARM data.json #5302

[FuhuXia]

PetalBot is not playing nice with catalog. It is making excessive useless requests, sometime at the rate of 20 requests/sec.

Thinking of blocking this bad bot.

[FuhuXia]

We see malicious requests from spoofed real_ips. Those IP are from private IP CIDR, such as 172.16.0.0/12 or 127.0.0.1. Tried with AWS WAF rules but it was not effective to identify this kind of traffic.

Create a nginx config to block this spoofed-real-ip malicious traffic.

discussion in slack.

[FuhuXia]

Basic auth is added to catalog-dev in all environments(dev, staging, prod) to stop crawler traffic. I has increase exponentially in recent days in dev space.