Story
Elastic@
Skidmore Owings and Merrill
Skidmore Owings and Merrill Standardizes Application Health on Elastic
Skidmore Owings and Merrill, an industrials organization in the United States, uses Elastic Observability from Elastic to support production support for SREs and developers.
Elastic Observability became the place Skidmore Owings and Merrill uses to see traces and errors in one place when a service slows down.
“Industrials work at Skidmore Owings and Merrill spans more than one site, even when headquarters sits in the United States.”
“SREs and developers asked for a shared way to run production support without freezing local judgment.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Capability | Application health can be reviewed without waiting on a personal export |
| Capability | Named workflow replaces ad hoc routing for application health |
| Capability | Production support stays visible to adjacent teams through Elastic Observability |
Story
Industrials work at Skidmore Owings and Merrill spans more than one site, even when headquarters sits in the United States. Application health was splitting across regional habits. SREs and developers asked for a shared way to run production support without freezing local judgment.
Elastic (Elastic Observability) is what they standardized on. Elastic builds search, observability, and security software on Elasticsearch, used to find information and investigate operational data. Skidmore Owings and Merrill uses it as the system of record for application health, with SREs and developers as the primary operators and other groups coming in through the same queue.
Leaders get a picture they can actually walk. Teams get fewer mystery statuses. The story is about operating change, not an unpublished percentage.
