Skip to main content

CUSTOMER STORY

Connect in-vehicle data.
Understand the service behind the experience.

ABOUT ZEEKR

About ZEEKR

ZEEKR is an intelligent-mobility brand headquartered in Hangzhou, China, developing, manufacturing and supporting intelligent electric vehicles. Its 2024 annual report recorded 17,439 employees across the company and consolidated subsidiaries at year-end, with research and development accounting for approximately 43%.

Intelligent mobility Industry
17,439 Consolidated employees, end of 2024
Hangzhou, China Headquarters

BUSINESS CHALLENGES

Follow an in-vehicle issue into the relevant service

An in-vehicle application issue can involve runtime behavior and multiple service calls. Connecting the data helps engineers move from the symptom to the relevant requests and narrow the investigation.

Metrics, traces and logs in separate tools required repeated searches and manual time alignment.

Single-layer monitoring could not explain where the experience deteriorated. Application data needed to connect to service tracing.

Development and operations needed the same time window, requests and alerts to reduce repeated explanations and handoffs.

KEY RESULTS

30%

Expected reduction in user-experience issue investigation time

25%

Expected reduction in investigation data preparation hours

20%

Expected reduction in manual sensitive-field review hours

SOLUTION

ZEEKR × Guance — Solution

01

Ingest in-vehicle application data

Bring runtime logs and service requests into one platform. Organize analysis by application, time and request relationships to connect experience issues to backend investigation.

25%

Expected reduction in investigation data preparation hours

02

Follow experience issues through application traces

RUM and APM connect experience to service calls, slow requests, errors and logs. Alerts, snapshots and incident tracking help teams investigate the same evidence.

30%

Expected reduction in user-experience issue investigation time

03

Process sensitive fields before analysis

Apply consistent scanning and redaction rules while retaining necessary investigation context. Data analysis and information protection become part of the same workflow.

20%

Expected reduction in manual sensitive-field review hours

Guance data-scanning rules showing generic settings, not customer records.
DATA PROTECTIONProtect sensitive information with consistent processing rules

BUSINESS IMPACT

Connected experience data and shared team context

01

Collaborate on the same incident

Shared services, time windows and evidence reduce the need to reconstruct context during handoffs.

02

Consolidate monitoring maintenance

Centralize collection and alert management to give teams more time for experience analysis and incident handling.

03

Apply consistent data protection

Scanning and redaction retain necessary clues while protecting sensitive content throughout investigation.

Follow in-vehicle and application issues along one path

Plan the collection, experience analysis and investigation workflow that fits your automotive engineering team.