Story
New Relic
LululemonLululemon Brings Application Health onto New Relic
Lululemon, a consumer discretionary organization in Canada, uses Pixie from New Relic to support production support for SREs and developers.
Teams at Lululemon moved application health onto New Relic after local tools started to collide.
“SREs and developers needed a system that would still make sense after the original project team moved on.”
“New Relic provides observability software so engineering teams can monitor applications, infrastructure, and user experience.”
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 Pixie |
Story
Inside Lululemon, production support used to depend on whoever still had the latest file. That pattern is common in consumer discretionary groups working out of Canada. SREs and developers needed a system that would still make sense after the original project team moved on.
Lululemon 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 Lululemon 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.
