F
member badge
Florian Nowarre
Problem / Use Case
As a platform engineer or platform owner, I want to subscribe myself (or a team distribution list) to receive email notifications when a tenant replication fails on my platform — without needing to ask the meshStack operator to make a dhall configuration change.
Today, replication failure email recipients are statically configured in the dhall deployment config by an operator. If my team wants to be alerted when an Azure or GCP tenant fails replication, we have to raise a support request and wait for the operator to update the deployment config. This creates unnecessary friction and blocks platform teams from being autonomous.
Value / Impact
  • Platform team autonomy
    : Platform engineers can manage their own alert contacts directly from the platform configuration screen in the meshStack panel.
  • Faster incident response
    : Reducing the time between a replication failure occurring and the right person being notified improves mean time to recovery.
  • Operator offload
    : Operators no longer need to make deployment-level config changes for a routine notification preference.
  • Scales with team changes
    : Platform teams can add/remove notification contacts as team membership evolves, without a support ticket each time.
Proposed Experience
In the platform configuration screen of the meshStack panel, a platform owner should be able to:
  • Add one or more email addresses (individual or distribution list) as notification contacts for replication failures on that platform.
  • These contacts receive the same failure alert that is today only reachable via dhall config.
  • No operator/dhall involvement required.
Context / Links