Phone:400-882-3320
Guance 
Customer context
Nu Skin operates in personal care, nutrition, and wellness. In China, websites, apps, mini programmes, and shared application platforms support consumer services and internal business workflows.
As the digital estate expanded, application reliability, customer touchpoints, and business operations required a more continuous technical evidence path.
The published story describes context switching across independent monitoring tools and difficulty analysing logs, business data, cloud usage, and billing together.
Separate monitors lengthened the investigation path
Operations and development teams used different platforms for metrics, logs, and application context and repeatedly restated the incident background.
Logs could not readily support business analysis
Large, inconsistently structured log sources required technical extraction before business teams could use events and fields.
Resource usage and bills lacked application context
Billing totals alone could not explain which application, environment, or business activity drove resource consumption.
Implementation
Collect applications, traces, logs, and alerts together
The published story describes OneAgent collection for applications, traces, logs, and infrastructure, with processing, analysis, and alerting in one platform.
Collaborate around the same investigation record
Snapshots, notes, and sharing retained time ranges, queries, and evidence so development, test, and operations did not rely only on screenshots and log fragments.
Connect business data, cloud resources, and bills
Log fields and business events were normalised while cloud usage and billing data entered configurable analysis views.
What changed
Teams shared complete anomaly context
Metrics, logs, traces, and alerts could be reviewed in one platform with fewer tool changes and repeated explanations.
Duplicate monitoring entry points were consolidated
Shared collection and analysis reduced data movement and repeated rules across tools.
Cloud-cost analysis gained resource context
Usage and billing trends could be reviewed by application, environment, and resource; actual optimisation still required governance decisions.
Technical data became easier to use in operations
Normalised log fields and business events could provide more timely inputs for operating and resource analysis.
