Generate Kibana or Grafana links for stage groups to dig into their budget spend
In #970 (closed) we made the performance of each component contributing to the error budget. This should allow people viewing the dashboard to determine where to look next.
I think we should try to wrap these in a definition like we have SLI definitions for services.
This would mean that we can add toolingLinks and perhaps link builders for Kibana to allow us to easily add links to the dashboard allowing viewers to dig through operations that are not performing well, and show descriptions for the components.
We currently have the following components attributing to stage group's error budgets:
| Element | Value |
|---|---|
| {component="proxy"} | 612829.8954 |
| {component="puma"} | 308530740.2 |
| {component="server"} | 51343873.91 |
| {component="storage"} | 28036665.57 |
| {component="trace_archiving_ci_jobs"} | 621219.3449 |
| {component="elasticsearch_searching"} | 658970.4157 |
| {component="goserver_op_service"} | 174693.7225 |
| {component="gitalyruby"} | 1605503.834 |
| {component="loadbalancer"} | 11511849.89 |
| {component="replicator_queue"} | 2101.877881 |
| {component="server_route_manifest_reads"} | 9307509.115 |
| {component="server_route_manifest_writes"} | 52584.25254 |
| {component="goserver"} | 181271183.5 |
| {component="praefect_cloudsql"} | 15166956.47 |
| {component="polling"} | 51228715 |
| {component="shared_runner_queues"} | 144350.5072 |
| {component="sidekiq_execution"} | 17498318.67 |
| {component="elasticsearch_indexing"} | 5087451.668 |
| {component="imagescaler"} | 1960660.784 |
Edited by Bob Van Landuyt