DaaS / Products / Cloud Migration to Unified Full-Stack Observability

Cloud Migration to Unified Full-Stack Observability

A team migrates their on-premises database to Alibaba Cloud (OSS→RDS, OceanBase, Elasticsearch) with EventBridge-based infra monitoring, then extends the same event backbone to ingest Supabase application events (orders, signups, schema changes), creating a single unified pipeline that correlates infrastructure failures with business-logic anomalies and routes alerts via Twilio SMS/WhatsApp and Resend email while persisting all events into a DataWorks analytics lake for post-mortem and trend analysis.

Products involved

Scenario

Use this workflow when migrating legacy databases to Alibaba Cloud (RDS/OceanBase/Elasticsearch) while requiring real-time correlation between infrastructure health and application-level anomalies. It unifies ECS/RDS metrics and Supabase business events into a single EventBridge backbone, enabling instant multi-channel alerting and long-term trend analysis via DataWorks.

Integration steps

  1. Provision EventBridge Bus & IAM Role: Create a custom event bus and attach a RAM role with AliyunEventBridgeFullAccess.

    2. aliyun eventbridge CreateEventBus --EventBusName unified-obs-bus --Description "Full-stack observability backbone"

  2. Configure Infra Event Rules: Route ECS/RDS CloudMonitor metrics to the bus using a pattern filter.

    3. aliyun eventbridge PutRule --EventBusName unified-obs-bus --RuleName infra-alerts --EventPattern '{"source":["acs.ecs","acs.rds"],"detail-type":["StatusChange"],"detail":{"state":["ALARM"]}}'

  3. Ingest Supabase App Events: Enable Supabase Database Webhooks to POST to an API Gateway endpoint that forwards to EventBridge.

    4. ``sql CREATE TRIGGER order_hook AFTER INSERT ON orders FOR EACH ROW EXECUTE FUNCTION http_post('https://api-gw.aliyuncs.com/eb-ingest', row_to_json(NEW)::text); ``

  4. Route to Alerting Channels: Create EventBridge targets for Twilio and Resend via Function Compute.

    5. aliyun eventbridge PutTargets --EventBusName unified-obs-bus --RuleName app-alerts --Targets '[{"Id":"twilio-sms","Arn":"acs:fc:cn-hangzhou::functions/twilio-notify","InputTransformer":{"InputPathsMap":{"phone":"$.detail.phone"},"InputTemplate":"{\"To\":\"<phone>\"}"}}]'

  5. Persist to DataWorks Analytics Lake: Configure a DataWorks Data Integration job to consume from EventBridge and stage in OSS.

    6. ``python client.create_di_job(job_name="eb_to_oss_lake", source_type="eventbridge", target_type="oss", config={"bucket": "obs-lake", "partition": "dt={date}"}) ``

  6. Index for Correlation: Push structured events to OpenSearch for unified querying.

    7. curl -X PUT "https://<es-endpoint>/observability/_mapping" -H 'Content-Type: application/json' -d '{"properties":{"event_type":{"type":"keyword"},"severity":{"type":"integer"}}}'

Architecture

Infrastructure metrics (ECS, RDS) and application events (Supabase webhooks) converge into a centralized Alibaba Cloud EventBridge bus. EventBridge applies pattern-based routing to fan out real-time alerts to Twilio (SMS/WhatsApp) and Resend (Email) via Function Compute targets. Simultaneously, all raw events are batched into OSS and ingested into DataWorks for ELT processing, while a parallel stream indexes structured payloads into OpenSearch for low-latency correlation dashboards.

Prerequisites

Common pitfalls

Typical questions

FAQ

Q: How can I migrate from on-premises to the cloud while achieving unified full-stack observability across infrastructure and application events? A: The solution is structured as a cross-product combination spanning services such as DataWorks, EB, ESS, RDS, OpenSearch, Supabase, ECS, Twilio, Resend, IDaaS, GitBook, OSS, and OceanBase. This integrated setup provides the unified full-stack observability required to monitor infrastructure and application events throughout your cloud migration.