Phone:400-882-3320
Guance 
Customer context
Sangfor’s IT-SRE team supports enterprise systems including ERP, CRM, supply-chain, and internal collaboration. Its published story describes how these systems connect to finance, delivery, and operating workflows.
The hybrid estate includes hyperconverged infrastructure, managed cloud, Kubernetes microservices, and existing IIS multi-site systems running across technology generations.
When a business system changed behaviour, SREs needed to assess impact across metrics, logs, traces, databases, middleware, and underlying resources.
Several architecture generations had separate views
Infrastructure, middleware, and application signals across hyperconverged, cloud, Kubernetes, and IIS environments remained in different tools.
Cross-service issues required manual reconstruction
A slow response could involve an application, database, middleware, or resource, requiring repeated alignment of metrics, logs, and traces.
Uniform thresholds created low-value alerts
Without business importance and error severity, critical events competed with large numbers of equal-priority notifications.
Implementation
Unify IaaS, PaaS, and application data
Infrastructure, middleware, applications, metrics, logs, traces, and business dashboards entered one platform organised through shared tags and object tiers.
Govern alerts by business tier
The published story describes S/A/B/C application tiers combined with monitoring severity so critical services and errors received greater handling priority.
Map technical signals to business workflows
A business dashboard organised runtime signals around quotation, contract, ordering, shipment, and collection so teams could drill from a process into applications and resources.
What changed
SRE gained a cross-layer investigation path
Teams could continue from a business signal into application, database, middleware, and infrastructure evidence.
Alert priority better reflected business impact
Application tier and error severity jointly informed routing instead of mixing critical events with low-value notifications.
Business teams could interpret technical state
Views based on quotation, contract, order, delivery, and collection placed technical anomalies in a business context.
Retrospectives retained shared evidence
Metrics, logs, traces, and business views used a common time range for later rule and architecture changes.
