-
Notifications
You must be signed in to change notification settings - Fork 107
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-08-26 #4864
Comments
|
Deleted staging |
After deployment, |
setting instance 1 (instead of 0) for |
set IMLS to manual schedule and marked it as a broken source, since there is no response to our request to unblock harvesting traffic. |
monthly harvest ioos with 30k+ records just refreshed all its timestamps to
UPDATE: Some (1127 to be exact, 3.5% ) are caught as simple file refreshing, for exchange this one |
apparently i don't have edit access to the audit log. ooooooooooof. can someone grant me that? |
Done. |
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: