Alibaba Cloud Retail China Translated from Chinese

Wandianzhang (万店掌)

IT Operations Automation

Wandianzhang had growing observability complexity across retail-AI products, but alert rules, dashboards, and infrastructure inspection still spanned multiple disconnected systems. Teams had to configure alarms in separate tools, write custom SQL for business dashboards, and inspect clusters manually to find capacity or health risks.

market share exceeds 80% in the snack/fast-moving-consumer-goods segment
supports 500,000+ retail chain stores

Reported impact

Business outcome

Wandianzhang gave its retail-AI platform a more unified and proactive operations model. Teams no longer have to bounce across tools for alarms or dashboard creation, and routine infrastructure and application checks can be delegated to AI-assisted missions before problems escalate.

  • Productivity Improvement
  • Risk Reduction

Solution

Wandianzhang used Alibaba Cloud STAROps to turn its observability stack into an AI-assisted operations system. Cloud Monitor 2.0 became the unified alert-governance center for logs, Prometheus metrics, application monitoring, and cloud-product signals, while STAROps adds rule-inspection and governance suggestions so teams can reduce noise and keep alerting logic healthy over time. For business observability, STAROps applies NL2SQL to translate natural-language questions into operational dashboards, which removes much of the manual SQL work required to build event-center reports. The same platform also runs scheduled missions that inspect ACK clusters, application health, and cloud resources, with digital employees capable of running checks automatically and requesting human-in-the-loop support when needed. This gives Wandianzhang a single AI operations surface instead of multiple hand-maintained control paths.

Data flow

Logs, metrics, application signals, and cloud-resource events are unified in Cloud Monitor 2.0 and then analyzed by STAROps. Operators can ask natural-language questions to generate dashboards, while scheduled missions inspect ACK clusters and cloud services and feed findings back into operations and alert-governance workflows.

Solution architecture

4 components · 3 layers
  1. Storage
    • Log Service SLS Feeds logs into the unified observability and alerting system.
  2. Orchestration
    • STAROps Provides AI-driven alert governance, NL2SQL dashboards, inspection missions, and root-cause analysis.
  3. Governance
    • Cloud Monitor 2.0 Acts as the unified alarm-management layer across observability data sources.
    • Application Real-Time Monitoring Service (ARMS) Supplies application-monitoring data used in AI-assisted operations workflows.

Architecture clues

  • Long-running missions let agents perform recurring inspection work rather than only react to incidents.
  • NL2SQL is used to turn operations questions into dashboards without hand-written SQL.
  • The same STAROps layer handles alert governance, dashboard generation, cluster inspection, and root-cause analysis.

Evidence from the source

STAROps gives the team unified alarm governance, NL2SQL-generated dashboards, and scheduled missions for ACK, application, and resource inspections. (original: 通过 STAROps,完成告警治理、NL2SQL 实现业务看板、自动巡检和根因分析... ACK 集群巡检、应用健康巡检、资源健康巡检等工作。)
The company has already accumulated digital-operating experience across more than 500,000 retail chain stores and over 80% share in one major vertical. (original: 积累 500,000+ 零售连锁门店数字化经验,最高(零食快消)行业市场占有率超 80%。)
Wandianzhang said alarm rules, metrics, logs, and APM were spread across different systems, which made governance difficult and increased the risk of alert storms. (original: 可观测系统缺乏统一告警治理和管理平台,指标、日志、APM 等需要在不同系统上配置不同的告警规则... 容易造成错配、漏配和告警风暴产生。)
Transparency Evidence & methodology 86/100 reference value · 88% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value86/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence88%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 of 12 key fields link to a named source.
  • Direct evidence15/20
    3 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Alibaba Cloud

    万店掌通过STAROps实现数字门店业务智能运维_零售&电商_阿里云客户案例

    First-party
    https://www.aliyun.com/customer-stories/retail-2026-ovopark
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Region
    • Company size
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • Published on source page Jul 17, 2026 · Alibaba Cloud · First-party
    Open date source
Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.