Founded in Shenzhen in 2016, Timekettle develops products and services for cross-language communication. Its translation earbuds combine voice technology, Bluetooth connectivity and machine translation for business, travel and everyday conversations. This case focuses on the applications, service traces and operational data supporting those products.
TranslationIndustry2016FoundedShenzhenFounded in China
BUSINESS CHALLENGES
A conversation spans more than one metric
The experience crosses device connectivity, app interactions and backend requests. As the business grows, Timekettle needs to connect signals across those stages, detect issues and give product teams evidence for improving the experience.
User experience, traces, logs and infrastructure data lived in separate tools. Investigating a slow or failed request meant repeatedly aligning timestamps and objects.
Bluetooth connectivity and two-person conversations have different operational signals. Teams need to relate those business indicators to application performance to understand which stage is affected.
Maintaining multiple tools, organizing alerts and preparing data for analysis consumes time that could otherwise go toward product improvements and delivery.
KEY RESULTS
50%+
Less time on related operational analysis
30%+
Lower annual platform build and maintenance labor costs
End to end
User sessions connected to backend calls
SOLUTION
Timekettle × Guance — Solution
01
Follow a user session into its service calls
RUM SDK telemetry connects application experience to backend traces. When latency or errors arise, engineers can continue into the relevant services and logs, including slow SQL, without reconstructing the context from scratch.
2
Connected sides: user sessions and backend calls
02
Bring logs, metrics and infrastructure together
DataKit collects container logs, metrics and events into a shared observability platform. This reduced time spent on activities including alert-noise reduction, root-cause investigation and capacity forecasting by more than 50%.
50%+↓
Less time on related operational analysis
03
Build views around the product experience
Dashboards cover Bluetooth operations, two-person conversations and core business indicators, helping technical and business teams relate experience changes to service health. A common platform also reduces tool-building and maintenance work, saving more than 30% in annual related labor costs.
30%+↓
Annual platform build and maintenance labor costs
BUSINESS IMPACT
Give investigation time back to product teams
01
Reconstruct user-visible issues more easily
Connected frontend and backend context lets engineers start with the experience problem and follow it into the relevant service records.
02
Reduce duplicated tool maintenance
A shared platform lowers the ongoing effort of managing multiple tools, preparing evidence and organizing alerts.
03
Give technical and business teams a common view
Bluetooth, conversation and core business indicators keep performance discussions tied to specific product experiences.
Make every connection easier to understand
Connect device, application and business telemetry with an observability plan built around the user experience.
