Story
Elastic@
Johns Hopkins Medicine
Johns Hopkins Medicine Runs Production Support with Elastic
Johns Hopkins Medicine, a health care organization in the United States, uses Kibana from Elastic to support production support for SREs and developers.
Johns Hopkins Medicine folded Kibana into production support so SREs and developers share one view of application health.
“From the United States, health care teams still had to serve customers and internal partners who expected a straight answer.”
“Elastic builds search, observability, and security software on Elasticsearch, used to find information and investigate operational data.”
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 Kibana |
Story
Johns Hopkins Medicine grew application health faster than the local tools around it. From the United States, health care teams still had to serve customers and internal partners who expected a straight answer. SREs and developers were the ones stitching the picture together by hand.
Rolling out Kibana put production support on Elastic. Elastic builds search, observability, and security software on Elasticsearch, used to find information and investigate operational data. Johns Hopkins Medicine keeps the product in the path where work already happens, so SREs and developers do not context-switch into a graveyard system used only for audits.
The visible result is steadier production support. Application health is easier to inspect, and adjacent groups can join SREs and developers without a guided tour of someone's desktop.
