Monitor workflow - Instrument


This page gives an overview of GitLab's vision for enabling the Instrument workflow within the Monitor stage.

Why Instrument?

The first step in application performance management is collecting the proper measurements. Getting accurate data in is critical. In order to know the health of your services and application, we'll help you collect appropriate application and infrastructure data. We focus primarily on instrumenting metrics and traces as apart of the three pillars of observability, logs will be streamed directly from a deployed Elasticsearch as mention the logging vision section

Doing so will enable you to act based on known information.

Initial setup

We aspire to make the configuration and instrumentation of these easy and automated as possible. We do this by providing a clear documented guide for the following steps:


Dashboards are a vital component in any observability solution as they provide the key to understanding complex data streams. A user should be able to view and set up the following dashboards:

Define Business level Objectives

The detection of unwanted behaviors of an application starts with setting Service Level Objectives and Indicators. These are internal standards of success by which we measure production systems. Monitoring and alerting on these critical metrics is the basis of any observability solution. Businesses want to know the health of these metrics rather than details about the underlying infrastructure. In order to bridge that gap, users should be able to define the business metrics (SLI/SLO) based on application or infrastructure metrics. This way, when an alert is triggered there is a common understanding of its impact.

What's next

We plan to provide a streamline instrumentation experience to allows our users to quickly and easily collect the needed information, additional detail on our direction can be found in the instrument to minimal epic