Apache Log4j vs. New Relic

There is multiple reasons. All types are logging messages support not only string msg. We can use parametrized variables for logging Support advance filter for logging like (Data, Markers, Regular Expression) Support Plugin Architecture (We just use the dependency and Layout configuration with minimal config, and this will start to work) Integration support with application server Could enable.

Incentivized

It is perfect for observing our energy platforms during high-load situations, such as grid demand spikes, or our real-time ingest of sensor data, allowing us to respond in real time to anomalies. And it’s a good way to monitor API performance in client dashboards, too. But it’s not as conducive for low-budget/low-code work or deep customization that doesn’t get ample development support given its complexity and expense.

Incentivized

• Integration with java.
• Configure logging levels.
• Customize logging contents.

Incentivized

• Capturing Front end Metrics specially web vitals and setting up alerts for violations really helps.
• NRQL is great tool to fetch the data you need. With queries you can pull the data and put the data by table or by chart. You can even trend graphs and create dashboards.
• Synthetic Monitoring is very helpful for proactive monitoring. You can use it for user journeys by using scripted browser monitor type or just check availability using PING type.
• ASk AI is great addition that can fetch details you need with natuaral language

Incentivized

• Fixed the vulnerability which is reported which affect many big brand.
• There should be security check to check all vulnerability.

Incentivized

• Support for SQL like query with more functional features of analysis while viewing distributed tracing.
• support for very low level specific integration from APIs to classes to functions to piece of code
• More detailed documentation, as we faced issues while integrating for the first time.

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 an engineer, New Relic has been very quick and easy for me to pick up/install/use. It has been less easy for some of the less technical-minded folks in our organization and their UI still is inconsistent multiple years after refactoring their platform to be New Relic One.

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

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.

The ability to customize logging levels and manage log files is superior to other products we have looked at; due to this we selected to go with log4j.

Incentivized

New Relic is the most full-featured offering that we've found, and is incredibly easy to start using with a PHP app. The New Relic agent is installed as a PHP extension so it is able to monitor and track the performance of any PHP app being run by the web server. Other tools required the installation and setup of a PHP dependency at the application level.

Incentivized

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

Incentivized

• Good logging tools we can integrate with minimal resource consumption.
• Ease of understanding.
• Plugin play component Architecture.
• Advance filter support can be used to filter all types of logs and events, which can be further analyzed.

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