Firebase Alerts Routing Shift from Console Email Fan‑out to Cloud Functions 2nd Gen firebasealerts Triggers

Teams need to decide how to handle Firebase Alerts to keep notification volume manageable without missing important signals. The default console configuration sends every alert email to all project members, offering no built‑in way to scope messages by alert type or individual recipient. An alternative is to intercept alerts with Cloud Functions 2nd gen firebasealerts triggers, filter them in code, and forward only high‑severity events to the appropriate channels or users.

This approach depends on the availability of firebasealerts event triggers for the chosen runtime and region, and introduces additional function invocations that could recreate noise or add cost if not carefully filtered. Before committing to either path, teams must confirm what routing options the Firebase console currently provides and verify which alert categories are supported by the trigger in their target environment.

What scoping options does the Firebase console provide for alert emails by alert type and project member? Does the firebasealerts trigger support all alert categories (Crashlytics, Performance, App Distribution, billing) in the selected runtime and region? How does the expected cost of filtered forwarding compare to accepting the default fan‑out in terms of function invocations and risk of missed alerts?