Scope out logical groupings of alerts to our personnel

[vevetron]

User story / feature request

As a developer,
I need to know which alerts I'm responsible for
So I can act on them accordingly

Acceptance Criteria

• Make groups of our different softwares and alerts
• Discuss with team
• Get most people to be okay with it.

Notes

Initial work:
What do we need to be tracking? how should it be grouped? - Who is responsible for which group?

1. GTFS-RT Archiver
2. Airflow Alerts - Payments?
3. Airflow Alerts - GTFS-RT parser?
4. Airflow Alerts - DBT ALL?
5. Airflow Alerts - Download Parse and Validate GTFS
6. Airtable issue management

etc.

How do logically group alerts to our team so it's not too noisy and we can act on them.

[vevetron]

I suggest this should be grouped and documented in https://github.com/cal-itp/central_docs

[fsalemi]

Dear Colleague,

This email is to notify you that your service catalog request has been
submitted and has been sent for approval and/or fulfilment:

Requested on behalf of: Farhad Salemi
Request Submitted date: 2026-08-28 16:10:09 PDT

View the status of your Requested Item(s) in Native, click here: RITM0534002

[fsalemi]

@vevetron
Here is the first version of the Airflow alert grouping document and saved it in the shared drive: Airflow Errors Grouping
This initial version focuses primarily on alerts generated by Airflow and identifies the proposed logical grouping, distribution email address, and recipients for each DAG.
Alerts from applications outside of Airflow (for example, the GTFS-RT archiver) are not yet included and will be added in a future version.
Distribution list membership is still open for discussion and can be updated in Microsoft Outlook without requiring changes to the Airflow configuration.

[vevetron]

@fsalemi I took a pass - I saw payments vs general backend - i think there are too few groupings to be reasonable. I added a third group - backend. Though I feel like there should be 4 groups.