Visualize GDK pipeline bottleneck with Jaeger/Zipkin
Overview
The issue is to take information about pipeline from https://gitlab.com/api/v4/projects/gitlab-org%2Fgitlab-development-kit/pipelines/922806769/jobs and put it into https://zipkin.io/ or Jaeger.
To make it obvious where the GDK build bottleneck is, and make measurements easily reproducible for experiments.
Impacted categories
The following categories relate to this issue:
-
gdk-reliability - e.g. When a GDK action fails to complete. -
gdk-usability - e.g. Improvements or suggestions around how the GDK functions. -
gdk-performance - e.g. When a GDK action is slow or times out.
Steps to replicate (optional)
- Convert pipeline data into Zipkin/Jaeger span format
- Feed spans to Z/J
- Get visualization back
(bonus) 4. Get rid of spans, and infer them from start/stop events in real-time (bonus) 5. Extract subitem performant (RUN in docker file, bash function call in RUN script, etc.)
Proposal (optional)
Environment (optional)
- Operating system name:
<!-- output of `uname -a` command --> - Architecture:
<!-- output of `arch` command --> - The contents of your
gdk.yml(if any) - Ruby version:
<!-- output of `ruby --version` command --> - GDK version:
<!-- output of `git rev-parse --short HEAD` command -->