New Relic Reviews

I use New Relic for the creation of dashboards, alerts, and any type of observability resources that are relevant for my company.

The most valuable features of New Relic are the ease of creating dashboards and its integration capabilities with many external tools. It enhances operational response by providing analytics and alerts that help us address issues quicker. 

Using New Relic speeds up troubleshooting and resolution, giving us a clearer picture of where issues are, thus saving time and effort.

Our main focus is APM-related functionality, so we were looking for a convenient way to get all the details, as some of them are missing from New Relic and Grafana. Currently, we are working with Site24x7, where we are getting the information we are looking for in our comfort zone.

We used the Docker container as the agent in our server, which was split into one agent to collect the client's logs and metrics to see the web vitals, and another metric to collect the server metrics and APM-related traces.

The main benefit we found was the Error Inbox, and having all features available at a single point was very useful for us. The API functionality allows us to get hit counts from external sources, such as APIs or databases, and everything is mapped very clearly. We can overview which components are experiencing response delays, which ones are getting correct responses, and identify any unknown external APIs inside the application. We can investigate why we are getting 400 responses and similar issues.

It is for APM,  Application Performance Monitoring. And server monitoring.

There are two types of teams we have in every organization. One is for DevOps, and the second one is for performance testing. Those who are using these tools, like AppDynamics, Dynatrace, or whatever tool we have on the APM side. 

These tools are used by two teams: one is the performance team, and another one is the DevOps team. So, the setup and the alert system belong to the DevOps team, not for performance. So, I don't use any alerts in AppDynamics, Dynatrace, or any of the tools. 

It is used to monitor applications, error logs, and Azure Kubernetes. We have used this as a self-hosted service in Kubernetes. We are not using it as an agent-based service. We self-hosted this New Relic on Kubernetes and maintained it as a service.

It can be integrated with PagerDuty and ServiceNow, which can auto-generate alerts and incidents and assign them to the concerned team. The dashboards can also be customized. We can also check the trends over the past year or so.

A typical use case with New Relic, it’s an APM tool. We basically put the agent in, the agent discovers, and then we feed it onto predefined monitors with a controlled baseline. That baseline will then feed the problems that New Relic is detecting into PagerDuty. PagerDuty is our incident management tool. PagerDuty has something called Event Orchestration.

The incident that comes down from New Relic has a payload. We look at the payload, the attributes, and define rules in Event Orchestration. Let’s say the team wants to implement suppressions on alerts, some mutations, delays. They want to actually cross-engage a different team. So there are a lot of use cases that come about once we get the incident into PagerDuty from New Relic. New Relic obviously has the conditional baseline, which can be adjusted as we go along. So, that’s basically a staple activity that we perform with New Relic. Among other advanced use cases, which will take me a bit to explain here.

It’s like any other APM tool. One of the most outstanding features of any APM tool is the anomaly detection part. If there is logic that is going to detect the anomaly, with a predefined baseline that the system will produce over a period of time, for instance, a week, then keep adjusting it as you go along. That is one of the most useful cases of any APM tool that I feel.

We use New Relic APM for application monitoring, so if the application goes down, we do the root-cause analysis of why it went down. Was it the database? Was it the middle tier? We try to find out where it is and determine why the component went down.

We also use New Relic APM for its self-healing mechanism, which helps us determine the application's needs if it goes down. What data does it require? What was missing? Was the application able to send an email or a text alert?

We also have contractors responsible for the upkeep of the application. We have service-level agreements with these vendors, so we try to figure out how to incentivize or disincentivize the vendor. We try to measure their KPIs and SLAs, so New Relic APM tells us the uptime for the application for a month, a quarter, and a year.

These are our use cases for the solution.

What I like best about New Relic APM is its user interface because it's simple.

The tool lets us view what caused issues, especially in the cloud, where so many things could go wrong.

The most valuable feature of New Relic APM is end-to-end monitoring.

I use New Relic for monitoring and observing the entire environment. It offers end-to-end monitoring and observability to predict potential impacts in the coming weeks. For instance, it can detect if two endpoints start consuming more bandwidth than usual, thereby providing more insights about potential impacts on the environment.

New Relic helps us maintain and shape the environment from a network perspective by providing end-to-end monitoring and observability. It offers insights into normal and peak behaviors, alerts us to any issues, and assists with remediation plans.

We use the solution to ensure the applications perform at the accepted performance level. The application must not have any bugs or problems. It must also have no bottlenecks in the volume of the transactions. We use the tool before we deploy an application to production and during the first part of the deployment to ensure that the application will perform properly.

The product allows the developer to see the actual problems in the applications. It shows which part of the code and which part of the software component or architecture is having a problem. It's easy to resolve the issues and pinpoint the bottlenecks in the application.