Story
Darktrace Uses Pixie for On-call Response
Darktrace, an information technology organization in the United Kingdom, uses Pixie from New Relic to support incident management for on-call rotations.
Darktrace standardized on-call response on New Relic instead of keeping parallel copies.
“Inside Darktrace, incident management used to depend on whoever still had the latest file.”
“That pattern is common in information technology groups working out of the United Kingdom.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Productivity | Handoffs in incident management sit in a shared queue instead of a mailbox trail |
| Risk and compliance | Pixie is the governed place on-call rotations use for incident management |
| Capability | New joiners can see how incident management actually runs |
Story
Inside Darktrace, incident management used to depend on whoever still had the latest file. That pattern is common in information technology groups working out of the United Kingdom. On-call rotations needed a system that would still make sense after the original project team moved on.
Darktrace uses Pixie from New Relic as the working layer for on-call response. New Relic provides observability software so engineering teams can monitor applications, infrastructure, and user experience. The practical change is simple: incident management has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What Darktrace gets from New Relic is a durable place to run incident management and a way for on-call rotations to see the same on-call response at the same time.