-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
O+M 2024-12-16 #5015
Comments
Tuesday 12/17https://github.com/GSA/data.gov/ Check Catalog Auto TasksCheck Harvesting Emails
|
DOT harvest source /harvest/national-transportation-atlas-database-ntad-metadata with url https://transtats.bts.gov/NTADmetadata/ is failing due to SSL cert error. The cert was issued on 2024-12-16 but has problem with the Intermediate certificates, as shown in |
Can the real ip from the catalog-proxy access log be mocked? We are seeing an increased hacking traffic from real_ip 127.0.0.1. +++++++++++++++++++ |
Reached out to DOT contacts about that transtats source issue. |
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
Weekly Checklist
Monthly Checklist
ad-hoc checklist
Reference
The text was updated successfully, but these errors were encountered: