update adding buildings page

website/docs/adding_meters_buildings.md

@@ -24,4 +24,9 @@ The following tables in the SQL database should be updated each time a new meter
  - Update building image by uploading image to `osu-energy-images` AWS S3 bucket (manual upload will be simplest)
  - Get map ID from https://www.openstreetmap.org/ ("way" on openstreetmap = map ID in database)
 - `meter_group_relation`
+
  - Match the corresponding meter group and meter ID together in. One meter group can be mapped to several meters, but not the other way around
+
+- Also need to update [validIDs file in automated-jobs](https://github.com/OSU-Sustainability-Office/automated-jobs/blob/main/check-acq/validIDs.json) to reflect the added buildings, meters, meter groups
+ - Needed to check if the newly added API endpoints are up at any given time. See [Cloudwatch](cloudwatch) for more info
+ - Might integrate this better in the database at some point

website/docs/cloudwatch.md

@@ -12,8 +12,8 @@ description: Overview of Cloudwatch and SNS Email Alerts
 :::
 
 - Important on left sidebar of AWS Cloudwatch:
- - Logs > Log groups
- - Alarms > All alarms
+ - Logs > Log groups > `/ecs/collect-check-acq` and `/ecs/collect-sec-data`
+ - Alarms > All alarms > `TimeoutError` and `3Or4DaysOutage`
 - The amount of time it takes for an alarm to go from "In alarm" to "Insufficient data" is defined by what you have set the "period" of the alarm as. In general, it takes 3 periods for the alarm state to reset
  - This is important because if you set the "period" too high, the alarm will never reset itself and will stay in the alarmed state permanently
  - Since the two jobs tracked by Cloudwatch (solar meter uploads vs regular meter uploads) are only run every 24 and 48 hours respectively, it is usually safe to leave the alarm period as 1 hour