CUSTOMER STORY

Give alerts business context so teams can focus on issues that need action

ABOUT WANGXIAOBAO

About the customer

Wangxiaobao provides AIoT and data services for sales intelligence in sectors such as real estate, connecting data from physical locations with sales operations. Applications, devices, and data services support these workflows, and technical teams need to identify service issues across their distributed operational signals.

Sales intelligence Industry

AIoT and data services Business focus

Sales operations Serves

The challenge

More alerts still required manual investigation context

Wangxiaobao connects several applications, services, and resources. Local monitoring could flag individual abnormalities without explaining the affected business flow, leaving teams to organize duplicate notifications and find related evidence.

Labels and object relationships differed across tools. Several alerts could describe one incident or obscure the issue that required priority.

Incomplete shared context forced investigators to switch between services, logs, and resources using experience, interrupting the investigation.

KEY RESULTS

30%

Expected reduction: Cross-service diagnosis time

30%

Expected reduction: Duplicate-alert handling hours

15%

Expected reduction: Monitoring maintenance effort

SOLUTION

Wangxiaobao × Guance — Solution

Connect dispersed data with common labels

DataKit collects runtime evidence with consistent service, environment, and resource labels. Metrics, logs, and traces can then be analyzed around the same object.

15%

Expected reduction: Monitoring maintenance effort

Use topology to explain the affected scope

Resource and microservice dependencies appear in one view. Teams can drill from an abnormal object into related services and calls instead of checking platforms one by one.

30%

Expected reduction: Cross-service diagnosis time

Organize alerts around the investigation

Service and resource context groups abnormal signals. Traces, logs, and metrics help teams examine the issue and progressively tune duplicate notifications and low-value rules.

30%

Expected reduction: Duplicate-alert handling hours

BUSINESS IMPACT

Use alert context to resolve business issues more effectively

Abnormal signals support a shared diagnosis

Metrics, traces, and logs for the same service can be reviewed together, reducing separate descriptions of one incident.

Alert tuning gains an observable basis

Common labels and objects help identify duplicate signals and prioritize them by business impact, supporting ongoing improvements in notification quality.

Maintenance effort can support reliability work

Consolidated collection and analysis let teams spend more time on rule quality, incident reviews, and service operations.

Build observability around your business

Work with Guance to connect telemetry, investigate service issues, and give teams shared operational context.

Give alerts business context so teams can focus on issues that need action

About the customer

More alerts still required manual investigation context

Connect dispersed data with common labels

Use topology to explain the affected scope

Organize alerts around the investigation

Use alert context to resolve business issues more effectively

Abnormal signals support a shared diagnosis

Alert tuning gains an observable basis

Maintenance effort can support reliability work

Build observability around your business

More customer stories