Saint-Gobain Guance

Connect on-premises infrastructure, public cloud, application traces, logs, and alerts

Hybrid-cloud operating view
APM and log correlation
Shared alerts and dashboards

Customer context

Saint-Gobain operates globally across building materials and services. Its published Guance customer story describes digital systems split between an on-premises data centre and public cloud, creating a hybrid environment that required infrastructure, application, and log evidence to work together.

As systems and monitoring entry points expanded, responders needed to place cloud resources, hosts, networks, middleware, logs, and application performance in one context instead of aligning multiple tools for every incident.

Hybrid-cloud data lived in different platforms

Cloud-native monitoring and data-centre tools supplied partial views, forcing teams to cross-check resource, host, network, and log state.

Hybrid-cloud data lived in different platforms

Application issues lacked request-path context

A slow API could involve cloud resources, middleware, a database, an external dependency, or application code; server metrics alone could not isolate the bottleneck.

Application issues lacked request-path context

Alerts were disconnected from investigation evidence

Rules and notification paths differed by system, so operations and development teams repeatedly aligned timestamps, affected objects, and evidence already checked.

Alerts were disconnected from investigation evidence

Implementation

Ingest signals from the data centre and public cloud

Cloud resources, hosts, networks, middleware, and logs entered Guance so teams could confirm overall state in one view and drill down through service and resource relationships.

Use APM to explain why an application request changed

APM recorded request paths, service time, and errors for core applications. When latency increased, teams could inspect service spans, databases or external dependencies, then correlate logs and host state.

Move from a shared alert to metrics, traces, and logs

Infrastructure, log, and application-performance alerts and dashboards shared context, allowing responders to continue from an alert into the relevant metrics, traces, and original logs.

What changed

Coverage extended from resources to applications and experience

Infrastructure, logs, APM, and RUM formed a connected workflow instead of stopping at a host or cloud-resource view.

Hybrid-cloud data gained a shared governance entry point

Data-centre and public-cloud signals could be analysed by the same service, environment, and time window, reducing cross-platform searches.

The evidence chain from alert to cause became more continuous

Teams could move from an alert through metrics, request traces, and logs to reconstruct where an anomaly occurred and what it affected.

Platform work focused on operating workflows

Shared collection, query, dashboard, and alert capabilities reduced duplicate platform engineering and left more time for reliability work.

Frequently asked questions

What did the hybrid-cloud scope include in the Saint-Gobain story?

The published story describes an on-premises data centre and public cloud, with cloud resources, hosts, networks, middleware, logs, and application-performance data. It does not specify every cloud service or region.

What did APM add to hybrid-cloud troubleshooting?

APM connected the services, time, and errors in a request so teams could continue into databases, external dependencies, logs, and the underlying host state.

How did shared alerts reduce investigation gaps?

With service and time context attached, responders could move directly from an alert to related metrics, traces, and logs instead of locating the same anomaly again in separate tools.

More customer stories