Microsoft Azure vs. New Relic

Azure is particularly well suited for enterprise environments with existing Microsoft investments, those that require robust compliance features, and organizations that need hybrid cloud capabilities that bridge on-premises and cloud infrastructure. In my opinion, Azure is less appropriate for cost-sensitive startups or small businesses without dedicated cloud expertise and scenarios requiring edge computing use cases with limited connectivity. Azure offers comprehensive solutions for most business needs but can feel like there is a higher learning curve than other cloud-based providers, depending on the product and use case.

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

• Microsoft Azure is highly scalable and flexible. You can quickly scale up or down additional resources and computing power.
• You have no longer upfront investments for hardware. You only pay for the use of your computing power, storage space, or services.
• The uptime that can be achieved and guaranteed is very important for our company. This includes the rapid maintenance for security updates that are mostly carried out by Microsoft.
• The wide range of capabilities of services that are possible in Microsoft Azure. You can practically put or create anything in Microsoft Azure.

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

• The cost of resources is difficult to determine, technical documentation is frequently out of date, and documentation and mapping capabilities are lacking.
• The documentation needs to be improved, and some advanced configuration options require research and experimentation.
• Microsoft's licensing scheme is too complex for the average user, and Azure SQL syntax is too different from traditional SQL.

• 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

Moving to Azure was and still is an organizational strategy and not simply changing vendors. Our product roadmap revolved around Azure as we are in the business of humanitarian relief and Azure and Microsoft play an important part in quickly and efficiently serving all of the world. Migration and investment in Azure should be considered as an overall strategy of an organization and communicated companywide.

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 Microsoft Azure is [doing a] really good with PaaS. The need of a market is to have [a] combo of PaaS and IaaS. While AWS is making [an] exceptionally well blend of both of them, Azure needs to work more on DevOps and Automation stuff. Apart from that, I would recommend Azure as a great platform for cloud services as scale.

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

It has proven to be unreliable in our production environment and services become unavailable without proper notification to system administrators

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

We were running Windows Server and Active Directory, so [Microsoft] Azure was a seamless transition. We ran into a few, if any support issues, however, the availability of Microsoft Azure's support team was more than willing and able to guide us through the process. They even proposed solutions to issues we had not even thought of!

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

As I have mentioned before the issue with my Oracle Mismatch Version issues that have put a delay on moving one of my platforms will justify my 7 rating.

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.

As I continue to evaluate the "big three" cloud providers for our clients, I make the following distinctions, though this gap continues to close. AWS is more granular, and inherently powerful in the configuration options compared to [Microsoft] Azure. It is a "developer" platform for cloud. However, Azure PowerShell is helping close this gap. Google Cloud is the leading containerization platform, largely thanks to it building kubernetes from the ground up. Azure containerization is getting better at having the same storage/deployment options.

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

• For about 2 years we didn't have to do anything with our production VMs, the system ran without a hitch, which meant our engineers could focus on features rather than infrastructure.
• DNS management was very easy in Azure, which made it easy to upgrade our cluster with zero downtime.
• Azure Web UI was easy to work with and navigate, which meant our senior engineers and DevOps team could work with Azure without formal training.

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