New Relic vs Red Hat OpenShift

• Monitor traffic rates and server usage on real time
• Helps engineers to dive deep into an issue and guides them to the root cause
• Provides high-level system health status of different components (ie. Server capacity, RPM, page load time, error rate..)
• Near real time reporting
• Links with deployment so easy to understand if an issue has occurred after a particular release

Read full review

• The same as many similar K8 vendor solutions, OpenShift provides a managed Kubernetes environment with advanced facilitative components built-in.
• It provides the life cycle management/monitoring toolset to help users better visualize and understand both the application and infrastructure environment.
• Provides the scaling and recovering mechanism to ensure the high resilience of the application.
• CI/CD pipeline integration following the DevOps concept.

Read full review

• It would be helpful if use cases for particularly a Windows installation, were provided to help determine which set of configuration files would be the one a group would want to control. I.e. potentially with a department trying to do DevOps, it's difficult to determine which team needs to have responsibility for what at times. The reason I mention this, is New Relic seems to in many ways be a tool that's useful for DevOps-related processes and staff.
• On the main New Relic One site, sometimes a refresh option is available for new features. It would be helpful to see what the new features are in advance before trying this out. Particularly if doing a demo or a working season with another team.
• I'm not aware of a page or specific site which describes/summarizes all of the different NR Products and their features.
• Sometimes it's tricky to determine which product to use to accomplish a task.

Read full review

• The shift from v2 to v3 was a huge transition, and Red Hat [OpenShift] really failed at making this step easy for users - their documentation at the time was fairly lacking
• When things go wrong it can be hard to diagnose

Read full review

• Gives us great visibility into what our services are doing at all times.
• Alerts us quickly when there is a problem so we can address it with alacrity.
• Gives us extremely customizable options in regards to how we want to track, store, and materialize our data.

Read full review

• Reduce [the] friction of monitoring environments. This leads to [a] quicker troubleshooting process.
• Completely remove the need to authenticate each and every time you want to check on a specific environment.
• Faster deployment workflow increases [the] efficiency of developers when testing in lower environment containers.

Read full review