Monitor application performance

GitLab provides a variety of tools to help operate and maintain your applications.

Measure reliability and stability with metrics (DEPRECATED)

Deprecated in GitLab 14.7.

caution
This feature is in its end-of-life process. It is deprecated for use in GitLab 14.7, and is planned for removal in GitLab 16.0.

Metrics help you understand the health and performance of your infrastructure, applications, and systems by providing insights into your application’s reliability, stability, and performance. GitLab provides a default dashboard that you can extend with custom metrics, and augment with additional custom dashboards. You can track the metrics that matter most to your team, generate automated alerts when performance degrades, and manage those alerts - all within GitLab.

Manage alerts and incidents

GitLab helps reduce alert fatigue for IT responders by providing tools to identify issues across multiple systems and aggregate alerts in a centralized place. Your team needs a single, central interface where they can easily investigate alerts and promote the critical alerts to incidents.

Are your alerts too noisy? Alerts configured on GitLab metrics can configured and fine-tuned in GitLab immediately following a fire-fight.

Track errors in your application

GitLab integrates with Sentry to aggregate errors from your application and surface them in the GitLab UI with the sorting and filtering features you need to help identify which errors are the most critical. Through the entire triage process, your users can create GitLab issues to track critical errors and the work required to fix them - all without leaving GitLab.

  • Discover and view errors generated by your applications with Error Tracking.

Trace application health and performance (DEPRECATED)

Deprecated in GitLab 14.7.

caution
This feature is in its end-of-life process. It is deprecated in GitLab 14.7, and is planned for removal in GitLab 15.0.

Application tracing in GitLab is a way to measure an application’s performance and health while it’s running. After configuring your application to enable tracing, you gain in-depth insight into your application’s layers. With application tracing, you can measure the execution time of a user journey for troubleshooting or optimization purposes.

GitLab integrates with Jaeger - an open-source, end-to-end distributed tracing system tool used for monitoring and troubleshooting microservices-based distributed systems - and displays results within GitLab.

Aggregate and store logs (DEPRECATED)

Version history
caution
This feature is in its end-of-life process. It is deprecated in GitLab 14.7. It will be removed completely in GitLab 15.2.
On self-managed GitLab, by default this feature is not available. To make it available, ask an administrator to enable the feature flag named monitor_logging. On GitLab.com, this feature is not available. This feature is not recommended for production use.

Developers need to troubleshoot application changes in development, and incident responders need aggregated, real-time logs when troubleshooting problems with production services. GitLab provides centralized, aggregated log storage for your distributed application, enabling you to collect logs across multiple services and infrastructure.

Manage your infrastructure in code

GitLab stores and executes your infrastructure as code, whether it’s defined in Ansible, Puppet or Chef. We also offer native integration with Terraform, uniting your GitOps and Infrastructure-as-Code (IaC) workflows with the GitLab authentication, authorization, and user interface. By lowering the barrier to entry for adopting Terraform, you can manage and provision infrastructure through machine-readable definition files, rather than physical hardware configuration or interactive configuration tools. Definitions are stored in version control, extending proven coding techniques to your infrastructure, and blurring the line between what is an application and what is an environment.

More features