Azure Kubernetes Service (AKS) vs. New Relic

AKS works very well for running containerized applications that require high availability and scalability. This includes systems like our HRIS platform and customer-facing web applications. AKS is a good choice when applications are broken into multiple services that need independent scaling and deployment. It provides the flexibility needed to manage these architectures effectively. But for single, low-traffic applications or simple internal tools, AKS can be overkill. For scenarios like that Azure App Service would be better.

Incentivized

New Relic its an excellent tool for monitoring services used on the SAAS universe, like web servers, relational and nosql dbms, reverse proxies, text databases, etc. Its also a powerful tool to monitor resource usage on said servers. However, its not well fitted to monitor custom services - if you need to generate alerts based on logs or database information, for example

• AKS makes it easier to replicate data to multiple regions
• Azure portal make it easier to manage the resources of the organization

Incentivized

• It gives us insights of applications, infrastructure, clouds very well.
• The alerting system in New Relic helps us to easily identify the root cause which reduces the MTTR.
• It has new features related to AI which helps to troubleshoot any problem in a very short time it gives future predictions also.

Incentivized

• Steep learning curve
• Expected charges are unclear until you see real production usage
• Operations teams need to learn an entirely new skill set

Incentivized

• And while powerful, building tailored dashboards with organ-specific metrics (such as energy load variance across regions) can be difficult to navigate. The UI isn't as drag-and-drop easy, and query-based widgets typically involve some trial and error for non-devs.
• Alerts may be hypersensitive or over general. I We often get a spam of non-critical alerts while doing load testing, all overhauling to me alone and making it difficult to identify actual issues especially in energy systems where spikes are very common.
• With our expanding fleet of Iot devices, the per-host pricing model is becoming expensive, quickly. More detailed billing based on microservices, or that works at sensor level, would make it more adaptable for energy platforms.

Incentivized

The only issue that we have had with New Relic is that the price might be a little expensive for smaller companies. The amount of data you store in New Relic impacts the cost, and can get away from you if you don't work closely with the vendor. Overall though the application is top notch.

Incentivized

As already said, the UI/CLI and even terraform are perfectly fine, but certain details could be documented better. For instance, if I want to secure the whole Azure Kubernetes Service (AKS) with my own managed keys, then it is very complex and hard to get there. Not really a single source that gives you the whole picture. Besides that, it is still good to use, in most cases intuitive but details mentioned as above can be tricky.

Incentivized

The reason fir giving this rating is that New Relic's UI is straight forward, intuitive and easy to navigate which makes its accessible even for new users.It offers real time visibility which helps teams quickly spot problems and understand performance data. Moreover it offers comprehensive monitoring in one place making it easier to mange complex tools

Incentivized

Never observed an outage

Incentivized

there are times where browser cache will cause issues that require you to clear your browser before continuing.

Incentivized

Microsoft support was really good, whenever we raise any ticket they come back to us within a couple of hours.

Incentivized

The support team has been really helpful and resolved most of the issues on time. However, for a couple of issues, several follow-ups were needed to elicit a reasonable response. The issue was deeply technical and could have been investigated only by their Architects, and bringing them into the ticket took longer than needed

Incentivized

It's better to start by implementing New Relic in one project and test everything. Try to follow best recommended practices and read all the official documentation. Everything seems well tested. Then, start by installing agents to the rest of your projects and keep a close look to all logs and metrics New Relic gives you.

Amazon EKS stacked up very well and had better performance in some areas. However, Azure Kubernetes Service was a better fit given our Azure environment.

Incentivized

Data Dog has solutions that look more attractive, but not at their price point. We have also tried to build a solution straight from the Cloud, where our business is built, but some things are too hard to replicate. This shows that New Relic is useful and helps our efficiency.

Incentivized

Agent deployment is easily integrated into our workflow. Adding the agent to new servers is quick and painless

Incentivized

• We had to spend more time on Azure Kubernetes Service (AKS) than on AWS and GCP to get our kubernetes cluster up and running
• The resources on nodes need to be left out unused, so effectively it is wasting money there
• It definitely made us spend more time into maintaining kubernetes

Incentivized

• We were able to quickly identify our most time consuming APIs. In some cases we were able to bring down times for some apis from 4s to 200ms.
• We were able to identify our slowest database queries and optimize them for quicker response times.

Incentivized