Crons: Add support for multiple environments

[gaprl]

Currently, a Cron Monitor does not support multiple environments such as "production", "development", etc.

---

Current estimated delivery: 03/22/23

Spec from @evanpurkhiser

We'll need to make some data model updates and adjust some assumptions about how monitors currently store status.

Adding environments means that each checkin entry will now be associated to an environment (or the default empty string).

1. Monitor status can no longer be denormalized onto the monitor object. The status needs to come from the most recent checkin for the selected environment(s). The status of the monitor will become dependent on the most recent checkin.

2. Each monitor should have a list of activated environments associated to it. We should introduce a monitorenvironment model that has a FK to the monitor and a FK to the project environment.

3. next checkin time needs to move to the environment.

4. Checkin details should be specific to a single environment. It does not make sense to try and show checkins for a monitor across multiple environments.

5. When listing monitors we should only allow selection of a single environment.

6. Checkins must now accept the environment for which the checkin is associated to. (If none is passed it should default to production (see environment in the link))

7. The check_monitors task now needs to take into account each environment as well, so we'll need to update the query to join on the monitor_environments table.

Tasks

Beta Give feedback

1. Crons: Disallow changing what project a monitor is associated to #45009
   +0
   
2. Crons: Create a MonitorEnvironment model #45011
   +0
   
3. Crons: Allow checkins to be associated to an environment #45013
   +0
   
4. Crons: Backfill monitor with default environments #45017
   +0
   
5. Crons: Update check_monitor task to dual write into monitor environments #45022
   +0
   
6. Crons: Update monitor_index + monitor_details endpoint to filter on environment #45019
   +0
   
7. Crons: Update monitor_stats to filter on environment #45020
   +0
   
8. Crons: Remove dual write logic for monitor checkins, leaving only writing to monitor environments #45023
   Status: Backlog Team: Crons +2
   
9. Crons: Allow filtering monitors by environment on the frontend. #45024
   2 of 2
   Status: In Progress Status: Stale Team: Crons +3
   
10. Crons: Update docs to indicate how to send environments #45025
    2 of 2
    Status: Backlog Team: Crons +2
    
11. Crons: Backfill checkins with default environments #45994
    +0
    
12. Crons: Generate monitor errors in the correct environment #46137
    Status: Backlog Team: Crons +2
    
13. Crons: Add backend endpoint for monitor environment deletion #47854
    +0
    
14. Crons: Add frontend endpoint for monitor environment deletion #47855
    +0

[epicserve]

When this feature is added, it would be nice if we could set up alerts for just one environment. For example, I would want to get alerted when it's down for production, but I'm not sure I wouldn't want alerts for other environments.

[gaprl]

Update from the Crons team: We've successfully rolled out support for multiple environments! 🎉

Here are some instructions per platform:

• SDKs: Your monitor environment will be automatically detected based on the SDK configuration. See how to configure environments for Python and PHP.
• Sentry CLI: We have feat(crons): Allow specifying checkin environment sentry-cli#1599 that will be merged soon and enable an additional argument environment.
• HTTP/API: If you are using our API to send check-ins, see how to specify an environment.

If you have any questions or issues, feel free to reach out to us at crons-feedback@sentry.io. Thank you.