Story
New Relic@
Johns Hopkins Medicine
Johns Hopkins Medicine Uses Pixie for Application Health
Johns Hopkins Medicine, a health care organization in the United States, uses Pixie from New Relic to support production support for SREs and developers.
Teams at Johns Hopkins Medicine moved application health onto New Relic after local tools started to collide.
“Inside Johns Hopkins Medicine, production support used to depend on whoever still had the latest file.”
“SREs and developers needed a system that would still make sense after the original project team moved on.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Capability | SREs and developers work from the same Pixie record for application health |
| Capability | Application health can be reviewed without waiting on a personal export |
| Capability | Named workflow replaces ad hoc routing for application health |
Story
Inside Johns Hopkins Medicine, production support used to depend on whoever still had the latest file. That pattern is common in health care groups working out of the United States. SREs and developers needed a system that would still make sense after the original project team moved on.
Johns Hopkins Medicine uses Pixie from New Relic as the working layer for application health. New Relic provides observability software so engineering teams can monitor applications, infrastructure, and user experience. The practical change is simple: production support has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What Johns Hopkins Medicine gets from New Relic is a durable place to run production support and a way for SREs and developers to see the same application health at the same time.
