430 New Relic Testimonials

Industry
Company Size
15 per page
  • 15
Reset
  • “With our new CI/CD environment, everything that is deployed is instrumented with New Relic, which gives us a good view of how our distributed platform is performing.”

  • "We worked closely with the Rackspace team to build a modern architecture that would provide the level of performance, scalability, and security we needed. Rackspace also provided us with Fusion-io SSD’s which provides simply superb IO performance. Rackspace has a great reputation. They are known for their high availability, performance, and security. When we tell people that we are running on Rackspace, we consistently get a great response. Our customers know they are in good hands."

  • "Many times when you’re troubleshooting you need a very transparent system so all the teams can see the same information. With New Relic we could actually solve the transparency issue between our dev teams and other teams. New Relic shows the details and blocks between backend and frontend."

  • "From there we were able to go through and with a single agent installation notice things that were falling between the cracks that allowed us to alleviate pressure before it was ever felt by any of the clients."

  • "What I like about New Relic is having everything available to me in a single place."

  • "Omnichannel is a really exciting strategy for Flight Centre. It's really the intersection between stores, which draw on forty years of knowledge about travel, and how we provide that same experience to our customers online and through digital channels."

  • "It's very easy to make users leave, and very difficult to make them come back. This has been one of the most significant technological challenges we have faced. It is perhaps the most complicated challenge, because in the end it is very easy to enter a website, read four news items and jump to the next one. If the user is provided with the information in no more than a few seconds, they will not come back. These are things that you have to constantly measure because they have a very big impact."

  • "It was clear that we had a weakness in monitoring our applications. We didn't know what was going on with them."

  • "We want to reduce the cognitive load on our engineers. We want our engineers to be agile. In terms of an engineer being able to move from one product to another, that commonality gives you that agility. There's some really good business outcomes there."

  • "New Relic is making my life easier because it's provided a place for engineers to come and collaborate without the kicking and screaming. We're able to get engineers excited to sign in, get them excited to instrument their services and get them excited to check on them whenever they need to."

  • "Observability is the table stakes, isn't it? It is non-negotiable in my worldview. We initially began with doing infrastructure and application monitoring in separate silos. And then we started graduating towards the more mature journey in observability where end-to-end signals were more important, and observability not only plays a part in faster mitigation, but also in prevention of some of the known incidents."

  • "We have SLOs on most parts of our system, and those workloads are set around core customer flows through the product. So we have that proactive ability to see what's impacting customer flows through the system and to address it in advance."

  • “Using this kind of system metric, QA regression is no longer just a black box exercise. It actually looks inside the box to see how the system reacted while QA was conducted as a particular kind of regression exercise.”

  • "I used to spend every waking hour investigating noise. Now, if a New Relic alert comes in, I see the issue straight away. All the information is already there on the incident page through the server. Now I spend 10 minutes investigating and can figure out the issue faster."

  • "The huge challenge we're facing is ensuring that our customers don't encounter any issues. We need to anticipate their needs and be alerted when there are errors on our apps, or when a microservice crashes or behaves poorly, which could potentially cause others to crash. It's important to us that our solution be stable and, if it isn't, that we are informed as quickly as possible so we can be proactive."