New Relic vs GitLab
Hardware infrastructure monitoring
GitLab monitors application performance with extensive instrumentation, but it does not monitor traditional hardware-based infrastructure.
Synthetic Transaction Monitoring
The ability to monitor websites using Web browser emulation or scripted recordings of Web transactions. Creating behavioral scripts to simulate an action or path performed by a customer/end-user that would be taken on an application
Cloud Native Monitoring
The monitoring of cloud native applications including micorservices that are built to run in the cloud so that bottlenecks and issues can be addressed via insights into collected metrics.
Reviewing and analyzing a server for availability, operations, performance, security and other operations-related processes. Monitor servers system resources like CPU Usage, Memory Consumption, I/O, Network, Disk Usage, Process, etc. GitLab uses the Node Exporter (via Prometheus) to expose an extensive set of machine-level metrics on Linux and other Unix systems such as CPU usage, memory, disk utilization, filesystem fullness, and network bandwidth.
The monitoring of servers, application, network and security devices via generated log files to identify errors and problems for analysis. GitLab makes it easy to view the logs of running pods in connected Kubernetes clusters. By displaying the logs directly in GitLab, developers can avoid having to manage console tools or jump to a different interface.
Measures an application’s performance and tells whether it meets the service level agreements before it goes live to customers. Used for a product’s or platform’s continuous performance analysis and monitorin
Real User Monitoring (RUM)
Records user interaction with a client interacting with a server or cloud-based application. Determines if users are being served quickly and without errors and, if not, which part of a business process is failing
Network mapping that provides real-time views and performance monitoring of network devices, services, applications, connections and traffic patterns on one or more networks
Tracing provides insight into the performance and health of a deployed application, tracking each function or microservice which handles a given request. This makes it easy to understand the end-to-end flow of a request, regardless of whether you are using a monolithic or distributed system.
If you feel there are inaccurate statements in this comparison, please edit this page or propose edits by creating an issue. When creating an issue, please use the "Comparison page" template and assign to @dangordon to ensure we see your suggested changes. You can also send an email to firstname.lastname@example.org with your suggested edits if you're unable to create an issue or edit this page.
We strive for technical accuracy and will review and update this post for inaccuracies as quickly as possible.