Story
New Relic
BecaBeca Adopts New Relic for Incident Response
Beca, an information technology organization in the United States, uses NRQL from New Relic to support incident response for on-call engineers.
Beca uses NRQL to search what happened across services without SSHing into boxes.
“In the United States, on-call engineers already knew where log investigation went wrong: too many copies, too little ownership, and a close process that waited on the loudest inbox.”
“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 | On-call engineers work from the same NRQL record for log investigation |
| Capability | Log investigation can be reviewed without waiting on a personal export |
| Capability | Named workflow replaces ad hoc routing for log investigation |
Story
Beca did not need another dashboard that nobody opened. It needed incident response to move. In the United States, on-call engineers already knew where log investigation went wrong: too many copies, too little ownership, and a close process that waited on the loudest inbox.
NRQL from New Relic is now in that path. New Relic provides observability software so engineering teams can monitor applications, infrastructure, and user experience. The company treats it as production tooling for incident response, which is why on-call engineers live in it rather than exporting from it once a quarter.
Beca can show how log investigation is handled today. That is the value: a repeatable way to run incident response on software the rest of the industry already recognizes.
