kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Update Prometheus Merge Request Metrics page

Browse source
This commit is contained in:
Joshua Lambert 2017-06-19 11:19:36 +00:00 committed by Achilleas Pipinellis
parent 2923a0c8fe
commit 54ab21a923
2 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

BIN
doc/user/project/integrations/img/merge_request_performance.png
View file

Binary file not shown.
Side by side Swipe Overlay

Before

Width:  |  Height:  |  Size: 65 KiB

After

Width:  |  Height:  |  Size: 59 KiB

8
doc/user/project/integrations/prometheus.md
View file

@ -167,15 +167,15 @@ environment which has had a successful deployment.
## Determining the performance impact of a merge ## Determining the performance impact of a merge
> [Introduced][ce-10408] in GitLab 9.2. > [Introduced][ce-10408] in GitLab 9.2.
> GitLab 9.3 added the [numeric comparison](https://gitlab.com/gitlab-org/gitlab-ce/issues/27439) of the 30 minute averages.
Developers can view the performance impact of their changes within the merge Developers can view the performance impact of their changes within the merge
request workflow. When a source branch has been deployed to an environment, a request workflow. When a source branch has been deployed to an environment, a sparkline and numeric comparison of the average memory consumption will appear. On the sparkline, a dot
sparkline will appear showing the average memory consumption of the app. The dot
indicates when the current changes were deployed, with up to 30 minutes of indicates when the current changes were deployed, with up to 30 minutes of
performance data displayed before and after. The sparkline will be updated after performance data displayed before and after. The comparison shows the difference between the 30 minute average before and after the deployment. This information is updated after
each commit has been deployed. each commit has been deployed.
Once merged and the target branch has been redeployed, the sparkline will switch Once merged and the target branch has been redeployed, the metrics will switch
to show the new environments this revision has been deployed to. to show the new environments this revision has been deployed to.
Performance data will be available for the duration it is persisted on the Performance data will be available for the duration it is persisted on the